agentleFS
Sign inStart free
stunt-doublestunt-double/stuntdouble-mcp/skills/run/SKILL.md

run

Skill1 starsChanged 31 days agoMITView on GitHub

Run a Stunt Double Studio checklist in a local Chrome with /stuntdouble:run <checklist> [resume]: an actor goes through localhost, staging or production, and the result comes back with each failed check's evidence and a viewer link.

45 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use init, report and 4 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.
  • MicrosoftSkill

    init

    Also in 4 projects that use this

  • MicrosoftSkill

    report

    Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 4 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 3 projects that use this

  • Hugging FaceSkill

    implement

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

    Also in 4 projects that use this

  • Microsoft AzureSkill

    verify

    End-to-end app testing pipeline for browser-based web apps on cloud browsers via Azure Playwright Workspaces: verify the live app, author tests for working flows, heal failing tests, then re-run with video and produce one consolidated report. Three phases (app verification, test authoring, test healing) plus a scoped final sanity run; each phase emits a sub-report. Use when asked to "verify my app", "make sure my app works and has good test coverage", "do a full QA pass", "add tests where I'm missing coverage", "fix failing tests and add new ones", "smoke test before deploy", "QA my deployment", or any combined verify-and-test ask. Requires Azure CLI (`az login`) and a Playwright Workspace resource ID — bootstraps configs on first invocation. Browser-based web apps with Playwright only — not for unit/API tests, native mobile/desktop, load/perf, or full accessibility audits.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 41 edited versions we read keep these.

  • 0

    Distinctive

    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:

    If the actor ends without finish_run (or was interrupted), start_run(checklist, resume: true) carries on with the run still open, and its …

    line 18

“Common” is measured: kept by at least 6 in 10 of the 41 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

Stunt Double Studio: run

/stuntdouble:run <checklist> [resume], one of the Studio skills (/stuntdouble:setup, /stuntdouble:run, /stuntdouble:open, /stuntdouble:cloud and /stuntdouble:doctor). Local runs use the person's own Claude plan: this session is the actor, and the plugin's local MCP server (npx stuntdouble@0.1.3 mcp) only drives a local Chrome, writes files and serves the viewer. Nothing else calls a model, and no account is needed. Say so before the first run in a session.

The local server ships only in the Claude Code plugin. Where its tools are missing, use the cloud skills. With no .stuntdouble/stuntdouble.json, offer /stuntdouble:setup first. To fix a field start_run names, the file format is in the setup skill's files.md (../setup/files.md from this skill's folder).

  1. start_run(checklist, resume?), with resume: true when asked. Fix any field it names and call again.
  2. Print only the viewer link from its output: the person can watch the run and stop it there.
  3. Dispatch the stuntdouble:stuntdouble-actor agent with the full start_run output as its prompt. Never drive the browser from this thread: page text and screenshots stay in the actor's context.
  4. Lead with the result from its reply: "Failed: 3 of 4 checks passed", then the score, or "no score" where score is null, explained in one clause (the checklist has no weighted checks, so it passes only when every pass/fail check passes). Then each failed and not-judged check with its evidence, and the viewer link. Say the verdicts are self-judged; a cloud run adds an independent judge. Offer to fix what failed and run again.

If the actor ends without finish_run (or was interrupted), start_run(checklist, resume: true) carries on with the run still open, and its output is the brief for a fresh dispatch: recorded verdicts stand. If the session closed mid-run, /stuntdouble:run <checklist> resume judges only the checks left.

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