mcpbeat Sign in

Apex Status Skill for Claude

by jeremylongshore

CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.

347 tokens
context cost
SKILL.md, read when the skill is used
2
files
plus reference files
0
copies elsewhere
how many repositories repackaged it
2 679
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill apex-status

What comes with it

431 bytes besides the instruction
.claude-plugin/plugin.json

What it tells the agent to use

found in the instruction text
Read reads your files
WebFetch fetches pages from the network
WebSearch reads your files

The instruction itself

2 sections, as written by the author

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

  • Check recent commits.
git log --oneline -20
  • Check current work in progress.
git status
  • Read key project files — README, CLAUDE.md, any planning docs, TODO files, or changelogs. Use Read and Glob to find them:
ls -la README* CLAUDE* TODO* CHANGELOG* PLAN* ROADMAP* 2>/dev/null
  • 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)
  • Keep it to 10-15 lines max. Lead with the most important thing. Skip anything that doesn't matter right now.

How to use it

Copy the folder

Take jeremylongshore/apex-status from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.