gtm-audit-pdf
Skill1 starsChanged 7 months agoNo licenceView on GitHub
Generate a polished editorial-style multi-page PDF brief from the JSON output of a GTM stack audit — produces an 8-page landscape board memo using the Anyreach editorial design system (Fraunces serif, cream + ink alternation, indigo + lime accents). Use whenever the user wants a static PDF, deck, brief, or shareable document version of a GTM audit run. Trigger on "generate the audit PDF", "build a deck for the audit", "turn this into a brief", "make a PDF version of the audit", "shareable doc for the audit findings", "investor doc for the audit", "board memo for the GTM audit", or whenever GTM audit JSON output (findings.json, tactics.json, run_summary.json, strategy.md) is provided with a request for a static deliverable. Trigger even for partial requests like "put this in a doc". Do NOT trigger for interactive/JSX prototypes — use gtm-audit-app for those. Depends on the anyreach-deck skill being installed; imports tokens, components, and rendering pipeline from there.
In this repository40 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- account-brief-generatorSkill
- ai-fluency-assessmentSkill
- anyreach-deck-pptxSkill
- anyreach-financial-reportSkill
- anyreach-funnel-analysisSkill
- anyreach-web-designSkill
- bpo-partner-pitch-deckSkill
- bpo-roi-briefSkill
- bpo-roi-internal-briefingSkill
- bpo-roi-modelSkill
- brand-style-extractorSkill
- callsSkill
- company-deep-researchSkill
- competitor-deep-diveSkill
- consumer-intelligence-xlsxSkill
- consumer-intel-reportSkill
- cx-intel-report-pdfSkill
- cx-intel-report-xlsxSkill
- demo-bot-usage-reportSkill
- deploy-intelSkill
- discovery-dashboardSkill
- discovery-to-proposalSkill
- gtm-audit-appSkill
- gtm-stack-auditSkill
- legal-reviewSkill
- leverage-analysisSkill
- maturity-assessmentSkill
- meeting-recap-emailSkill
- narrative-deckSkill
- portfolio-cx-briefSkill
- product-site-frameworkSkill
- proposal-sow-generatorSkill
- remotion-best-practicesSkill
- reviews-vs-live-callsSkill
- richard-thought-leadershipSkill
- shadcn-deckSkill
- stakeholder-intelSkill
- status-deckSkill
- visual-briefSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 364,980 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.

