Menu
Generate a recent Agentic OS status report from Claude/Codex logs, OS state, source status, and Notion projection state.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | status-report |
| description | Generate a recent Agentic OS status report from Claude/Codex logs, OS state, source status, and Notion projection state. |
Use when the user asks /status-report, asks what has been worked on in the
last N hours or days, asks for a recent Agentic OS work report, or asks for gap
analysis across recent agent work.
/Users/genome/agentic_os/harness/shared_factory/03-workflows/operations/status_report.quick-reference.md, workflow.md, approval-rules.md,
output-contract.md, runbook.md, and progress.md./Users/genome/agentic_os/clarks_consulting/02-projects/genomes_agentic_os/work-items/02-active/011_status_report_workflow.--hours N, --days N, or --since <ISO timestamp>.local, genomesbox, or all.Call memory_read first with a focused recent-work query.
Use Context Mode timeline search for recent prompts, decisions, blockers, errors, and compaction summaries.
Summarize Codex evidence from local and remote ~/.codex sessions and
rollout summaries. Reuse the existing Codex collector when available:
python3 /Users/genome/.codex/skills/agentic-status-report/scripts/agentic_status.py --hours <N> --format json
Summarize Claude evidence from ~/.claude/projects, ~/.claude/tasks,
~/.claude/sessions, ~/.claude/context-mode/sessions, and installed OS
conversation logs.
Inspect Agentic OS active work, work items, workflows, automations, commands,
skills, registries, .agents/skills, and routed TOOLS.md files.
Inspect registered source roots and active worktrees with read-only Git status.
Write the full markdown report to the filesystem source-of-truth path.
Verify Genome's Notion before writing any Notion projection. If verification
fails, record warning or blocked and do not write elsewhere.
Return the report path, Notion projection status or URL, top next actions, and validation receipt.
Check for:
/command, $skill, harness skill, Codex adapter,
registry, or TOOLS.md visibility;NEXT.md, or
no recent worklog;Default full report:
/Users/genome/agentic_os/clarks_consulting/02-projects/genomes_agentic_os/worklogs/status-reports/<YYYY-MM-DD-HHMM>-status-report.md
Default artifacts:
/Users/genome/agentic_os/clarks_consulting/02-projects/genomes_agentic_os/work-items/02-active/011_status_report_workflow/artifacts/status-reports/<run-id>/
Groom rough software ideas into source-backed implementation specs with original intent, capability discovery, tracker hierarchy, QA, Gherkin, and Notion documentation projection.
Append environment variables to ~/.zshenv on bigmac, genomesbox, and the Mac laptop in one step. Use when the user pastes `KEY=value` pairs and asks to add them to zshenv, or when setting secrets that need to be available on all three hosts. ssh aliases `bigmac`, `genomesbox`, and `mac` are already configured where needed.
Commit all local changes in logical groups until the repository is clean. Use when the user asks to commit everything, make all needed commits, or cleanly commit the full worktree without pushing.
Help users operate the published Composio CLI to find the right tool, connect accounts, inspect schemas, execute tools, subscribe to trigger events with `composio listen`, script workflows with `composio run`, and call authenticated app APIs with `composio proxy`. Use when the user asks how to do something with `composio`, wants to run a known tool slug, needs to discover a slug with `composio search`, fix a missing connection with `composio link`, inspect tool inputs with `--get-schema` or `--dry-run`, troubleshoot top-level CLI flows, or explicitly needs `composio dev` guidance.
Use when the user wants to work a LOS Jira ticket or non-trivial LOS task in a dedicated fast worktree, especially when they mention /workon, /orchestrate, fast worktree, use a worktree, or parallel agents.
Use when working or resuming LOS Jira implementation in a fast worktree with minimal chat output, especially after noisy /workon loops, repeated stack setup, test polling, or context/token burn.