agentleFS
lukashouthoofdlukashouthoofd/cenekathon/.agents/skills/demo-and-pitch/SKILL.md

demo-and-pitch

Skill1 starsChanged 15 days agoMITView on GitHub

Use in the last 90 minutes (from about 17:30) — freeze scope, script the demo, build the slides, rehearse the pitch for the 19:00 pitch block.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    17:30 feature freeze: Only bugfixes and demo polish after this.

    line 8
  2. Distinctive:

    Q&A prep: write 5 likely judge questions (tech choices, data, limits, business value, what if the model is wrong) with answers.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Demo & pitch

17:30 feature freeze. Only bugfixes and demo polish after this. Apply the cut line from docs/PLAN.md.

Demo script (docs/PITCH.md) — one happy path, ≤ 2 min, rehearsed 3×:

  1. Hook: one sentence on the person with the pain (a story, not a statistic).
  2. Show the magic moment live (fallback: recording).
  3. One line on how it works (architecture picture, ≤ 3 boxes).
  4. Honest status: what's real, what's mocked.
  5. Why it scales / what's next (3 bullets from deploy-fast).
  6. Closing line / ask.

Slides (max 5): Problem · Solution + demo · How it works (tech + AI) · Impact / scale · Team + next. Big text, one idea per slide; a screenshot beats a bullet list.

Rehearse: time it on a phone. Assign a speaker and a driver (hands on keyboard). Pre-load demo state, silence notifications, have the deployed URL and local fallback ready. Q&A prep: write 5 likely judge questions (tech choices, data, limits, business value, what if the model is wrong) with answers. Last check against the judging criteria in docs/CHALLENGE.md.

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.