Credible claims and safe authority
Skill ArthurZakirov/ProofStack/skills/credible-claims-and-safe-authority
Use authority, numbers, and institutional credibility without exaggerating or creating legal, ethical, or reputational risk.From its SKILL.md
npx -y skills add ArthurZakirov/ProofStack --skill credible-claims-and-safe-authorityAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.0 KB, 431 tokens by cl100k_base, as published. Nobody here has run it
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:
- Direct factual claim
- "Built and deployed X."
- Quantified but bounded claim
- "Surfaced 770 addressable hours."
- Shared-outcome claim
- "Helped the team maintain velocity."
- Inference claim
- "This suggests a higher-leverage roadmap."
- Borrowed authority claim
- "Adapted from public guidance by X."
- 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?
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.