agentleFS
Sign inStart free
juanitourquizajuanitourquiza/shipframe/skills/client-copy-review/SKILL.md

client-copy-review

Skill4 starsChanged 22 days agoMITView on GitHub

Review product copy, i18n, email, and landing text for clarity, approvals, and implementation-safe wording.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Use before changing visible product text, emails, landing pages, app UI labels, or client-approved copy.

    line 11
  2. Distinctive:

    If the project is bilingual or localized, update every required locale together.

    line 16
  3. Distinctive:

    Do not present planned, demo, experimental, or partially shipped work as released.

    line 18
  4. Distinctive:

    Prefer paste-ready final wording.

    line 19

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

Client Copy Review

Use before changing visible product text, emails, landing pages, app UI labels, or client-approved copy.

Rules

  • Preserve explicitly approved copy verbatim unless the user asks to revise it.
  • If the project is bilingual or localized, update every required locale together.
  • Separate factual claims, marketing claims, and implementation status.
  • Do not present planned, demo, experimental, or partially shipped work as released.
  • Prefer paste-ready final wording.

Output

## Client Copy Review

**Files/areas checked:** <paths>
**Languages:** <languages>

### Recommended copy
<final wording>

### Consistency checks
- ✅/⚠️ <i18n, tone, legal/safety, approval status>

### Implementation notes
- <where to update>

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