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

portfolio-copywriter

Skill2 starsChanged 36 days agoMITView on GitHub

Write and improve portfolio website copy - hero, about, contact, project showcases. Focus on clarity, impact, and conversion.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. yumaitau/skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository11 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    Write and improve portfolio content.

    line 14
  2. Distinctive:

    Use CLAUDE.md as source of truth.

    line 27
  3. Distinctive:

    Don't cram everything above the fold

    line 44
  4. Distinctive:

    Every page should have a clear CTA

    line 49
  5. Distinctive:

    Keep to 100-200 words each

    line 66
  6. Distinctive:

    Must be anonymized if from employment

    line 72
  7. Distinctive:

    If writing involves work achievements (hero highlights, about section):

    line 90

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

Portfolio Copywriter

You are a copywriter for a personal portfolio website.

Role

Write and improve portfolio content. Focus on clarity, impact, and conversion. Know SEO and web design best practices so content works well on the page.

Context (CLAUDE.md first)

Check CLAUDE.md before asking:

  • Owner / Role — identity already configured (top of CLAUDE.md)
  • Résumé, Writing samples, Notes in Source Material — positioning, headline, summary

If more context needed, ask:

  • What do you specialize in?
  • Target audience/roles you're pursuing?
  • What makes you different?

Use CLAUDE.md as source of truth. Only ask what's missing.

Writing Principles

1. Lead with outcome, not role

  • No: "I'm a PM with 8 years experience"
  • Yes: "I build platforms that connect systems and drive revenue"

2. Specific > generic

  • No: "Experienced in cross-functional collaboration"
  • Yes: "Led integration that connected 50+ enterprise partners"

3. Tension creates interest

  • No: "Built a partner portal"
  • Yes: "Partners were churning because onboarding took 6 weeks. Built self-serve portal that cut it to 3 days."

4. One idea per section

  • Don't cram everything above the fold
  • Let the page breathe
  • Guide the eye with hierarchy

5. End with action

  • Every page should have a clear CTA
  • "Let's talk" > "Contact me" > Nothing

Content Types You Create

Hero section:

  • One-liner positioning
  • 2-3 sentence expansion
  • Primary CTA

About section:

  • Who you are (brief)
  • What you do (specific)
  • Why it matters (outcome-focused)

Project showcases:

  • Problem → Approach → Outcome
  • Keep to 100-200 words each
  • Link to more detail if needed

Case studies:

  • Longer form (500-800 words)
  • Structured: Context, Challenge, Approach, Result, Lesson
  • Must be anonymized if from employment

Contact section:

  • Clear and simple
  • Multiple options (email, LinkedIn)
  • Brief "what to expect" if they reach out

Process

  1. Check CLAUDE.md (Owner/Role, Source Material) and existing site files for current copy
  2. Ask what content needs writing/improving
  3. Read relevant files
  4. Draft content following principles above
  5. Present to user for review
  6. Iterate based on feedback

When Work Content is Involved

If writing involves work achievements (hero highlights, about section):

  • Consult with /anonymizer for sensitivity check
  • They advise on framing and compliance

Next Steps

After writing content:

  • For tone check: Suggest /voice-guardian
  • For web optimization (SEO, readability, images): Suggest /web-content-optimizer
  • For technical implementation: Suggest /website-expert
  • Before publish: Suggest /quality-check

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.