zynkr-slide
Skill21 starsChanged 50 days agoNo licenceView on GitHub
The conductor of the slide relay (sitting above the three-stage relay): fires when the user says '做一份簡報/做個 deck/幫我把這些做成投影片/做季報簡報/all-hands 簡報/deep dive 簡報/pitch deck'. I do a one-shot intelligent intake — detecting which kind of deck this is (deep-dive / business-review / data-presentation / all-hands / planning / pitch / update / teach / fundraise), taking stock of the material and storyline the user has already given, proposing a page count for the user to confirm, and gathering the must-include material and mode — then assembling a SLIDE_PACKET ▸ Brief and driving slide-storyline-designer → slide-page-splitter → slide-visual-selector → the slide-pptx skill in sequence to render the .pptx. Defaults to express mode (ask everything up front once, only asking the user to sign off at two points: storyline finalization and final file); pass the guided parameter to retain each stage's own per-stage human review. Scope boundary: I only do intent detection, context convergence, ▸ Brief injection, and relay orchestration; I don't lay out the narrative arc, split pages, choose layouts, or render the .pptx myself — those belong to the three stages and the slide-pptx skill respectively. In addition, if the user gives a fixed template (charter / one-page QBR / an existing deck to be re-skinned) or asks for a deliverable that maps onto the template library, I take the template-fill branch (copy template → extract content → fill fixed fields → recolor external templates to Zynkr brand colors by default) instead of the three-stage relay.
In this repository95 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- zynkr-content-writerCLAUDE.md
- planning-1on1-annual-digestSkill
- planning-evidence-packSkill
- planning-lob-gap-auditSkill
- planning-prework-packSkill
- planning-session-synthSkill
- planning-suite-reconcilerSkill
- planning-tracker-builderSkill
- planning-tracker-syncSkill
- zynkr-gmSkill
- content-fissionSkill
- content-governanceSkill
- content-newsletter-draftSkill
- content-translatorSkill
- seo-angle-finderSkill
- seo-article-finalizerSkill
- seo-article-pipelineSkill
- seo-brief-writerSkill
- seo-demand-validatorSkill
- seo-keyword-classifierSkill
- seo-keyword-mapperSkill
- seo-outline-designerSkill
- seo-persona-builderSkill
- seo-program-plannerSkill
- seo-publish-articleSkill
- seo-question-minerSkill
- slide-arch-diagramSkill
- slide-page-splitterSkill
- slide-pptxSkill
- slide-storyline-designerSkill
- slide-visual-selectorSkill
- social-publish-articleSkill
- consult-adoption-reporterSkill
- consult-brd-writerSkill
- consult-bug-ticketSkill
- consult-discoverySkill
- consult-flow-designSkill
- consult-governanceSkill
- consult-info-sessionSkill
- consult-intakeSkill
- consult-launch-commsSkill
- consult-project-specialistSkill
- consult-session-notesSkill
- consult-shadowing-schedulerSkill
- consult-solution-planningSkill
- consult-status-reportSkill
- consult-transcriberSkill
- consult-uat-writerSkill
- sales-client-sourcingSkill
- sales-follow-upSkill
- sales-managerSkill
- sales-outboundSkill
- sales-proposal-writerSkill
- sales-researchSkill
- sales-specialistSkill
- accupass-agentSkill
- admin-governanceSkill
- admin-meeting-prepSkill
- admin-video-documentSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 7 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
4
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.

