grid-help
Skill4 starsChanged 8 days agoMITView on GitHub
Explain how to use the-grid (which slash command or subagent to reach for, orchestrators vs specialists, the four factories). Use when the user asks "how do I use the-grid", "what can I do here" or "how do I add a skill/agent/automation".
In this repository15 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- cavemanSkill
- gh-issues-by-severitySkill
- grill-meSkill
- growth-psychSkill
- handoffSkill
- mine-learningsSkill
- openspec-helpSkill
- rubber-duckSkill
- setup-repo-skillsSkill
- skill-scoutSkill
- spec-scoutSkill
- standupSkill
- tightenSkill
- un-claudishSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Very specific: line 14
Read sections/orientation.md for the summary to answer from.
- Distinctive: line 18
Don't reproduce their content — hand off:
- Distinctive: line 37
If the question is deeper than a pointer — which template to pick, how a pattern composes, how the delegation topology works — read the …
- Distinctive: line 43
Read a section only when its condition applies.
≈ “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.
Files
grid-help
A live, in-session guide to the-grid. Answer from the summary in sections/orientation.md; point to
USAGE.md (repo root) for the full walkthrough rather than
reproducing it verbatim — it changes independently of this skill.
Quick orientation
Read sections/orientation.md for the summary to answer from.
Sibling help skills
Don't reproduce their content — hand off:
| Command | Owns |
/openspec-help | The 12 openspec skills, spec format, adoption paths |
/ponytail-help | ponytail modes and intensity levels |
Answering well
- Give a pointer, not a tutorial. One or two lines plus the file to read.
- Check before asserting. SKILLS.md is generated and
current; your memory of what's wired is not. Same for which agents exist —
read
~/.claude/agents/. - Private projects: mechanism yes, names never. A machine may run a project
composed from roles outside this repo (
GRID_PRIVATE_ROLES_DIR, gated in gitignoredmachines/<host>.local.txt). Explain how that works to anyone who asks; never enumerate the roles of a private desk in this repo or in a shared session.
If the question is deeper than a pointer — which template to pick, how a pattern composes, how the delegation topology works — read the relevant section of USAGE.md, README.md, or CLAUDE.md rather than guessing.
Sections
Read a section only when its condition applies; do not preload them.
- sections/orientation.md: read before answering any question about using the-grid
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
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.

