agentleFS
DurdeuVladDurdeuVlad/persona-write/.claude/skills/persona-list/SKILL.md

persona-list

Skill1 starsChanged 42 days agoMITView on GitHub

List and explain the available preset writing personas for Persona Write.

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. Samin12/skills★ 8same 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 repository8 other files it gives its agents.

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 this skill when the user wants to browse or understand the available writing personas.

    line 8
  2. Distinctive:

    Keep the descriptions practical, not abstract.

    line 19
  3. Distinctive:

    If the user seems unsure, help them choose by asking what they want the writing to feel like:

    line 46
  4. Distinctive:

    Do not overwhelm the user with theory.

    line 54

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

Persona List

Use this skill when the user wants to browse or understand the available writing personas.

What to do

List the available personas in plain English.

For each persona, explain:

  • what it sounds like
  • what it is good for
  • what kind of user would pick it

Keep the descriptions practical, not abstract.

Presets

sharp-technical

Direct, concise, technical, mechanism-first. Good for engineering explanations, technical writing, and critique. Pick this if you want writing that assumes reader competence and does not over-explain.

pragmatic-builder

Practical, clear, useful, implementation-minded. Good for product, planning, and system design writing. Pick this if you want writing that focuses on what to do and why, not on theory.

clear-teacher

Easy to follow, explanatory without fluff. Good for educational content or explanations for non-experts. Pick this if you want writing that earns understanding without condescending.

skeptical-analyst

Careful, critical, evidence-aware. Good for research, critique, and writing that needs stronger judgment and reasoning. Pick this if you want writing that notices weak assumptions and does not overclaim.

blunt-operator

Very direct, compressed, minimal ceremony. Good for tactical writing, tight rewrites, and cutting fluff hard. Pick this if you want writing stripped to the minimum needed to land the point.

problem-first-marketer

Problem-first, design-aware. Leads with the reader's frustration before the product. Good for READMEs, landing pages, product docs, and any writing that needs to earn attention before asking for action. Treats visual hierarchy and whitespace as part of the message — a soulless layout kills interest before a word is read. Pick this if you want writing that makes the reader feel understood, then gives them a reason to care.

quiet-witness

Close-third, present-tense scene voice. Dramatizes technical friction through ordinary domestic or work action instead of exposition. Good for narrative-nonfiction cold openers and story beats, not explainer prose. Pick this if you want a scene the reader watches rather than a point the reader is told.

Guidance

If the user seems unsure, help them choose by asking what they want the writing to feel like:

  • more technical
  • more practical
  • more explanatory
  • more critical
  • more direct
  • more persuasive or reader-first

Do not overwhelm the user with theory. Help them choose.

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.