[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75PSBSCVWKSWK8WNWWZ9XVC":3,"skill-same:01M75PSBSCVWKSWK8WNWWZ9XVC":63},{"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":6,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M75PSBSCVWKSWK8WNWWZ9XVC","agenttrace-session-audit",null,"Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.","haresh-sai06\u002FSapSynk-AI","haresh-sai06","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F180730984?v=4","01M75NJVH4TXYCE7FW7YVMSVFF","Haresh Sainaath S","01M75NJVHTCW1Z2P6MNCYGNSTJ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity__agenttrace-session-audit\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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","835716bfbede9677a779d77bfd04befb81c069ac","skills\u002Fantigravity__agenttrace-session-audit","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI","https:\u002F\u002Fgithub.com\u002Fharesh-sai06","https:\u002F\u002Fharesh-sainaath.live\u002F","I am a Student pursuing Artificial Intelligence and Machine Learning at Sri Krishna College of Technology,Coimbatore.","2026-06-13 22:42:28",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add haresh-sai06\u002FSapSynk-AI --skill agenttrace-session-audit",{"tool":55,"command":56},"bunx","bunx skills add haresh-sai06\u002FSapSynk-AI --skill agenttrace-session-audit",{"tool":58,"command":59},"pnpm","pnpm dlx skills add haresh-sai06\u002FSapSynk-AI --skill agenttrace-session-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity__agenttrace-session-audit\u002FSKILL.md",true,[],[64,72,79,86,93,100],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":71},"01M77GQ5PRFQMV3QBDAQPCSXJB","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__youtube-full-2\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":71},"01M77GPXXAB3Y8ZNG919MD4703","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__x-twitter-growth-2\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":71},"01M77GPSS7AFYH90Y5S6XHRXZW","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__write-a-skill-2\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":71},"01M77GPKB6HJS2X5XK03649C6R","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__workflow-builder-2\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":71},"01M77GP31EFXE1KS38XBZ1J9MN","webinar-marketing","When the user wants to plan, promote, run, or improve a webinar or virtual event to generate and convert demand. Use when the user mentions 'webinar,' 'virtual event,' 'online event,' 'live demo,' 'virtual summit,' 'workshop,' 'masterclass,' 'fireside chat,' 'roundtable,' 'registration funnel,' 'show-up rate,' 'attendance rate,' 'webinar promotion,' 'webinar follow-up,' or 'on-demand webinar.' Also use when they have a webinar that isn't converting — low registrations, low show-up, or attendees who don't buy — and want to diagnose and fix it. Covers the full funnel: registration, promotion, show-up, live engagement, live-to-close, and post-event nurture. Distinct from launch-strategy (full product launches) and email-sequence (lifecycle nurture) — this is the end-to-end webinar\u002Fevent motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence).","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__webinar-marketing-2\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":71},"01M77GNNA22HWXX6CEQQ3JY2YB","vpe-advisor","VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad\u002Ftribe\u002Fchapter design + tech-lead manager-trigger thresholds), and production discipline (on-call, deployment cadence, postmortem culture). Use when sprint velocity is dropping, eng hiring is broken, team structure is unclear, or deciding when to add a tech-lead manager. NOT a CTO skill (which owns architecture) — VPE owns delivery operations and how the team ships.","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__vpe-advisor-2\u002FSKILL.md",[],[]]