القائمة
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/TuYv/ccpm --skill agenttrace-session-auditيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
Use when auditing a paid ad account for incremental contribution, wasted spend, or measurement integrity before scaling; runs a typed 20-item ROAS profile with verified vetoes and a SHIP/FIX/BLOCK/UNDECIDED gate on own exported data. Not for campaign structure design — use campaign-architect; not for creative production — use ad-creative-builder. 付费广告账户审计/ROAS评分
Use when the user asks to "write ad copy", "generate RSA headlines", or "build ad creative at volume"; produces ad units — RSA headlines/descriptions, hooks, and an angle matrix — message-matched to the destination landing page. Not for scoring an ad account — use ad-account-auditor; not for the post-click page — use landing-optimizer; not for organic articles — use content-writer. 广告创意/广告文案/RSA标题
Use when the user asks to "design an A/B test", "set up a creative/landing test", "run an incrementality test", or "is this result statistically and practically material?"; produces a hypothesis, variant matrix, sample-size/duration/power plan, and a documented effect/uncertainty read from own exported results. It applies only a precommitted owner-approved action rule; the statistical helper never chooses a business action. Not for producing variants — use ad-creative-builder; not for reading back one shipped change — use paid-measurement-loop. 广告AB测试设计/实验设计/显著性判定/增效测试
| name | agenttrace-session-audit |
| description | Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates. |
| category | development |
| risk | safe |
| source | community |
| source_repo | luoyuctl/agenttrace |
| source_type | community |
| date_added | 2026-05-10 |
| author | luoyuctl |
| tags | ["ai-coding","observability","cost-tracking","session-analysis"] |
| tools | ["claude","cursor","gemini","codex-cli"] |
| license | MIT |
| license_source | https://github.com/luoyuctl/agenttrace/blob/master/LICENSE |
Use this skill to inspect local AI coding-agent sessions with agenttrace. It focuses on the process behind a run: token and cost spikes, tool failures, retry loops, latency gaps, anomalies, health scores, and session-to-session diffs.
agenttrace is local-first and reads session logs from tools such as Claude Code, Codex CLI, Gemini CLI, Aider, Cursor exports, OpenCode, Qwen Code, Kimi, and generic JSON or JSONL traces.
Prefer an installed agenttrace binary when it is available on PATH. If the
current repository is luoyuctl/agenttrace, use go run ./cmd/agenttrace
instead.
agenttrace --doctor
agenttrace --overview
If no sessions are detected, report the directories checked by --doctor and
ask for the exported session file or log directory.
Use Markdown when the user wants a concise report they can inspect or share.
agenttrace --overview -f markdown -o agenttrace-overview.md
In the report, lead with the highest-risk sessions and explain why they matter: critical anomalies, repeated tool failures, token or cost waste, long latency gaps, low health scores, and suspiciously shallow sessions.
Use the latest session for a quick check, or pass an explicit export path when the user provides one.
agenttrace --latest
agenttrace --latest -f json
agenttrace path/to/session-or-export.json
agenttrace --overview -d path/to/session-dir
Token and latency metrics can look healthy even when an agent confidently takes the wrong implementation path. When the risk is semantic drift, pair the trace audit with a diff against a previous or known-good attempt.
Look for:
For CI or repeatable team workflows, use JSON output or health thresholds.
agenttrace --overview -f json -o agenttrace-overview.json
agenttrace --overview --fail-under-health 80 --fail-on-critical --max-tool-fail-rate 15
Tune thresholds to the project. A strict gate is useful for critical workflows; a reporting-only command is better while the team is learning its baseline.
agenttrace --overview
agenttrace --latest
Use this after a long coding-agent run to decide whether the next prompt should split the task, avoid a failing tool path, add missing tests, or reset context.
agenttrace --overview --fail-under-health 80 --fail-on-critical
Use this when agent session logs are available in CI and the team wants a simple guard against critical anomalies or unhealthy runs.
--doctor when session discovery is uncertain.Problem: No sessions are found.
Solution: Run agenttrace --doctor, then point agenttrace at the exported file or log directory.
Problem: A run looks cheap and fast but produced the wrong refactor. Solution: Compare the session against a prior attempt or known-good diff; cost metrics alone will miss semantic drift.
Problem: CI fails too often after adding a health gate. Solution: Start with JSON or Markdown reporting, inspect normal baselines, then tighten thresholds gradually.
@langfuse - Use for production LLM application tracing and evaluation.@observability-engineer - Use for broader service monitoring, SLOs, and incident workflows.