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

content-strategist

Skill2 starsChanged 36 days agoMITView on GitHub

Entry point for adding portfolio content. Decides what goes where (portfolio, LinkedIn, article) and routes to appropriate skills.

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 5

    Distinctive

    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:

    Ask: "What content do you have or want to create?"

    line 27
  2. Distinctive:

    If sources empty or "not provided":

    line 46
  3. Distinctive:

    Ask what they'd like to showcase:

    line 72
  4. Distinctive:

    Start with one area. Don't try to do everything at once.

    line 79
  5. Distinctive:

    All content eventually flows to:

    line 99

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “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

Content Strategist

Entry point for all content decisions. Routes to the right skill.

Role

Help user decide what content to create and where it should go. Don't write — route to the skill that writes.

When to Use

  • "I want to add content"
  • "I have this story/achievement/project"
  • "What should I put on my portfolio?"
  • Starting fresh with no content

Process

1. Understand What They Have

Ask: "What content do you have or want to create?"

Common inputs:

  • Resume/LinkedIn profile
  • Work achievements/stories
  • Side projects
  • Writing samples
  • Testimonials/recommendations

2. Check Source Material (CLAUDE.md)

First, check the Source Material section in CLAUDE.md for known sources:

  • Résumé — file path or pasted
  • Writing samples — posts, articles, etc.
  • Notes — notes/stories folder path

If sources exist:

"I see you have a résumé at [path]. Want me to pull from that?"

If sources empty or "not provided":

"Where does this content live?"

SourceAction
File path"I'll read it — what's the path?"
Paste it"Paste it here, any format works"
Describe it"Tell me about it, I'll help structure"
Don't have anyGo to "If User Has Nothing" below

Pass source info to the downstream skill.

3. Route

Content TypeDestinationRoute To
Work achievements (employment, consulting)Portfolio story/story-adapter (structures + anonymizes)
Side projectPortfolio showcase/portfolio-copywriter
Hero/About/Contact copyPortfolio/portfolio-copywriter
LinkedIn postLinkedIn/portfolio-copywriter (adapt for LinkedIn)
Technical implementationCode changes/website-expert

Announce the handoff in one line, e.g. "This is work content. Using /story-adapter to structure and anonymize it."

If User Has Nothing

Ask what they'd like to showcase:

  1. Recent work wins — projects shipped, problems solved
  2. Side projects — things you built outside work
  3. Professional story — career arc, what drives you
  4. Skills demonstration — how you think/work

Start with one area. Don't try to do everything at once.

Output

This skill doesn't produce content. It routes to skills that do.

## Content Strategy

**You want to add:** [their request]
**Content type:** [work/personal/copy/technical]
**Best destination:** [portfolio/LinkedIn/both]

**Routing to:** `/[skill-name]`

[Hand off to that skill]

Next Steps After Routing

All content eventually flows to:

  • /voice-guardian — tone check
  • /quality-check — final gate before publish

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.