mcpField
A
authority-first-headlines

authority-first-headlines

github.com/arthurzakirovMarketing & growth0163 installsUpdated 4w ago
Repository

About authority-first-headlines

A writing skill for revising titles and headlines to establish credible authority before explaining the subject. It is intended for people editing content such as repository descriptions, homepages, and articles.

Key features

  1. 01Authority-first headline structure
  2. 02Specific, traceable proof points
  3. 03Guidance against implied endorsement
  4. 04Reusable headline templates
  5. 05Headline review checklist

Use cases

  1. 01Revising a generic repository description
  2. 02Writing a homepage hero line
  3. 03Retitling an article around a concrete result

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/arthurzakirov/proofstack --skill authority-first-headlines

After installing, type/authority-first-headlinesin Claude Code to confirm it loaded.

Details

From the project README

Authority-First Headlines Skill

Purpose

Rewrite titles, headlines, repository descriptions, homepage hero lines, LinkedIn headlines, article titles, and section openers so they lead with credible authority before explaining the content.

Use this when a title sounds like a generic description instead of a reason to care.

Core Pattern

Authority -> Outcome -> Mechanism -> Reader Promise

Examples of authority:

  • A measurable result
  • A recognized institution
  • A senior audience
  • A hard operating context
  • A respected company, university, publication, or framework
  • A concrete proof point such as "used by 20+ engineers"
  • A rare achievement, ranking, certification, or adoption signal

Rewrite Rules

  1. Lead with proof before explanation.
    • Weak: "A tool for setting up AI development environments."
    • Stronger: "The AI workstation setup method adapted from senior engineering workflows."
  2. Prefer specific authority over vague authority.
    • Weak: "Trusted by professionals."
    • Stronger: "Used by 20+ engineers and technical leaders."
  3. Borrowed authority must be truthful and traceable.
    • Acceptable: "Adapted from practices learned from a senior engineering lead, then customized for my own workflow."
    • Not acceptable: "Google's official workflow" unless it actually is official.
  4. Do not overclaim ownership of institutional authority.
    • Say "inspired by," "adapted from," "used in," "learned from," or "based on public guidance from" when appropriate.
    • Avoid implying endorsement.
  5. Add curiosity when possible.
    • Weak: "How to prioritize automation."
    • Stronger: "The 770-hour automation opportunity hidden behind a 41-hour roadmap."

Headline Templates

  • [Authority proof] + [result] + [reader promise]
  • [Recognized source/framework] + [practical application]
  • [Unexpected contrast] + [outcome] + [how-to promise]
  • [Senior audience adopted X] + Here's how it works
  • [Hard constraint] + [surprising result] + [repeatable method]

Checklist

  • Does the title answer "why should I trust this?"
  • Does it contain a concrete proof point if available?
  • Does it avoid false endorsement?
  • Does it make the reader curious?
  • Does it imply a useful method, not just a finished artifact?

Comments

Markdown supported