metrics-reporter

Skill: metrics-reporter

When to Use

• User asks for this skill's functionality

Purpose

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.

When to use

Call this skill as the LAST step of any task or sub-task.

Steps

1. Prepare Directory: Ensure the daily directory exists.

   EVENT_DIR=".agents/events/$(date -u +%Y/%m/%d)"
   mkdir -p "${EVENT_DIR}"
   

2. 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"
   

3. 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)"
   }
   

4. Verify: Ensure the JSON is valid and written to the correct location.

Stacked PR Metrics

When using the stacked-prs skill, add these optional fields to the event JSON:

{
  "stack_id": "billing-feature",
  "stack_position": 1,
  "stack_total": 3
}

• stack_id: Identifier for the stack (feature name)
• stack_position: This layer's position in the stack (1-indexed)
• stack_total: Total number of layers in the stack

Do NOT include these fields for non-stacked work.

Human Interventions

Set human_interventions > 0 if:

• A human corrected, rewrote, or reverted your code.
• A PR required a fixup commit after your submission.
• A review comment called out an error in your work.

Aggregation

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.