crew-role-content
Skill16 starsChanged 31 days agoApache-2.0View on GitHub
Crew content pass: posts, reports, video, pages and social on a crew card; rendered artifact plus source.
In this repository4 other files it gives its agents.
- crew-diagnoseSkill
- crew-role-workerSkill
- crewSkill
- crew-verifierSkill
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
- Very specific: line 12
Read the card: GOAL, Done when, the Verify: line, target channel and format.
- Distinctive: line 32
Use a number that is not computed or cited.
- Distinctive: line 33
Put internal data in anything outward-facing.
≈ “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
Crew content pass
Loaded on a crew card whose role is content (posts, reports, video, pages, every social channel).
Do
- Read the card: GOAL,
Done when, theVerify:line, target channel and format. - Produce the artifact and keep its raw source next to it. Read every entry of the card's
Inputs(paths, URLs, quoted text) before you start; the result is checked against them as well asDone when. A proof script the proof command names (<folder>/.crew/<card folder>/verify.py) belongs to the verifier: you never create, edit or delete anything under.crew/(the plugin refuses it; reading is fine), and the script may not exist yet. Fix the work, not the proof. - Render it the way the reader will see it (image, page, preview) and check the render yourself.
- A card whose proof command runs a
.crew/script isVerify: independentand its script is the verifier's to write: skip the verdict and go to step 5 (kanban_request_review). Otherwise run the card's proof through the tool, never by hand, so the PASS/FAIL line lands in the verdict log:crew_verdict(card="<card id>")(the proof command the card was opened with; editing the line on the card changes nothing). A"verdict": "BLOCKED"result means Hermes safety refused the proof and nothing ran (no verdict line):kanban_blockwith kindneeds_inputand theblockedreason. - Finish with the rendered artifact path, the source path and any figures with their source, by the
Verify:line:proof-kanban_completeafter the PASS (no verifier session;kanban_request_reviewis refused; the coordinator runs the proof once more afterwards);independent-kanban_request_review, neverkanban_complete;closeout(a part of a split, no proof of its own) -kanban_completewith the paths.
Never
- Publish or send without the owner's approval on the card.
- Use a number that is not computed or cited.
- Put internal data in anything outward-facing.
- Edit a skill file (crew's skills are shipped and overwritten on update). A lesson worth keeping:
crew_lesson(role=<role>, text="...")(role = who it applies to: worker, content, verifier, coordinator or all).
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.

