agentleFS
Sign inStart free
Starlight-IntelligenceStarlight-Intelligence/starlight-agent-skills/skills/brand/frankx-authority-post/SKILL.md

frankx-authority-post

Skill1 starsChanged 4 months agoMITView on GitHub

Write a FrankX authority post — an AI-Architect-voiced LinkedIn/X post that leads with a result, teaches one concrete lesson, and stays humble. Use when drafting a thought-leadership post as FrankX, sharing a build/insight, or asked for an 'authority post'.

1 other project uses a version of this.

Adopted by

Most recently taken up by

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:

    Every claim must be earned and specific.

    line 38

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

FrankX Authority Post

An insight or shipped result → a FrankX-voiced authority post.

Purpose

FrankX's positioning is elite creator, AI architect, humble. This skill drafts authority content in that voice: lead with a demonstrated result, extract one concrete, teachable lesson, and let the work speak — no guru cadence, no grandiose claims. Output is ready to post on LinkedIn or X.

When it fires

  • Keyword triggers: authority post, frankx post, thought leadership, linkedin post, share this insight
  • File triggers: posts/**
  • Command triggers: /frankx-authority-post

Inputs

InputRequiredNotes
seedyesThe result/insight/build to post about.
platformnolinkedin (default) or x.
ctanoOptional soft call-to-action.

Voice rules

Lead with results and demonstrated expertise; precise/technical where useful; show don't tell; confident but understated. Avoid: spiritual/consciousness language, grandiose impact claims, over-explaining motivation, self-help cadence. Every claim must be earned and specific.

Workflow

  1. Find the result — the concrete, true thing that earns attention. ✅ Check: it's demonstrated, not asserted.
  2. Hook — first line states the result or the surprising lesson.
  3. Body — the one lesson, with enough specifics to be useful; humble about scope.
  4. Close — optional soft CTA or open question.
  5. Voice pass — strip guru/grandiose phrasing; verify every claim is earned.

Output contract

{
  "platform": "linkedin | x",
  "post": "string",
  "hook": "string — first line",
  "lesson": "string — the one teachable point",
  "claims_checked": ["string — each claim + why it's earned"]
}

Tools & MCP

  • Tools: Read. MCP: none required.

Quality bar

  • Leads with a demonstrated result, not a claim.
  • Exactly one clear, concrete lesson.
  • No spiritual/guru/grandiose language.
  • Humble in tone; specifics over superlatives.

Example

Input: "Shipped a 6-skill portable library that runs across 5 runtimes" → a LinkedIn post leading with that result, teaching one lesson about portable skill design, with a soft question close.

Built on SIP — Starlight Intelligence Protocol Substrate: starlightintelligence.org/protocol v1.1.0 Layers used: [file-contract, attestation, sovereignty] Vertical: starlight-agent-skills · portable capability layer

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.

Check your setup, free