slide-page-splitter
Skill21 starsChanged 50 days agoNo licenceView on GitHub
The second leg of the slide-assistant three-leg relay: take the storyline approved by the previous leg (SLIDE_PACKET ▸ Storyline) and, following paging principles, slice it into a page-by-page slide list — deciding which beat each page maps to, what title it carries, how many bullet points it holds, and how dense its information should be. Trigger me immediately when the user hands over a ▸ Storyline handoff packet, or says 「幫我分頁」, 「把故事線切成投影片」, 「每頁放什麼」, 「規劃投影片頁數」, 「slide 分頁設定」. I only handle paging and per-page content allocation, handing off once ▸ Pages is produced; I do not design layout or visuals, nor render .pptx (that's slide-visual-selector and the slide-pptx skill), and I do not go back and rewrite the storyline (that's slide-storyline-designer).
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-pptxSkill
- slide-storyline-designerSkill
- slide-visual-selectorSkill
- social-publish-articleSkill
- zynkr-slideSkill
- 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
5 rules. About 0 are common, 3 are distinctive, and 2 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.
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 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.

