Skip to content
Back to skills

Sitrep

ASecurity

Honest situation report for the current ASTROLABE session — raw assessment of git state, work in flight, green/red flags, and project health, recorded on the active GitHub issue (issues are the only durable state; no ./tmp SITREP files) and summarized inline. Use when asked for a sitrep/status/honest assessment, or before risky transitions. For a plain pause/stop record, astro-handoff alone suffices.

  • 4 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 22, 2026
ai-agentsgit

Security analysis

A100/100

Scanned September 22, 2026

npx -y skills add ChrisRoyse/Astrolabe --skill sitrep --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Sitrep?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Sitrep
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/chrisroyse-sitrep/badge)](https://www.skillsdirectory.com/skills/chrisroyse-sitrep)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: sitrep
description: Honest situation report for the current ASTROLABE session — raw assessment of git state, work in flight, green/red flags, and project health, recorded on the active GitHub issue (issues are the only durable state; no ./tmp SITREP files) and summarized inline. Use when asked for a sitrep/status/honest assessment, or before risky transitions. For a plain pause/stop record, astro-handoff alone suffices.
---

# SITREP

A sitrep is astro-handoff **plus** candid analysis. It is written for a zero-context successor and for the operator.

1. Execute the astro-handoff protocol in full (hygiene verification, done-verified vs not-done, next concrete step, uncommitted state, telemetry block kind `handoff` on the active issue).
2. In the same issue comment and inline to the operator, add the honest layer — raw, not diplomatic:
   - **Green flags** — what is genuinely solid, with the evidence that makes it solid.
   - **Red flags** — risks, smells, drift, unverified claims found in prior comments, hygiene debt (stray branches/worktrees/locks), anything that looks done but has no FSV evidence.
   - **Health call** — one paragraph: is this effort on track, stalled, or quietly broken? Say which and why.
   - **Recommended next steps** — ordered, concrete, each one command/edit deep.
3. Never write SITREP files to `./tmp` or anywhere on disk — the issue comment is the artifact. If no issue is active, file one first (astro-new-issue) or attach to EPIC #65 as a session report.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.