Skip to content

mvschwarz/openrig / packages/daemon/assets/plugins/openrig-core/skills/loading-addressable-markdown

loading-addressable-markdown

Verified

Use when a mission, slice, dashboard, or task references Markdown as path#h2-slug or path#h2-slug/h3-slug outside the OpenRig context-pack library.

FileKindSize
SKILL.mdskill md1.3 KB
scripts/resolve-markdown.mjsexecutablescript5.5 KB
---
name: loading-addressable-markdown
description: Use when a mission, slice, dashboard, or task references Markdown as path#h2-slug or path#h2-slug/h3-slug outside the OpenRig context-pack library.
---

# Loading Addressable Markdown

## Overview

Load exactly one addressed Markdown section from any filesystem tree. The resolver mirrors OpenRig's shipped H2/H3 grammar without requiring the file to live in the context library.

## Use

Run the bundled script. Relative file references resolve from `--root`; without it they resolve from the current directory.

```bash
node ~/.agents/skills/loading-addressable-markdown/scripts/resolve-markdown.mjs \
  --root /path/to/mission \
  'slices/09-source-cleanup/SPEC.md#proposal'
```

The accepted forms are:

- `file.md` — whole file
- `file.md#h2-slug` — full H2 span, including child sections
- `file.md#h2-slug/h3-slug` — full H3 span

Slugs are lowercase; Markdown emphasis/code markers are removed; each other non-alphanumeric run becomes `-`. Duplicate or missing paths fail loudly. Headings inside fenced code blocks are ignored.

## Common mistakes

- Do not use `rig context get` for an arbitrary filesystem path; that command resolves context-library refs.
- Do not hand-slice headings with `sed` or line numbers; the bundled resolver owns span and fence behavior.
- Quote addresses in shell commands.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall