agentleFS
robotostudiorobotostudio/turbo-start-web-agent/.claude/skills/no-em-dash-copy/SKILL.md

no-em-dash-copy

Skill4 starsChanged 48 days agoMITView on GitHub

Use when writing, editing, or reviewing copy visitors read on this site. Use whenever page content, UI text, metadata, announcements, or blog posts are created or changed.

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:

    Never use the em dash character (—) in copy visitors read on this site.

    line 8

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

No em dashes in visitor-facing copy

Never use the em dash character (—) in copy visitors read on this site. Use commas, colons, semicolons, parentheses, or full stops instead.

Apply this rule to page content, UI labels, metadata, announcements, and blog posts. Before delivering any of those, search the changed text for em dashes, en dashes, spaced dashes, and double hyphens used as dashes. Rewrite each one naturally rather than replacing punctuation mechanically.

This rule does not apply to the repository's own documentation, commit messages, or pull request text. Those may continue to use em dashes.

This is a site-wide convention for visitor-facing copy, not a personal preference. It lives in the repository so every contributor and content-editing agent applies the same rule.

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.