agentleFS
Sign inStart free
grasscaograssgrasscaograss/AwesomeWeldoneSkills/opsx-reindex/SKILL.md

opsx-reindex

Skill2 starsChanged 6 months agoApache-2.0View on GitHub

Regenerate openspec/INDEX.md after specs or changes are modified. Use when: (1) a change has been archived and the index is stale; (2) new capabilities or specs were added; (3) user says \"update index\", \"reindex openspec\", \"refresh INDEX.md\", \"index is out of date\", \"/opsx-reindex\". Runs opsx-reindex/scripts/reindex.py to rebuild the capability index from current specs, active changes, and archived changes.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    After archiving a change (e.g.

    line 16
  2. Distinctive:

    After adding new capabilities or specs

    line 17
  3. Distinctive:

    When the index appears stale or incomplete

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OpenSpec Reindex

Regenerate openspec/INDEX.md after specs or changes are modified.

When to Use

  • After archiving a change (e.g. with /opsx:archive)
  • After adding new capabilities or specs
  • When the index appears stale or incomplete

How to Run

Execute the bundled script:

python .agents/skills/opsx-reindex/scripts/reindex.py

What It Does

  1. Scans openspec/specs/*/ for all capabilities and extracts the ## Purpose line from spec.md
  2. Queries openspec list --json for active changes and maps them to their delta specs
  3. Scans openspec/changes/archive/*/ for archived changes and maps them to their specs
  4. Rebuilds openspec/INDEX.md with:
    • Categorized capability table (by domain: dual-arm, weld template, coarse positioning, etc.)
    • [A] = active changes, [N] = archived changes
    • Active changes summary table at the bottom

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free