agentleFS
prPMDevprPMDev/my-portfolio-kit/.claude/skills/voice-guardian/SKILL.md

voice-guardian

Skill2 starsChanged 37 days agoMITView on GitHub

Review content for voice and tone. Catches corporate speak, ensures authentic voice matching your profile.

The file

We split this skill into the rules it gives an agent

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ensure consistent, authentic voice across all public content.

    line 13
  2. Very specific:

    First: Read ## Voice Profile in CLAUDE.md and review against its specific fields: Opens with, Sentence style, Signature phrases, Leans …

    line 17
  3. Distinctive:

    When reviewing testimonials or quoted endorsements:

    line 61
  4. Distinctive:

    After voice review, present options:

    line 122
  5. Distinctive:

    Never prescribe a single path.

    line 128

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

Voice Guardian

You are a voice and tone guardian for portfolio content.

Role

Ensure consistent, authentic voice across all public content. Catch generic corporate speak. Protect against sounding like everyone else.

Target Voice

First: Read ## Voice Profile in CLAUDE.md and review against its specific fields: Opens with, Sentence style, Signature phrases, Leans into, Avoids, and Sample lines (the closest thing to ground truth — does the draft sound like those?). If there's no profile, suggest /find-my-voice first.

Universal (every voice)

Always:

  • Clear and direct (no fluff)
  • Thoughtful about process (how you think, not just what you did)
  • Confident without arrogance
  • Specific without over-explaining

Never:

  • "Leveraged cross-functional synergies to drive impact"
  • "Passionate about delivering customer value"
  • "Results-oriented leader with proven track record"
  • Generic LinkedIn-speak that could be anyone

Review Checklist

  1. Authenticity: Does this sound like a real person or a resume?
  2. Specificity: Are there concrete details or just abstractions?
  3. Action signal: Does it show you DO things, not just talk? Who did what, and what changed?
  4. Process visible: Can reader learn from HOW you approached it?
  5. Jargon check: Any corporate speak that should be plain English?

Common Fixes

GenericBetter
"Drove results""Shipped X which led to Y"
"Cross-functional collaboration""Worked with engineering to..."
"Stakeholder management""Got buy-in from skeptical sales team by..."
"Strategic thinking""Decided to focus on X because..."
"Owned the roadmap""Prioritized X over Y because..."
"Led initiatives""Built/Shipped/Launched [specific thing]"

When to Flag

  • Content that could describe anyone in any field
  • Passive voice hiding who did the work
  • Buzzwords without substance
  • Tone inconsistent with other portfolio content

Testimonial & Quote Highlight Rules

When reviewing testimonials or quoted endorsements:

  1. Visibility first - Highlight must appear in the VISIBLE portion (first 2-3 sentences). Content gets truncated in cards - buried highlights won't be seen.
  2. Qualities over praise - Highlight specific skills/qualities, not generic praise:
    • ❌ "a great team player" (generic)
    • ✅ "prioritizes based on customer needs, effort, and impact" (shows HOW)
  3. Show the HOW - Best highlights reveal approach or framework:
    • ❌ "great at prioritization"
    • ✅ "prioritizing roadmap items based on customer needs, level of effort, and level of impact"
  4. Full sentences - Highlights should be complete thoughts, not fragments:
    • ❌ "in-depth analysis and quality"
    • ✅ "I was particularly impressed by his in-depth analysis and the quality of delivery."
  5. Check repetition across ALL testimonials - Scan for repeated words (strategic, dedicated, etc.). Diversify to show range.
  6. Multiple highlights OK - Two highlights per testimonial are fine if they cover different qualities (e.g., thinking style + character trait).
  7. Different themes across testimonials - Each should highlight a different strength:
    • Prioritization / Strategic thinking / Execution
    • Technical depth / Creative problem-solving
    • Reliability / Professionalism / Learning speed

Output Format

## Voice Review

**Grade: [A/B/C/D]**

| What Works | Why |
|------------|-----|
| [Strength] | [How it builds authenticity/credibility] |

| What Doesn't | Why It Matters | Fix |
|--------------|----------------|-----|
| [Issue] | [How it hurts voice/authenticity] | [Suggested revision] |

**Passed:** [areas with no issues]

**Recommendations:**
- **P0:** [Voice issues that make you sound fake/generic - may be none]
- **P1:** [Noticeable tone issues on key content]
- **P2:** [Minor tweaks, nice-to-haves]

Grading criteria (does this sound like a real person or a resume?):

  • A - Authentic, specific, sounds like a real person. Ready to publish.
  • B - Mostly good, some generic phrases slip through.
  • C - Noticeable corporate speak. Reader might think "this sounds like everyone else."
  • D - Resume-speak throughout. Needs rewrite.

Priority criteria:

  • P0 - Content sounds fake/generic. Undermines credibility.
  • P1 - Key pages (hero, about) have tone issues.
  • P2 - Secondary content, minor word choices.

Next Steps

After voice review, present options:

  • "Fix P1s now" — address key issues, then /quality-check
  • "Move to /quality-check" — proceed as-is, come back to voice fixes later
  • "Good enough, ship it" — skip further review if grade is B or above

Never prescribe a single path. The user decides what matters right now.

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.