Tech Status Brief
Turn technical facts into a brief a non-technical reader can decide from, with the consequence first, hypotheses separated from what is known. Use for exec updates or escalations.
Install
npx skills add eshmith7/claude-skills-library --skill tech-status-briefgit clone --depth 1 https://github.com/eshmith7/claude-skills-library.git /tmp/claude-skills-library
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills-library/tech-skills/tech-status-brief ~/.claude/skills/tech-status-briefPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Engineering Brief for Non-Technical Readers Engineers explaining engineering to leadership have two failure modes and use both. Either the explanation carries every detail, so the reader stops at paragraph two and decides from the last thing they understood. Or it is simplified until it is no longer true, and the decision made from it is wrong in a way nobody catches for a month. ## When to use this Trigger on: status update, exec summary, escalation, outage update, customer update, steering committee, client update, "explain this to leadership", "why is it late", "justify the tech debt work", "how do I present this decision". ## Before you start Required: what you want to communicate, and the technical detail behind it. Ask, briefly: 1. **Who reads it, and what they can do about it.** A CEO, a client, a product manager and a steering committee need different documents, and the second half matters more: a reader who cannot act on something does not need it explained. 2. **What decision is being asked for, if any.** A brief for a decision is a different document from one for information, and most are written as the second when they should be the first. 3. What they already believe, including anything wrong. Correcting a wrong belief is a different job from filling a gap. 4. **For a live incident, what is confirmed against what is suspected.** These must not be mixed, and nothing suspected goes in.
Details
- Skill name
tech-status-brief- Repository
- eshmith7/claude-skills-library
- Path
tech-skills/tech-status-brief/SKILL.md- Repo updated
- 9 September 2026
FAQ
What does the Tech Status Brief skill do?
Turn technical facts into a brief a non-technical reader can decide from, with the consequence first, hypotheses separated from what is known. Use for exec updates or escalations.
How do I install the Tech Status Brief skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add eshmith7/claude-skills-library --skill tech-status-brief. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Tech Status Brief popular?
It lives in eshmith7/claude-skills-library, which has 5 GitHub stars and 1 forks.
Related skills
Content Brief
5eshmith7/claude-skills-library
Turn a vague content request into a brief a writer can execute without a second conversation: one question, reader, intent, angle, structure, evidence required. Use for content briefs.
Content Performance Audit
5eshmith7/claude-skills-library
Turn a performance export into one decision per asset: keep, refresh, rewrite, consolidate or delete, with cannibalisation groups found first. Use for content audits or pruning.
Content Prepublication Check
5eshmith7/claude-skills-library
Check a draft before publishing: every claim registered with its source, numbers verified, headline against body, originality and compliance flags. Use before anything goes out.
Batch Grill Me
5GAGAA-HUE/ASHUO-claude-skills
A relentless interview that asks every frontier question at once, round by round.
Tech Rollout Plan
5eshmith7/claude-skills-library
Classify a change by reversibility, phase it by blast radius, and set abort criteria and a tested rollback before it starts. Use for rollouts, migrations or cutovers.
Council
5npow/claude-skills
Convene the 18-member Council of High Intelligence — simulate multi-persona deliberation from Aristotle, Feynman, Torvalds, Taleb, Kahneman, and 13 others, then synthesize into ONE verdict. Use when facing hard decisions, design tradeoffs, strategy questions, or when you want diverse adversarial perspectives on a problem. Trigger on "/council", "ask the council", "what would the council say", "multi-perspective analysis". Supports --quick (fast), --duo (dialectic pair), --triad <domain>, --full (all 18), --members a,b,c.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.