Install
$ agentstack add skill-d-oit-rust-2026-template-metrics-reporter ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
- Prepare Directory: Ensure the daily directory exists.
``bash EVENT_DIR=".agents/events/$(date -u +%Y/%m/%d)" mkdir -p "${EVENT_DIR}" ``
- Generate Filename: Create a unique filename for the event.
``bash 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.
``json { "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.
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.
Rationalizations
| 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. |
Red Flags
- [ ] Not calling metrics-reporter as the last step of a task
- [ ] Setting human_interventions to 0 when a human fixed your code
- [ ] Using the old append-to-metrics.jsonl pattern instead of event files
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: d-oit
- Source: d-oit/rust-2026-template
- License: MIT
- Homepage: https://d-oit.github.io/rust-2026-template/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.