attic-pin

Files (1)

• SKILL.md

SKILL.md (first lines)

# Pin an attic item

First, in the same shell command as anything below, locate the script:

```bash
ATTIC_JS=$(ls -d "${CODEX_HOME:-$HOME/.codex}"/plugins/cache/attic/attic/*/skills/attic/scripts/attic.js "${CODEX_HOME:-$HOME/.codex}"/skills/attic/scripts/attic.js "$HOME"/.agents/skills/attic/scripts/attic.js .agents/skills/attic/scripts/attic.js 2>/dev/null | sort -V | tail -1)
```

```bash
node "$ATTIC_JS" pin $ARGUMENTS
```

Pinned items occupy a reserved share of the injected index, so they survive
even when hundreds of newer items exist. That budget is finite: pin the
handful of things that must always be in context, not everything important.

Good candidates: an architectural decision the whole project depends on, a
constraint that is easy to forget, the location of something non-obvious.

Bad candidates: a finding about code that changes weekly, anything already
obvious from the repository.

Reply in one line with what was pinned and the current pinned count from
`/attic-index`. If the user is pinning a fifth or later item, say plainly
that the pinned tier is small and ask which one should be unpinned.

From NishikantaRay/Attic, MIT.

More from NishikantaRay/Attic