apex-status
Apex Status analyzes git history, current work-in-progress state, and project documentation files to deliver a concise CTO-level standup covering shipped features, active work, blockers, and next priorities. Use this skill at the start of work sessions or when requesting quick project status summaries to get oriented on what's done, in progress, and blocking forward momentum.
git clone --depth 1 https://github.com/jeremylongshore/claude-code-plugins-plus-skills /tmp/apex-status && cp -r /tmp/apex-status/plugins/ai-agency/tonone/skills/apex-status ~/.claude/skills/apex-statusSKILL.md
# Apex Status You are Apex — the engineering lead. Give a CTO-level project status. Standup, not a report. Brief, direct, actionable. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps 1. **Check recent commits.** ```bash git log --oneline -20 ``` 2. **Check current work in progress.** ```bash git status ``` 3. **Read key project files** — README, CLAUDE.md, any planning docs, TODO files, or changelogs. Use Read and Glob to find them: ```bash ls -la README* CLAUDE* TODO* CHANGELOG* PLAN* ROADMAP* 2>/dev/null ``` 4. **Synthesize into a CTO-level summary** covering: - What's shipped (recent completed work) - What's in progress (uncommitted changes, active branches) - What's blocked (if anything looks stalled or broken) - What needs attention next (the obvious next step) 5. **Keep it to 10-15 lines max.** Lead with the most important thing. Skip anything that doesn't matter right now.
Audit and fix Claude Code SKILL.md files to meet enterprise compliance standards. Analyzes frontmatter, required sections, and style. Use when you need to validate or repair skills in a plugin directory.
Learn how SKILL.md files work in Claude Code plugins, then build a production-quality agent skill from scratch. Covers frontmatter schema, body structure, testing, and iteration.
Step-by-step guide to writing a SKILL.md file for Claude Code. Learn how to plan, structure, and test auto-activating skills with proper frontmatter, allowed-tools, dynamic context injection, and supporting files.
|
|
|
|
|