agentleFS
Sign inStart free
malinskibeniaminmalinskibeniamin/skills/demo/SKILL.md

demo

Skill4 starsChanged 11 days agoMITView on GitHub

Create a customer-facing feature recording and publish it in a draft PR.

26 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use spec, implement and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    spec

    Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.

    Also in 4 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 4 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 24 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Keep sources/output in demos/<slug>/.

    line 14
  2. Very specific:

    Use a capture-first stack: real browser footage.

    line 15
  3. Distinctive:

    Keep muted playback understandable.

    line 18
  4. Distinctive:

    Never edit README. Honor local/no-push stops.

    line 20

“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “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

Turn finished work into customer proof. Read REFERENCE.md.

Contract

  1. Resolve target; default whole current branch/PR from merge-base: committed, staged, unstaged, relevant untracked.
  2. Tell one customer problem -> action -> payoff story.
  3. Keep sources/output in demos/<slug>/; reuse for updates.
  4. Use a capture-first stack: real browser footage; asciinema .cast terminal replays (not MP4). Follow recipes.
  5. Deliver output/demo.mp4 or output/index.html with assets; use the walkthrough scaffold. Label simulations/explanations, not recorded evidence.
  6. Compose optionally with existing HyperFrames; preserve existing Remotion sources. No second renderer for recordings.
  7. Keep muted playback understandable. Requested/source-required voiceover must align with actions, retain captions/transcripts, and pass listening checks. Cloud speech, cloned voices, and uploads require authorization.
  8. Inspect early/middle/late frames, full playback, and error paths; fix defects; redact secrets/private/customer PII. When motion adds no value, use an architecture diagram with accessible description and reason.
  9. Never edit README. Honor local/no-push stops; otherwise commit, push current branch, create draft PR with artifact link. Preserve existing PR review state.
  10. macOS: open -R; otherwise show pwd, absolute path, exact cd.

Done

Return story, artifact type/path, capture/render/playback evidence, limits, and PR URL when publication is in scope. Local output satisfies only an explicit local endpoint.

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