doc-writer
Skill1 starsChanged 4 months agoNo licenceView on GitHub
Write the long-form Markdown document behind a customer engagement -- the detailed writeup that an exec PDF, slide deck, or Google Doc is later cut from. Use when Craig says: write this up, build out a one pager, I need a doc for this customer, turn this into an actionable google doc, make the doc look nice with spectro branding, we need a migration plan (VMware or existing K8s to Palette), start a new doc to piece together why spectro and where our gaps are, write the postmortem / RCA / POC report / assessment / solution brief / architecture writeup. Also use for the detailed .md that feeds exec-doc-generator, where the markdown carries all the detail and the PDF is the 1-2 pager. Owns long-form writeups only -- for a 1-2 page executive PDF use exec-doc-generator, for a multi-page docs site use docs-site-generator, and for a slide deck (rendered PDF or a Google Slides link) use slide-deck-generator. See this skill's Deliverable Routing table for all four.
20 other projects use a version of this.
Adopted by
Most recently taken up by
- ayushgoel/skillstheir own version, first seen Nov 5, 2026
- k1lgor/virtual-companytheir own version, first seen Nov 1, 2026
- claude-world/director-mode-litetheir own version, first seen Nov 1, 2026
- TaiMaBenJi/taima-skillstheir own version, first seen Oct 11, 2026
- redai-infra/Relaxtheir own version, first seen Oct 8, 2026
- mitchdenny/hex1btheir own version, first seen Oct 8, 2026
Used with
Projects with it also use code-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions20 projects use a version of this.
Word for word · 1
- nctiggy/claude-skills★ 1100% same
Edited · 0
None found.
Wrote their own version · 19
- microsoft/vscode-docs★ 6.7ksame name
- redai-infra/Relax★ 675same name
- microsoft/aspire.dev★ 202same name
- mitchdenny/hex1b★ 182same name
- claude-world/director-mode-lite★ 80same name
- zeroclaw-labs/zeroclaw-skills★ 65same name
- nimbalyst/skills★ 28same name
- k1lgor/virtual-company★ 4same name
- dqtx760/skills-manage★ 2same name
- GeziP/doc-wiki★ 2same name
9 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- architecture-diagramsSkill
- craigcloud-designSkill
- docs-site-generatorSkill
- example-skillSkill
- exec-doc-generatorSkill
- ralph-ready-planningSkill
- rvtools-consolidationSkill
- slide-deck-generatorSkill
- spectrocloud-agent-modeSkill
- spectrocloud-appliance-modeSkill
- spectrocloud-brandSkill
- spectrocloud-cluster-profilesSkill
- spectrocloud-clustersSkill
- spectrocloud-commonSkill
- spectrocloud-docs-siteSkill
- spectrocloud-maas-edgeSkill
- spectrocloud-packsSkill
- spectrocloud-poc-docsSkill
- spectrocloud-promptsSkill
- spectrocloud-terraformSkill
- spectrocloud-troubleshootingSkill
- spectrocloud-web-uiSkill
- superSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
2
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 measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “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.