zoranmarticzoranmartic/coord-wright/skills/coord-help/SKILL.md

coord-help

Skill0 starsChanged 47 days agoApache-2.0View on GitHub

Show help for a coord skill (parameters, examples) or list all coord-* skills with one-line descriptions. Read-only. Use when the user says "/coord-help", "/coord-help <name>", "what params does <skill> take", or "list coord skills".

Commits and pushes

In this repository20 other files it gives its agents.
- coord-archive-indexSkill
- coord-assignSkill
- coord-auditSkill
- coord-checkSkill
- coord-dirtySkill
- coord-discardSkill
- coord-initSkill
- coord-loop-doctorSkill
- coord-promoteSkill
- coord-refineSkill
- coord-requeueSkill
- coord-reviewSkill
- coord-shape-reviewSkill
- coord-shapeSkill
- coord-splitSkill
- coord-statusSkill
- coord-tokensSkill
- coord-unblockerSkill
- merge-to-mainSkill
- rebase-to-mainSkill

The file

We split this skill into the rules it gives an agent

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

≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Prefer ${COORD_TOOLS:-$HOME/Projects/coord-wright}/skills (canonical source).
line 22
Very specific:
If the skill maps to a coord subcommand, append a section:
line 36
Very specific:
If the named skill does not exist under the skills root, print: unknown skill: <name> and run the no-arg list form so the user sees what's …
line 50
Very specific:
Read-only; never call coord update, git add, git commit, or git push.
line 54
Very specific:
Do not summarise or paraphrase SKILL.md content — print it verbatim so users see the canonical text.
line 55

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

Display documentation for coord skills. Read-only — never mutates anything.

Project-root preflight:

Resolve the canonical project checkout before showing command-specific coord help: COORD_MAIN=$("${COORD_TOOLS:-$HOME/Projects/coord-wright}/bin/coord-project-root") && cd "$COORD_MAIN"
Generic skill-file help can be shown without changing directories, but any coord <subcommand> --help call should run from the main checkout.

Syntax

/coord-help → list all coord-* skills.
/coord-help <skill-name> → show full help for one skill.

Workflow

Locate the skills root.
- Prefer ${COORD_TOOLS:-$HOME/Projects/coord-wright}/skills (canonical source).
- Fall back to $HOME/.claude/skills if the canonical path is unavailable.
- Fall back to $HOME/.agents/skills if neither of the above exists (Codex runtime).
No-arg form: list mode.
- Enumerate every directory under the skills root whose name starts with coord-.
- For each, parse the description: line from SKILL.md frontmatter.
- Print one line per skill: /<name> — <description>.
- Sort alphabetically.
- End with a hint: Run /coord-help <name> for full help.
Single-arg form: detail mode.
- Accept the skill name with or without a leading / or coord- prefix; normalise to coord-<name>.
- Print the full body of SKILL.md (skip the frontmatter block).
- If the skill maps to a coord subcommand, append a section:
```
─── coord help ───
<output of: python3 "${COORD_TOOLS:-$HOME/Projects/coord-wright}/bin/coord" <subcommand> --help>
```
- Skill → coord subcommand mapping (use this when present, omit the section when the skill has no direct mapping):
  - coord-promote → promote
  - coord-assign, coord-requeue, coord-discard → update
  - coord-status → status
  - coord-split → new
  - coord-shape → new
  - coord-tokens, coord-check, coord-init, coord-refine, coord-help → no mapping
Unknown skill.
- If the named skill does not exist under the skills root, print: unknown skill: <name> and run the no-arg list form so the user sees what's available.

Rules

Read-only; never call coord update, git add, git commit, or git push.
Do not summarise or paraphrase SKILL.md content — print it verbatim so users see the canonical text.
Surface helper errors (missing file, coord non-zero exit) verbatim.

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