[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EV5TR92AVNKBWWXH7PRJFM":3,"skill-same:01M7EV5TR92AVNKBWWXH7PRJFM":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":14,"repositoryHtmlUrl":44,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M7EV5TR92AVNKBWWXH7PRJFM","agenttrace-session-audit",null,"Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fdevelopment\u002Fagenttrace-session-audit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: agenttrace-session-audit\ndescription: \"Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.\"\ncategory: development\nrisk: safe\nsource: community\nsource_repo: luoyuctl\u002Fagenttrace\nsource_type: community\ndate_added: \"2026-05-10\"\nauthor: luoyuctl\ntags: [ai-coding, observability, cost-tracking, session-analysis]\ntools: [claude, cursor, gemini, codex-cli]\nlicense: \"MIT\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002Fluoyuctl\u002Fagenttrace\u002Fblob\u002Fmaster\u002FLICENSE\"\n---\n\n# agenttrace Session Audit\n\n## Overview\n\nUse this skill to inspect local AI coding-agent sessions with\n[agenttrace](https:\u002F\u002Fgithub.com\u002Fluoyuctl\u002Fagenttrace). It focuses on the process\nbehind a run: token and cost spikes, tool failures, retry loops, latency gaps,\nanomalies, health scores, and session-to-session diffs.\n\nagenttrace is local-first and reads session logs from tools such as Claude Code,\nCodex CLI, Gemini CLI, Aider, Cursor exports, OpenCode, Qwen Code, Kimi, and\ngeneric JSON or JSONL traces.\n\n## When to Use This Skill\n\n- Use when a user asks why an AI coding run was slow, expensive, shallow, or unreliable.\n- Use when reviewing local agent logs before retrying a failed or suspicious task.\n- Use when building a lightweight CI health gate for AI-assisted coding sessions.\n- Use when comparing two attempts and looking for changed tool paths, retries, or cost patterns.\n\n## How It Works\n\n### Step 1: Discover Available Sessions\n\nPrefer an installed `agenttrace` binary when it is available on `PATH`. If the\ncurrent repository is `luoyuctl\u002Fagenttrace`, use `go run .\u002Fcmd\u002Fagenttrace`\ninstead.\n\n```bash\nagenttrace --doctor\nagenttrace --overview\n```\n\nIf no sessions are detected, report the directories checked by `--doctor` and\nask for the exported session file or log directory.\n\n### Step 2: Produce a Human-Readable Audit\n\nUse Markdown when the user wants a concise report they can inspect or share.\n\n```bash\nagenttrace --overview -f markdown -o agenttrace-overview.md\n```\n\nIn the report, lead with the highest-risk sessions and explain why they matter:\ncritical anomalies, repeated tool failures, token or cost waste, long latency\ngaps, low health scores, and suspiciously shallow sessions.\n\n### Step 3: Inspect One Session or Directory\n\nUse the latest session for a quick check, or pass an explicit export path when\nthe user provides one.\n\n```bash\nagenttrace --latest\nagenttrace --latest -f json\nagenttrace path\u002Fto\u002Fsession-or-export.json\nagenttrace --overview -d path\u002Fto\u002Fsession-dir\n```\n\n### Step 4: Compare Attempts When Semantics Matter\n\nToken and latency metrics can look healthy even when an agent confidently takes\nthe wrong implementation path. When the risk is semantic drift, pair the trace\naudit with a diff against a previous or known-good attempt.\n\nLook for:\n\n- changed files or commands that diverge from the intended task\n- missing tests or verification steps compared with the reference attempt\n- repeated edits around the same files without a clear reason\n- lower cost that came from skipping necessary exploration\n\n### Step 5: Add Automation Gates\n\nFor CI or repeatable team workflows, use JSON output or health thresholds.\n\n```bash\nagenttrace --overview -f json -o agenttrace-overview.json\nagenttrace --overview --fail-under-health 80 --fail-on-critical --max-tool-fail-rate 15\n```\n\nTune thresholds to the project. A strict gate is useful for critical workflows;\na reporting-only command is better while the team is learning its baseline.\n\n## Examples\n\n### Quick Local Review\n\n```bash\nagenttrace --overview\nagenttrace --latest\n```\n\nUse this after a long coding-agent run to decide whether the next prompt should\nsplit the task, avoid a failing tool path, add missing tests, or reset context.\n\n### CI Health Check\n\n```bash\nagenttrace --overview --fail-under-health 80 --fail-on-critical\n```\n\nUse this when agent session logs are available in CI and the team wants a simple\nguard against critical anomalies or unhealthy runs.\n\n## Best Practices\n\n- Start with `--doctor` when session discovery is uncertain.\n- Report missing fields plainly; do not invent cost, model, latency, or health data.\n- Treat prompts, code, and session contents as private local data.\n- Prefer JSON output for automation and Markdown output for human review.\n- Use trace metrics for process failures and diff\u002Freference review for semantic drift.\n\n## Limitations\n\n- agenttrace can only analyze logs that are present locally or provided as exports.\n- Some agents do not expose enough fields to infer cost, model, cache use, or latency.\n- Healthy trace metrics do not prove the final code is correct; still run tests and review diffs.\n- CI gates should start as advisory until the team understands normal baseline behavior.\n\n## Security & Safety Notes\n\n- Do not upload private session logs to external services unless the user explicitly approves it.\n- Do not overwrite user reports unless they requested that exact output path.\n- Avoid printing secrets found in prompts, tool output, environment variables, or logs.\n\n## Common Pitfalls\n\n- **Problem:** No sessions are found.\n  **Solution:** Run `agenttrace --doctor`, then point agenttrace at the exported file or log directory.\n\n- **Problem:** A run looks cheap and fast but produced the wrong refactor.\n  **Solution:** Compare the session against a prior attempt or known-good diff; cost metrics alone will miss semantic drift.\n\n- **Problem:** CI fails too often after adding a health gate.\n  **Solution:** Start with JSON or Markdown reporting, inspect normal baselines, then tighten thresholds gradually.\n\n## Related Skills\n\n- `@langfuse` - Use for production LLM application tracing and evaluation.\n- `@observability-engineer` - Use for broader service monitoring, SLOs, and incident workflows.\n","# agenttrace Session Audit\n\n## Overview\n\nUse this skill to inspect local AI coding-agent sessions with\n[agenttrace](https:\u002F\u002Fgithub.com\u002Fluoyuctl\u002Fagenttrace). It focuses on the process\nbehind a run: token and cost spikes, tool failures, retry loops, latency gaps,\nanomalies, health scores, and session-to-session diffs.\n\nagenttrace is local-first and reads session logs from tools such as Claude Code,\nCodex CLI, Gemini CLI, Aider, Cursor exports, OpenCode, Qwen Code, Kimi, and\ngeneric JSON or JSONL traces.\n\n## When to Use This Skill\n\n- Use when a user asks why an AI coding run was slow, expensive, shallow, or unreliable.\n- Use when reviewing local agent logs before retrying a failed or suspicious task.\n- Use when building a lightweight CI health gate for AI-assisted coding sessions.\n- Use when comparing two attempts and looking for changed tool paths, retries, or cost patterns.\n\n## How It Works\n\n### Step 1: Discover Available Sessions\n\nPrefer an installed `agenttrace` binary when it is available on `PATH`. If the\ncurrent repository is `luoyuctl\u002Fagenttrace`, use `go run .\u002Fcmd\u002Fagenttrace`\ninstead.\n\n```bash\nagenttrace --doctor\nagenttrace --overview\n```\n\nIf no sessions are detected, report the directories checked by `--doctor` and\nask for the exported session file or log directory.\n\n### Step 2: Produce a Human-Readable Audit\n\nUse Markdown when the user wants a concise report they can inspect or share.\n\n```bash\nagenttrace --overview -f markdown -o agenttrace-overview.md\n```\n\nIn the report, lead with the highest-risk sessions and explain why they matter:\ncritical anomalies, repeated tool failures, token or cost waste, long latency\ngaps, low health scores, and suspiciously shallow sessions.\n\n### Step 3: Inspect One Session or Directory\n\nUse the latest session for a quick check, or pass an explicit export path when\nthe user provides one.\n\n```bash\nagenttrace --latest\nagenttrace --latest -f json\nagenttrace path\u002Fto\u002Fsession-or-export.json\nagenttrace --overview -d path\u002Fto\u002Fsession-dir\n```\n\n### Step 4: Compare Attempts When Semantics Matter\n\nToken and latency metrics can look healthy even when an agent confidently takes\nthe wrong implementation path. When the risk is semantic drift, pair the trace\naudit with a diff against a previous or known-good attempt.\n\nLook for:\n\n- changed files or commands that diverge from the intended task\n- missing tests or verification steps compared with the reference attempt\n- repeated edits around the same files without a clear reason\n- lower cost that came from skipping necessary exploration\n\n### Step 5: Add Automation Gates\n\nFor CI or repeatable team workflows, use JSON output or health thresholds.\n\n```bash\nagenttrace --overview -f json -o agenttrace-overview.json\nagenttrace --overview --fail-under-health 80 --fail-on-critical --max-tool-fail-rate 15\n```\n\nTune thresholds to the project. A strict gate is useful for critical workflows;\na reporting-only command is better while the team is learning its baseline.\n\n## Examples\n\n### Quick Local Review\n\n```bash\nagenttrace --overview\nagenttrace --latest\n```\n\nUse this after a long coding-agent run to decide whether the next prompt should\nsplit the task, avoid a failing tool path, add missing tests, or reset context.\n\n### CI Health Check\n\n```bash\nagenttrace --overview --fail-under-health 80 --fail-on-critical\n```\n\nUse this when agent session logs are available in CI and the team wants a simple\nguard against critical anomalies or unhealthy runs.\n\n## Best Practices\n\n- Start with `--doctor` when session discovery is uncertain.\n- Report missing fields plainly; do not invent cost, model, latency, or health data.\n- Treat prompts, code, and session contents as private local data.\n- Prefer JSON output for automation and Markdown output for human review.\n- Use trace metrics for process failures and diff\u002Freference review for semantic drift.\n\n## Limitations\n\n- agenttrace can only analyze logs that are present locally or provided as exports.\n- Some agents do not expose enough fields to infer cost, model, cache use, or latency.\n- Healthy trace metrics do not prove the final code is correct; still run tests and review diffs.\n- CI gates should start as advisory until the team understands normal baseline behavior.\n\n## Security & Safety Notes\n\n- Do not upload private session logs to external services unless the user explicitly approves it.\n- Do not overwrite user reports unless they requested that exact output path.\n- Avoid printing secrets found in prompts, tool output, environment variables, or logs.\n\n## Common Pitfalls\n\n- **Problem:** No sessions are found.\n  **Solution:** Run `agenttrace --doctor`, then point agenttrace at the exported file or log directory.\n\n- **Problem:** A run looks cheap and fast but produced the wrong refactor.\n  **Solution:** Compare the session against a prior attempt or known-good diff; cost metrics alone will miss semantic drift.\n\n- **Problem:** CI fails too often after adding a health gate.\n  **Solution:** Start with JSON or Markdown reporting, inspect normal baselines, then tighten thresholds gradually.\n\n## Related Skills\n\n- `@langfuse` - Use for production LLM application tracing and evaluation.\n- `@observability-engineer` - Use for broader service monitoring, SLOs, and incident workflows.\n",{"name":5,"risk":24,"tags":25,"tools":30,"author":35,"source":36,"license":15,"category":37,"date_added":38,"description":7,"source_repo":39,"source_type":36,"license_source":40},"safe",[26,27,28,29],"ai-coding","observability","cost-tracking","session-analysis",[31,32,33,34],"claude","cursor","gemini","codex-cli","luoyuctl","community","development","2026-05-10","luoyuctl\u002Fagenttrace","https:\u002F\u002Fgithub.com\u002Fluoyuctl\u002Fagenttrace\u002Fblob\u002Fmaster\u002FLICENSE","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fdevelopment\u002Fagenttrace-session-audit","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill agenttrace-session-audit",{"tool":53,"command":54},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill agenttrace-session-audit",{"tool":56,"command":57},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill agenttrace-session-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fdevelopment\u002Fagenttrace-session-audit\u002FSKILL.md",true,[],[62,70,77,84,91,98],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":69},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":69},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":69},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":69},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":69},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":69},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]