Render the ODD loop status from committed .odd/ reports and git metadata.
npx skills add https://github.com/using-system/oddyssey --skill get-status-using-system
Please help me install this Agent Skill. Skill: get-status Source: https://github.com/using-system/oddyssey/tree/main/.apm/skills/get-status Command: npx skills add https://github.com/using-system/oddyssey --skill get-status-using-system
High-intent search queries and answers about installing and using this skill.
Run the get-status skill, which executes scripts/odd_status.py --render against the repository's .odd/ directory. It prints a one-screen status by default, or the full tables with --full or when scoped to a service, stack, or environment.
No. The status is computed entirely from committed .odd/ reports, the decisions ledger, and git metadata. It never queries a backend, starts a stack, or writes any file.
The skill states exactly what was searched (each filter and value) and what exists instead: the distinct services, stacks, and environments present in stored frontmatters. It never renders an empty table silently or falls back to the unfiltered picture.
Rulings the rules cannot settle are deferred to a Judgment needed list. The caller rules on them via flags like --ruled REPORT/ID=STATE, then the script re-renders with those rulings applied before the burn-down is computed.
Reports naming an unreachable external repository have an unknown code boundary, and pre-convention reports without a verifies field leave the chain unknown. Unreadable reports are reported and skipped rather than failing the whole status.
grafanaInstruments LLM applications to send generations and OTel telemetry to Grafana Agent Observability.
V4-CompanyValidate logging, tracing, and telemetry against MarsAI standards for Gate 2.
marcmontecalvoAudit deferred-work ledger entries against codebase status and partition them.
vibercoder79Generate and update Grafana Cloud dashboards, panels, and PromQL alert rules.
