mcpField
C
credible-claims-and-safe-authority

credible-claims-and-safe-authority

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

About credible-claims-and-safe-authority

A skill for using factual, quantified, and authority-related claims without overstating evidence or implying unsupported endorsements. It is intended for people writing project, team, or institutional claims where accuracy and reputational risk matter.

Key features

  1. 01Rank claims by risk
  2. 02Distinguish opportunity from achieved savings
  3. 03Describe team contributions precisely
  4. 04Frame institutional authority accurately
  5. 05Use quotes with clear attribution
  6. 06Check claims for evidential support

Use cases

  1. 01Review quantified impact statements
  2. 02Describe shared team outcomes fairly
  3. 03Reference institutional recognition accurately
  4. 04Check quotes and borrowed authority before publication

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/arthurzakirov/proofstack --skill credible-claims-and-safe-authority

After installing, type/credible-claims-and-safe-authorityin Claude Code to confirm it loaded.

Details

From the project README

Credible Claims and Safe Authority Skill

Purpose

Use authority, numbers, and institutional credibility without exaggerating or creating legal, ethical, or reputational risk.

Claim Safety Ladder

From safest to riskiest:

  1. Direct factual claim
    • "Built and deployed X."
  2. Quantified but bounded claim
    • "Surfaced 770 addressable hours."
  3. Shared-outcome claim
    • "Helped the team maintain velocity."
  4. Inference claim
    • "This suggests a higher-leverage roadmap."
  5. Borrowed authority claim
    • "Adapted from public guidance by X."
  6. Endorsement-like claim
    • "X recommends this." Only use if explicitly true.

Use Careful Language For

Addressable Opportunity vs Guaranteed Savings

Say:

surfaced 770 addressable hours

Avoid:

saved 770 hours

unless the hours were actually saved.

Team Outcomes

Say:

helped maintain team velocity

Avoid:

single-handedly maintained team velocity

unless that is provably true.

Institutional Authority

Say:

at a World Economic Forum-recognized AI scale-up

Avoid:

World Economic Forum-backed

unless backed is accurate.

Inspired by Credible People

Say:

adapted from practices learned from a senior engineering lead

Avoid:

Google's official method

unless it is official.

Quote Usage

When using quotes:

  • Keep excerpts short.
  • Use brackets [...] to omit irrelevant parts.
  • Preserve meaning.
  • Attribute clearly.
  • Do not make a quote sound broader than it is.

Checklist

  • Is every number explainable?
  • Could a former colleague agree the claim is fair?
  • Is borrowed authority framed as origin/context, not endorsement?
  • Are "helped," "solo-built," and "led" used precisely?
  • Does the claim stay impressive without becoming misleading?

Comments

Markdown supported