agentleFS
lxyang20131208-starlxyang20131208-star/x-algorithm-skills/skills/x-profile/SKILL.md

x-profile

Skill1 starsChanged 6 months agoMITView on GitHub

Audit an X (Twitter) profile — handle, display name, bio, header, pinned post — for follow conversion. Use when the user asks "review my X profile", "improve my bio", "why don't visitors follow me", "audit my Twitter profile", or shares their profile details. Returns a per-element audit and rewritten copy.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. Jakeschincariol/x-agent-skill★ 4same name
    2. belzoralolbtw/x-agent-skill★ 0same name
    3. lloyd3126/chenchungnien-skills★ 0same name
    4. swayamdhawan/x-agent★ 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

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read reference/ALGORITHM.md if available.

    line 8
  2. Distinctive:

    Never invent credentials, numbers, or achievements.

    line 78
  3. Distinctive:

    Keep the user's voice and personality — a profile should sound like a person.

    line 83

“Common” is measured: kept by at least 6 in 10 of the 4 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

x-profile — Profile Audit for Follow Conversion

Read reference/ALGORITHM.md if available. Why the profile matters to the algorithm, not just to humans:

follow_author and profile_click are two of the 19 actions Phoenix predicts. A post drives a viewer to your profile; the profile converts that visit into a follow. Every follow improves your in-network base — and in-network is structurally favored in ranking. The profile is the conversion step in the whole growth loop.

A great post with a weak profile leaks reach: you get the impressions and the profile clicks, then lose the follow.

What you need from the user

Their current handle, display name, bio, header image description, and pinned post (or a screenshot of the profile). Also their niche and what they want to be known for.

The audit — 6 elements

  1. Handle (@) — Ideally readable and stable. Numbers/underscores from auto-generated handles read as low-trust. A handle change is high-cost; only recommend it if the current one is actively hurting (e.g. @user82910473).
  2. Display name — Best practice in 2026: Name · what you do or Name | building X. The "what you do" half is what makes you legible in reply threads and notifications, where only the display name shows.
  3. Bio — The highest-leverage element. It must answer, in the first line, three questions a stranger has after reading one good post: who are you, what do you do, why should I care. Structure that works:
    • Line 1: the specific thing you do + proof (a number, a product, a credential).
    • Line 2: who it's for / what you post about (sets topic expectation).
    • Optional line 3: a current focus or a soft link cue. Kill: vague identity words ("entrepreneur", "thought leader", "passionate about"), emoji soup, and joke bios that don't tell a visitor what they'll get by following.
  4. Header image — Should reinforce the one thing you do (product screenshot, a metric, a clear tagline). A generic stock image wastes the largest pixels on the page.
  5. Pinned post — Your single best proof, permanently. It should be your strongest "who I am + what I deliver" post: a real result, a flagship thread, or a build-in- public milestone. If the pinned post is months old or off-niche, flag it.
  6. Coherence — Handle, name, bio, header, and pinned post should all point at the SAME one thing. A visitor should be able to state your niche in five words after three seconds. Mixed signals kill the follow decision.

Output format

Profile read: <what a stranger currently thinks you do, in one line>
Follow-conversion verdict: <strong / leaky / broken> — <why>

Element audit:
  Handle ......... PASS/FLAG — <note>
  Display name ... PASS/FLAG — <note>
  Bio ............ PASS/FLAG — <note>
  Header ......... PASS/FLAG — <note>
  Pinned post .... PASS/FLAG — <note>
  Coherence ...... PASS/FLAG — <note>

Rewrites:
  Display name: "<new>"
  Bio:
  "<new bio, ready to paste>"
  Header: <what it should show>
  Pinned: <which post to pin, or what to create>

Rules

  • Never invent credentials, numbers, or achievements. Write the bio from what the user actually told you; if a proof point would strengthen it, ask for one.
  • Give paste-ready copy, not just advice.
  • Respect character limits: bio is 160 characters. If your rewrite is over, trim it and say so.
  • Keep the user's voice and personality — a profile should sound like a person.

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.