agentleFS
postoncehqpostoncehq/x-mcp/skills/x-bio-generator/SKILL.md

x-bio-generator

Skill1 starsChanged 46 days agoMITView on GitHub

Write an X (Twitter) bio of up to 160 characters, plus a display name and a pinned tweet idea, for the user to paste into their profile. Use when the user asks for a Twitter bio, an X bio, a bio generator, or help with their X profile.

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. liftli-ai/x-agent-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 repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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 a bio that tells a visitor in one read who this is and why to follow.

    line 11

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

X (Twitter) bio generator

Write a bio that tells a visitor in one read who this is and why to follow. The PostOnce MCP can't edit profiles; the user pastes the result into X under Edit profile.

Before writing

Get: who the account is (person, founder, brand), what they post about, who they want to follow them, one proof point (role, company, result, audience), and the link they want in the profile. Paste the current bio if there is one. Never invent credentials, employers, numbers or awards.

Limits

FieldLimit
Bio160 characters
Display name50 characters
Location30 characters
WebsiteOne link, in its own field, so it doesn't need to go in the bio

Count emoji as 2 characters to be safe.

What makes a bio work

  • Answer "what will I get if I follow?" Topics and angle beat job titles alone.
  • One proof point: "Built [X] to [result]", "[Role] at [company]", "Writing about [topic] since [year]".
  • Specific nouns over adjectives. "Posts about pricing for SaaS founders" beats "Passionate entrepreneur".
  • Separators (·, |, line breaks) are fine; keep it to 2–3 short parts.
  • Mentions of a company handle (@acme) link to it; use one if it helps.
  • Hashtags and emoji: 0–1 each. They rarely help.

Patterns:

  • "[What I do] for [who]. [Proof point]. [What I post about]."
  • "[Role] at @[company]. Posting about [topic 1], [topic 2] and [topic 3]."
  • "[Result]. Now sharing how I [did it]."

Display name and pinned tweet

  • Display name: the real name, optionally plus a short topic ("Sam Lee | SaaS pricing"). Don't keyword-stuff.
  • Pinned tweet: suggest one post that shows the account at its best (a strong thread lead, an intro post or a proof post). If the user wants to publish it, draft it with x-tweet-generator. Pinning happens in the X app; the MCP can't pin.

Output

Give 3 bio options with character counts, one display name suggestion and one pinned tweet idea. Remind the user to paste the bio into X themselves. Offer to publish the pinned tweet through the postonce skill (confirm account and time before create_post).

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.