agentleFS
9heaven9heaven/linkedin-growth-skills/skills/linkedin-authority-growth/SKILL.md

linkedin-authority-growth

Skill1 starsChanged 11 days agoMITView on GitHub

Builds credibility and the right audience on LinkedIn for founders, consultants, creators, and experts: narrows the position, audits the proof stack, plans comment and collaboration routines, picks a signature format, and sets a dated 90-day arc. Use when someone asks how to become known for something on LinkedIn, build authority or thought leadership, grow a niche audience, or get referrals from LinkedIn. Not for job seeking, follower buying, or engagement pods.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 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.

  • 2

    Very specific

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

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

    Use this after linkedin-profile-audit (the asset) and alongside linkedin-content-strategy (the output engine).

    line 18
  2. Distinctive:

    Ask: if someone in the audience had this problem at 11pm, would the user's name come to mind?

    line 38
  3. Distinctive:

    Test the position against three checks:

    line 41
  4. Distinctive:

    Do you have proof in it, or can you build some within 90 days?

    line 45
  5. Very specific:

    Never invent or inflate any of it (references/voice-rules.md).

    line 63
  6. Distinctive:

    Treat a comment as content, not a courtesy.

    line 84

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

LinkedIn Authority Growth

Build the kind of credibility that makes people pre-sold before the first call. Authority is a byproduct of visible, specific competence repeated in public. It is not a personal-brand aesthetic.

Use this after linkedin-profile-audit (the asset) and alongside linkedin-content-strategy (the output engine). This skill covers position, proof, and network: the parts that make the same content land harder.

Pick the depth

  • Quick: the user asks one thing ("help me narrow my niche", "what should my signature series be"). Run that step only and deliver its output.
  • Full (default): Steps 1 to 6.

Step 1: Claim a specific position

Broad expertise is invisible. Narrow expertise travels. Run the narrowing test with the user, for example:

Too broadBetterOwnable
Digital marketingEcommerce growthStore speed and checkout conversion for D2C brands on WooCommerce
CoachingLeadership coachingFirst-time engineering managers at Series A startups

Ask: if someone in the audience had this problem at 11pm, would the user's name come to mind? If not, the position is still too broad.

Test the position against three checks:

  1. Can you say it in 8 words?
  2. Does it exclude most people? (It must.)
  3. Do you have proof in it, or can you build some within 90 days?

Narrowing does not shrink the business. It makes referrals possible, because people can only refer what they can describe.

Step 2: Build the proof stack

Credibility ranks in a strict order. Move the user up it deliberately.

TierProofHow to get it in 90 days
1Your own results, documentedPublish build logs, numbers, and screenshots as you work
2Client results, namedAsk 3 past clients for a result you may post; offer to draft it, and they approve the wording
3Volume claims"47 stores audited": count what you have already done
4Third-party validationPodcast guest spot, article, community talk, tool-partner listing
5Original research or a free toolA survey of 100 people in the niche, or a small calculator
6Recommendations on the profileAsk 5 people directly, give one first, suggest what to mention

Never invent or inflate any of it (references/voice-rules.md). One checkable claim outperforms five vague superlatives, and a caught exaggeration ends the exercise.

Step 3: Grow the right network

Followers are only useful if they are the audience. Deliberate network building beats hoping for reach.

Comment strategy, the highest-leverage growth activity that is not posting:

  • Build a list of 15–25 accounts the buyers already read: peers, adjacent experts, and a few large accounts in the niche. The user names them. You may suggest categories and ways to find them (who comments on the user's own posts, who the buyers follow, LinkedIn search for the niche sorted by recent posts). Never invent names, handles, or follower counts. If a browsing tool lets you confirm a public profile exists, link it; otherwise write "verify before engaging".
  • Comment within the first 30 minutes of their post, 2–4 sentences, adding a distinct point or an example. Never "Great post!".
  • 10 a day. Expect profile visits and follows within a few weeks. Comments count toward the daily action ceiling (references/platform-reality.md), so they replace other activity, not add to it.
  • Treat a comment as content, not a courtesy. It is the cheapest reach on the platform: it puts the user's name in front of an audience they did not have to build.

Collaborations that compound:

  • Guest on niche podcasts and community AMAs. Small and specific beats large and general.
  • Co-write a teardown with a peer who serves the same audience from a different angle.
  • Newsletter or community swaps.
  • Publicly credit other people's work. Reciprocity is the whole mechanism.

Connections vs followers: make Follow the primary profile button once the audience outgrows the network, but keep accepting connection requests from the target audience: a connection can message the user directly and sits in their first-degree network, which a follower does not.

Step 4: Own a repeatable format

Authority accelerates when people recognize the work on sight. Pick one signature format and run it weekly for 12 weeks:

  • A numbered teardown series ("Teardown #14")
  • A weekly numbers post from real work
  • A "what I changed this week" build log
  • A recurring myth-bust for the niche

Consistency of format is what makes a stranger's third exposure feel like familiarity.

Step 5: Set a 90-day arc

Give dated phases, not a vague ambition.

  • Days 1–30, credibility base: profile fixed, 5 proof posts published, 3 recommendations requested, comment routine started.
  • Days 31–60, visibility: signature format running weekly, 2 collaborations booked, one lead magnet live.
  • Days 61–90, compounding: one piece of original research or a free tool, a first podcast or guest appearance, inbound DMs tracked weekly.

Set one honest expectation up front: meaningful authority takes 6–12 months of consistent output. Anyone promising 30 days is selling engagement pods.

Step 6: Deliver

  1. The narrowed position in 8 words or fewer, plus what it deliberately excludes
  2. Proof stack audit: the tier they are on, and the next three proof assets
  3. Target account list: the names the user supplied, organized by category, plus search methods to fill any gaps (no invented names)
  4. The signature format, with the first 4 installments outlined
  5. The 90-day arc with dated milestones
  6. Metrics: followers from the target audience, profile views, inbound DMs, and unsolicited referrals, with today's baseline (or "not provided")

Anti-patterns

  • Engagement pods and comment automation. LinkedIn treats coordinated and automated engagement as low quality, and the engagement is worthless anyway.
  • Buying followers or connections.
  • Broad motivational content to farm reach. It builds an audience of nobody.
  • "Personal branding" as aesthetics: logos, brand colors, a tagline, no proof.
  • Fake scarcity, fake client counts, invented case studies, invented target accounts.
  • Claiming thought leadership. Demonstrate the thinking and let others say it.

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.