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

check-continuity

Skill1 starsChanged 31 days agoMITView on GitHub

Check continuity across surfaces (pricing, plan names, terminology, feature names, promises) between marketing site, product, docs and emails, with actors walking each surface and mismatches reported with evidence.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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:

    Promise versus product: use an interview. create_interview(...) with a task that walks from the marketing claim into using the feature …

    line 10

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

Check continuity

  1. Context: list_workspaces(), list_projects(workspace_id). Match the surfaces to a project, or let create_checklist find or create it. Ensure a reviewer actor (list_actors, else create_actor).
  2. One checklist per surface with mirrored extraction checks so values compare cleanly: "Record the price, billing period and plan names shown", "Record what the main feature is called on this page". On the primary surface add cross-surface assertions such as "The price at checkout matches the pricing page".
  3. Promise versus product: use an interview. create_interview(...) with a task that walks from the marketing claim into using the feature ("The homepage says setup takes two minutes; sign up and see if that holds"), a persona participant, launch_interview, then get_interview_report.
  4. Run: run_checklist per surface, poll get_checklist_run until terminal, then compare recorded values.
  5. Report a discrepancy table (item, what each surface shows, which disagree, evidence), ranked by customer impact with billing mismatches first.
  6. Standing coverage: offer a scheduled create_workflow (see setup-guardrails).

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