CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

apex-status

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.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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.
git log --oneline -20
  1. Check current work in progress.
git status
  1. 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
  1. 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)
  2. Keep it to 10-15 lines max. Lead with the most important thing. Skip anything that doesn't matter right now.

Repository

jeremylongshore/tons-of-skills-marketplace

Path

plugins/ai-agency/tonone/skills/apex-status/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.