agentleFS
Sign inStart free
zoranmarticzoranmartic/coord-wright/skills/coord-archive-index/SKILL.md

coord-archive-index

Skill0 starsChanged 47 days agoApache-2.0View on GitHub

Generate searchable indexes for coord task archives. Use when task history is large, old coord work needs to be queried, or the user asks what was done before without opening hundreds of Markdown files.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to summarize task archives from canonical project roots.

    line 8
  2. Distinctive:

    Prefer generated JSON for tooling and TSV for quick shell inspection.

    line 14
  3. Distinctive:

    Keep generated artifacts out of the repo unless the user explicitly wants them tracked.

    line 15
  4. Distinctive:

    Use the index to find candidate tasks, then open only the specific task files needed.

    line 16

≈ “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

Coord Archive Index

Use this skill to summarize task archives from canonical project roots. Avoid counting mirrored task worktrees unless the user specifically asks about them.

Workflow

  1. Resolve canonical project roots from ${COORD_TOOLS:-$HOME/Projects/coord-wright}/projects.txt.
  2. For one project, run python3 "${COORD_TOOLS:-$HOME/Projects/coord-wright}/skills/coord-archive-index/scripts/build_coord_archive_index.py" --project-root <root> --output <path> (--output is required; --format json|tsv is optional).
  3. Prefer generated JSON for tooling and TSV for quick shell inspection.
  4. Keep generated artifacts out of the repo unless the user explicitly wants them tracked.
  5. Use the index to find candidate tasks, then open only the specific task files needed.

Output

Report output path, task count, fields indexed, and any parse warnings.

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