exec-doc-generator
Skill1 starsChanged 4 months agoNo licenceView on GitHub
Generate a polished 1-2 page executive PDF (HTML rendered via Puppeteer) merging customer brand colors with Spectro Cloud branding -- pinned footers, stat cards, timelines. Also answers to exec-doc and exec-docs. Use when Craig says: I need a one pager for this customer, make it a 1-2 pager PDF for executive reading, not deep technical, an exec summary of this, a brief one pager that hammers home the selling points, do not be verbose, a nice looking PDF for their leadership, a POC overview or solution summary for the exec audience. Typically follows doc-writer or a postmortem: the markdown holds all the detail, this is the two pages an executive actually reads. Owns the short executive PDF only -- for a long-form writeup use doc-writer, 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 the Deliverable Routing table in doc-writer.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- nctiggy/claude-skillsword for word, first seen Jul 10, 2026
Other versions1 project uses a version of this.
Word for word · 1
- nctiggy/claude-skills★ 1100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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
- doc-writerSkill
- example-skillSkill
- 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
11 rules. About 0 are common, 3 are distinctive, and 8 are 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.
8
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.