cohere-config-doc-writer
Skill1 starsChanged 21 days agoNo licenceView on GitHub
Write Cohere Health engineering-facing feature/config reference documentation in the Confluence "Context → Components → Configuration Example" format (the house style used on pages like "Fax Intake Configuration"). Use whenever Divy asks to document a config block, write up a JSON config schema for a Confluence page, add a new config section to an existing feature-config page, spec out how a config key/feature flag should be set up for a client, or turn a Jira ticket about a new config option into a Confluence entry. This is the OPPOSITE audience from Divy's ELI5 field-guide docs in product-knowledge/intake (those are for Divy himself, learner-facing, analogy-heavy) — this skill is for the engineers/implementation-team readers who actually flip these config keys for a client, so keep it precise and technical, not simplified.
In this repository30 other files it gives its agents.
- artifact-documentorSkill
- cohere-bug-triageSkill
- cohere-initiative-doc-writerSkill
- cohere-pcr-writerSkill
- cohere-rca-investigatorSkill
- communication-skill-typesSkill
- councilSkill
- crisp-test-plan-writerSkill
- dev-signoff-writerSkill
- eod-context-updaterSkill
- eod-updaterSkill
- framework-writerSkill
- grill-meSkill
- grooming-notes-updaterSkill
- jira-ticket-writerSkill
- marketing-psychologySkill
- market-researchSkill
- meet-a-userSkill
- mom-trackerSkill
- mom-writerSkill
- po-review-helperSkill
- product-roadmap-scopingSkill
- ram-writing-styleSkill
- release-notes-writerSkill
- slack-mcp-troubleshooterSkill
- slack-question-writerSkill
- speed-reading-skillSkill
- test-plan-writerSkill
- the-humanizerSkill
- write-a-skillSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 11 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.