reporting

Aggregate Geas mission state files into health-check JSON and markdown summaries.

15|4|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/choam2426/geas --skill reporting-choam2426
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reporting
Source: https://github.com/choam2426/geas/tree/main/plugin/skills/reporting
Command: npx skills add https://github.com/choam2426/geas --skill reporting-choam2426

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The reporting skill automates mission health assessment by aggregating debt registers, gap assessments, event logs, and agent memory to produce objective health signals and human-readable summaries, removing manual auditing and ad-hoc status checks.

Core Features & Use Cases

  • Automated Health-Check Generation: Computes eight protocol health signals and writes a validated .geas/state/health-check.json.
  • Debt and Gap Rollups: Summarizes debt by severity, kind, and status and computes gap closure ratios from latest assessments.
  • Product Authority Briefings and Session Summaries: Emits phase-briefing and session end markdown artifacts for decision-making and audits.
  • Use Case: At phase transitions or session close, run reporting to surface triggered signals (e.g., debt_stagnation, worker_low_confidence), required authority actions, and an actionable markdown briefing for stakeholders.

Quick Start

Invoke the reporting skill with the mission ID to generate the health-check.json and a markdown briefing for the mission.

Frequently Asked Questions about reporting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate mission health-checks and generate reporting summaries?

Automate mission health-checks by running the reporting skill to aggregate debt registers, gap assessments, and event logs into structured markdown summaries. It computes debt rollups, gap closure ratios, and eight protocol health signals without manual auditing.

What protocols or file formats are required for generating Geas mission health-checks?

Generating Geas mission health-checks requires read access to .geas state files like debt-register.json, gap-assessment JSONs, events.jsonl, rules.md, agent memory, and task record.json, plus write access to .geas/state/health-check.json.

When should I run a gap assessment and debt rollup for a project mission?

Run gap assessments and debt rollups during phase transitions, at session ends, or for ad-hoc reporting. This computes objective health signals, surfaces triggered alerts like debt stagnation, and produces actionable markdown briefings for stakeholders.

Does this reporting approach work with existing agent memory and event logs?

Yes, the reporting approach works directly with existing agent memory and events.jsonl logs. It aggregates these state files alongside debt registers and gap assessments to compute objective health signals and generate phase-briefing markdown artifacts.

What is the best way to surface triggered protocol health signals for authority briefings?

The best way to surface triggered protocol health signals is to apply the reporting skill to mission folders. It identifies signals like worker low confidence, highlights required authority actions, and emits session end markdown artifacts for decision-making.