agentleFS
Sign inStart free
aakatheeriaakatheeri/narrative-deck/skill/SKILL.md

narrative-deck

Skill1 starsChanged 23 days agoMITView on GitHub

AI-agent skill for narrative interactive web presentations, pitch decks, explainers, reports, and scrollytelling pages in vanilla HTML/CSS/JS. Uses a nine-beat story frame and editorial effects to help assistants structure content, choose interactions, and produce responsive, dependency-free decks.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. anyreachai/claude-skills★ 1same name

    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 repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 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.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Does not: write content; export PDF/PPTX.

    line 20
  2. Very specific:

    Ask purpose/audience/tone.

    line 24
  3. Distinctive:

    Read only used effect references.

    line 57
  4. Very specific:

    Read prefers-reduced-motion once.

    line 61
  5. Very specific:

    Use IntersectionObserver; scroll math uses rAF + ticking + {passive:true}.

    line 62
  6. Distinctive:

    Kinetic type: headlines only: Never body copy.

    line 75
  7. Very specific:

    No dependencies: No build step, no framework, no package.json.

    line 76

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Narrative Deck

Nine-beat frame, fifteen effects, three templates. Placement beats spectacle.

Scope

Does: structure HTML decks; implement scroll/canvas effects.

Does not: write content; export PDF/PPTX.

Workflow

  1. Ask purpose/audience/tone; infer when clear.
  2. Shape story — read references/story-design.md.
  3. Map beats — read references/structure.md.
  4. Choose at most three effects — read references/placement.md.
  5. Confirm beats/effects.
  6. Start from ../templates/.
  7. Implement chosen references.
  8. Run references/checklist.md.

The Nine Beats

Hook → Setup → Inciting → Pinch 1 → Midpoint → Pinch 2 → PP2 → Climax → Resolution. See references/structure.md.

Effects

#EffectServesReference
01Scroll revealSetupreferences/01-reveal.md
02Sticky scrollytellingPinch 1references/02-scrolly.md
03Hover disclosureIncitingreferences/03-hover.md
04You Draw ItMidpointreferences/04-draw.md
05Physics fieldAmbientreferences/05-orbs.md
06Forensic annotationPinch 1 / PP2references/06-forensic.md
07Kinetic typeHook / Climaxreferences/07-type.md
08Parallax depthHookreferences/08-parallax.md
09Colour threadingThroughoutreferences/09-thread.md
10Binary quizMidpointreferences/10-quiz.md
11Turn-by-turnPinch 2references/11-proc.md
12Spatial viewerMidpointreferences/12-ar.md
13Before/afterInciting / Climaxreferences/13-ba.md
14Audio waveformPinch 2references/14-wave.md
15Paywall simulatorResolutionreferences/15-pw.md

Read only used effect references.

Architecture — Non-Negotiable

  1. Read prefers-reduced-motion once; animations jump to end.
  2. Use IntersectionObserver; scroll math uses rAF + ticking + {passive:true}.
  3. Gate canvas loops; max three active.
  4. Replay uses WAAPI with fill:'both' and cancel().
  5. Tokens follow brand/tone; ask if missing. See references/tokens.md.
  6. Hover reveals work on :focus-visible; use <button>, never <div>.
  7. Canvas scales by devicePixelRatio.
  8. Arrows/space advance slides; responsive from 360px.

Hard Limits

  • Three effects max. Four reads as showreel.
  • No climax effects. Spectacle competes with resolution.
  • Parallax: six layers maximum.
  • Kinetic type: headlines only. Never body copy.
  • No dependencies. No build step, no framework, no package.json.

Templates

FileShape
../templates/pitch.htmlproblem → solution → ask
../templates/explainer.htmlquestion → mechanism
../templates/report.htmlfinding → recommendation

Live Reference

../docs/index.html runs all effects with replay controls. Lift working code from there.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free