Menu
Record agentic task completion via event files for DORA observability.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Generate a DORA-REPORT.md for this repository by computing the five core DORA software delivery performance metrics and three DORA agentic metrics from available data sources. Use this when asked to generate a DORA report or assess delivery performance.
Generate a human-friendly overview infographic by scanning the live project structure, including workspace crates, skills, and scripts. Use this skill whenever the user asks to regenerate, refresh, or update the overview diagram. Triggers on phrases like "update the overview", "regenerate the overview SVG", or "sync the overview".
Run comprehensive linting and static analysis on Rust code including clippy, format check, security audit, supply chain, and unused dependencies. Use before committing, during CI, or when reviewing code quality. Triggers: "lint rust", "clippy", "static analysis", "code quality".
Read all open issues (GitHub/GitLab), categorize by type and effort, plan batch implementation order, and coordinate implementation across multiple issues in a single PR/MR. Auto-detects platform from git remote. Use when asked to "implement all issues", "fix all open issues", "batch implement", or "address all issues". Triggers: "all issues", "implement all", "batch issues", "open issues", "fix all", "address all issues".
Automated secret scanning using secretlint to prevent credential leaks.
Harness engineering guide — maps all sensors and feedforward guides, teaches self-correction protocol when a CI sensor fires. Use when a sensor fires, before making code changes, or when setting up agent context for a new task. Triggers: "harness", "sensor fire", "CI failure", "self-correction".
| name | metrics-reporter |
| description | Record agentic task completion via event files for DORA observability. |
| category | metrics |
| license | MIT |
| metadata | {"author":"jules","version":"2.0"} |
Record agentic task completion by writing a per-event JSON file to .agents/events/. This pattern avoids Git merge conflicts and supports multi-agent coordination.
Call this skill as the LAST step of any task or sub-task.
Prepare Directory: Ensure the daily directory exists.
EVENT_DIR=".agents/events/$(date -u +%Y/%m/%d)"
mkdir -p "${EVENT_DIR}"
Generate Filename: Create a unique filename for the event.
EVENT_FILE="${EVENT_DIR}/$(date -u +%Y-%m-%dT%H-%M-%SZ)-${AGENT_NAME:-unknown}-${TASK_ID:-$(date -u +%s)}.json"
Write Event Data: Populated with task metadata and success status.
{
"event_id": "$(date -u +%s)-${AGENT_NAME}",
"task_id": "${TASK_ID}",
"skill": "${SKILL_NAME}",
"status": "success",
"started_at": "${STARTED_AT}",
"finished_at": "$(date -u +%Y-%m-%dT%H:%M:%SZ)",
"success": true,
"human_interventions": 0,
"git_sha": "$(git rev-parse --short HEAD)"
}
Verify: Ensure the JSON is valid and written to the correct location.
Set human_interventions > 0 if:
Aggregated metrics are periodically generated by CI into .agents/aggregated/. The CI status files are in .agents/ci/. Do not hand-edit files in these directories.
| Rationalization | Reality |
|---|---|
| "I'll skip metrics — it's just paperwork." | Without metrics, you can't prove AI tooling ROI or identify bottlenecks. |
| "I'll log it later." | Later never happens. Log immediately after task completion. |
| "human_interventions doesn't matter." | It's the key metric for measuring true agent autonomy vs human effort. |