agentleFS
Sign inStart free
KhaledSaeed18KhaledSaeed18/deck-kit/.agents/skills/ship-deck/SKILL.md

ship-deck

Skill0 starsChanged 12 days agoMITView on GitHub

Final verification and packaging for this deck kit: runs every check, builds the single-file deck, the PDFs and the presenter script, and lists what to take to the room with the fallback order. Use when the talk is ready, before presenting, or when the user asks to export, build, package, or \"get it ready for the USB stick\".

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run, in order, and stop at the first failure (show its output, fix it if it is clearly mechanical, otherwise report):

    line 8
  2. Very specific:

    Check that nothing is pending: no data-todo (the lint fails on them), every flag in docs/plan.md has an answer in docs/decisions.md, and …

    line 17
  3. Distinctive:

    Commit or tag only if the speaker asks.

    line 36

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

Ship the deck

  1. Run, in order, and stop at the first failure (show its output, fix it if it is clearly mechanical, otherwise report):
    • pnpm check
    • pnpm test:e2e (engine suite on the example, plus your deck in a real browser, all with the network blocked)
    • pnpm build:single, which writes dist-single/deck.html
    • pnpm pdf, which writes out/deck-<profile>.pdf for every profile
    • pnpm notes:pdf (and pnpm notes:pdf <profile> for each other profile the speaker might give), which writes out/presenter-script-<profile>.pdf
  2. Check that nothing is pending: no data-todo (the lint fails on them), every flag in docs/plan.md has an answer in docs/decisions.md, and the profile times fit the slot.
  3. Collect the files to take to the room into out/usb/:
    • deck.html (from dist-single/)
    • deck-<profile>.pdf for each profile
    • the presenter script PDF(s)
    • a copy of dist/ as dist/ (for the static-server option)
  4. Tell the speaker the fallback order, and the keys that matter on the day:
    1. pnpm preview (or python3 -m http.server -d dist), open the deck, press P for the presenter window, and move it to the laptop screen
    2. deck.html from the USB stick by double-click; P opens the presenter (deck.html?role=presenter)
    3. the PDF Keys: F fullscreen, P presenter, B blackout, O overview, a number then Enter to jump, H to hide the progress bar. Clickers send PageUp/PageDown, which work. Add ?profile=<name> for a shorter version.
  5. Suggest one full rehearsal with the presenter timer running; the pace line shows whether they are ahead or behind each slide's plan.

Commit or tag only if the speaker asks.

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