agentleFS
getedgehqgetedgehq/skills/fede-voice/SKILL.md

fede-voice

Skill5 starsChanged 11 days agoApache-2.0View on GitHub

Draft or rewrite DMs and public posts in Federico De Ponte's documented voice. Use for writing as Federico; this is a finished profile.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow the thread's language.

    line 12
  2. Very specific:

    Write lowercase fragments, usually two or three short lines with one thought per line.

    line 13
  3. Distinctive:

    Use normal sentence capitalization and short paragraphs separated by blank lines.

    line 19
  4. Distinctive:

    Put the payoff in the post.

    line 21
  5. Distinctive:

    Prefer everyday language to technical feature lists.

    line 22
  6. Very specific:

    No em dash (—) or en dash (–).

    line 26
  7. Distinctive:

    Avoid “game changer,” “excited to announce,” “unlock,” “revolutionary,” artificial urgency, generic praise, and a writerly closing line.

    line 27
  8. Distinctive:

    Keep sentences short and direct.

    line 28
  9. Distinctive:

    Check counts, names, dates, and claims against the actual source.

    line 29
  10. Distinctive:

    Stop there when that is the last supported fact.

    line 55

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

Fede Voice

Write in Federico's documented style. Use the supplied thread, notes, or verified source for substance. Never borrow a claim, relationship, metric, or opinion from a style example. If a needed fact is missing, ask or mark it for confirmation. To build a new person's profile, use clone-my-voice.

Private messages

  • Follow the thread's language. Use Federico's own prior messages as the closest style reference when available.
  • Write lowercase fragments, usually two or three short lines with one thought per line. A short question fragment, casual abbreviation, ..., or occasional :D can fit.
  • Skip greetings, signoffs, bullets, numbered prose, bold emphasis, and polished transitions.
  • Suggest rather than command. Keep the stakes at the level Federico stated.

Public posts

  • Use normal sentence capitalization and short paragraphs separated by blank lines. Keep each beat concrete and easy to scan.
  • Open with a real reader problem, event, constraint, or result from supplied material. If a hook borrows a proven shape, identify its source outside the post. Never manufacture a first-person event or measured result.
  • Put the payoff in the post. Show what happened, then stop after the last supported fact. No tidy summary or engagement question at the end.
  • Prefer everyday language to technical feature lists. Preserve Federico's phrasing when editing his notes.

Across formats

  • No em dash (—) or en dash (–). Use a period, comma, or colon.
  • Avoid “game changer,” “excited to announce,” “unlock,” “revolutionary,” artificial urgency, generic praise, and a writerly closing line.
  • Keep sentences short and direct. One idea per sentence is a useful default, not a fixed word count.
  • Check counts, names, dates, and claims against the actual source. Do not invent them for style.

Short pattern examples

These are synthetic style illustrations, not Federico's messages or product claims. Replace their facts with the user's real context.

DM, German

könnte gut passen sollen wir das morgen kurz testen?

DM, English

looks useful actually want me to try it first?

Post opening

We tested the draft with 12 people.

Each revision took 30 minutes less in this synthetic example.

Post ending

The team kept the shorter version.

Stop there when that is the last supported fact.

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.