agentleFS
stunt-doublestunt-double/stuntdouble-mcp/skills/check-brand/SKILL.md

check-brand

Skill1 starsChanged 33 days agoMITView on GitHub

Audit a product or site against brand and tone-of-voice guidelines, with an actor reading every in-scope page like a customer and flagging copy, voice and presentation that break the rules, with evidence.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No guidelines supplied: ask, or draft a short rule set from the strongest existing pages and confirm it before auditing.

    line 13

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

  1. Context: list_workspaces(), list_projects(workspace_id). Match the URL to a project, or let create_checklist find or create it.
  2. Actor and rules:
    • list_actors(workspace_id), else create_actor(...) described as a meticulous brand and copy reviewer.
    • list_workspace_guidelines(workspace_id): if the standard exists, attach it with set_project_guideline(project_id, guideline_id) rather than typing a second copy. Otherwise add_project_guideline(project_id, category: "tone_of_voice" | "brand", content, title), one rule per guideline so a finding can name the rule it breaks. Guidelines reach every run, review, interview and triage for the project.
    • add_actor_knowledge is for what only this reviewer needs, not the standard itself.
    • No guidelines supplied: ask, or draft a short rule set from the strongest existing pages and confirm it before auditing.
  3. One checklist per surface (default: homepage, one core flow, one high-traffic marketing page) with 4 to 8 reader-observable checks, e.g. "Headlines use sentence case", "Error messages state what happened and offer a next step". Actors see the rendered page, so never phrase checks by CSS or component names.
  4. Run: run_checklist(checklist_id), poll get_checklist_run(run_id) until terminal, read evidence per check.
  5. Report deviations grouped by page: the broken rule, the offending copy as evidence, and a suggested rewrite in the correct voice.
  6. Standing coverage: offer create_workflow on a schedule or deploy trigger (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.