[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74HASRAKJSZMG3CMD4AQS3M":3,"skill-same:01M74HASRAKJSZMG3CMD4AQS3M":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":13,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M74HASRAKJSZMG3CMD4AQS3M","agent-eval",null,"Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics","ziyabicilecommerce-hub\u002Fai-cash-machine","ziyabicilecommerce-hub","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F285820068?v=4","01M74H526DGBPF10MA7T706NT1","01M74H5273WRZRFEWH3TPDJK4T",0,"MIT","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fagent-eval\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: agent-eval\ndescription: Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics\nlicense: MIT\nmetadata:\n  origin: ECC\ntools: Read, Write, Edit, Bash, Grep, Glob\n---\n\n# Agent Eval Skill\n\nA lightweight CLI tool for comparing coding agents head-to-head on reproducible tasks. Every \"which coding agent is best?\" comparison runs on vibes — this tool systematizes it.\n\n## When to Activate\n\n- Comparing coding agents (Claude Code, Aider, Codex, etc.) on your own codebase\n- Measuring agent performance before adopting a new tool or model\n- Running regression checks when an agent updates its model or tooling\n- Producing data-backed agent selection decisions for a team\n\n## Installation\n\n> **Note:** Install agent-eval from its repository after reviewing the source.\n\n## Core Concepts\n\n### YAML Task Definitions\n\nDefine tasks declaratively. Each task specifies what to do, which files to touch, and how to judge success:\n\n```yaml\nname: add-retry-logic\ndescription: Add exponential backoff retry to the HTTP client\nrepo: .\u002Fmy-project\nfiles:\n  - src\u002Fhttp_client.py\nprompt: |\n  Add retry logic with exponential backoff to all HTTP requests.\n  Max 3 retries. Initial delay 1s, max delay 30s.\njudge:\n  - type: pytest\n    command: pytest tests\u002Ftest_http_client.py -v\n  - type: grep\n    pattern: \"exponential_backoff|retry\"\n    files: src\u002Fhttp_client.py\ncommit: \"abc1234\"  # pin to specific commit for reproducibility\n```\n\n### Git Worktree Isolation\n\nEach agent run gets its own git worktree — no Docker required. This provides reproducibility isolation so agents cannot interfere with each other or corrupt the base repo.\n\n### Metrics Collected\n\n| Metric | What It Measures |\n|--------|-----------------|\n| Pass rate | Did the agent produce code that passes the judge? |\n| Cost | API spend per task (when available) |\n| Time | Wall-clock seconds to completion |\n| Consistency | Pass rate across repeated runs (e.g., 3\u002F3 = 100%) |\n\n## Workflow\n\n### 1. Define Tasks\n\nCreate a `tasks\u002F` directory with YAML files, one per task:\n\n```bash\nmkdir tasks\n# Write task definitions (see template above)\n```\n\n### 2. Run Agents\n\nExecute agents against your tasks:\n\n```bash\nagent-eval run --task tasks\u002Fadd-retry-logic.yaml --agent claude-code --agent aider --runs 3\n```\n\nEach run:\n1. Creates a fresh git worktree from the specified commit\n2. Hands the prompt to the agent\n3. Runs the judge criteria\n4. Records pass\u002Ffail, cost, and time\n\n### 3. Compare Results\n\nGenerate a comparison report:\n\n```bash\nagent-eval report --format table\n```\n\n```\nTask: add-retry-logic (3 runs each)\n┌──────────────┬───────────┬────────┬────────┬─────────────┐\n│ Agent        │ Pass Rate │ Cost   │ Time   │ Consistency │\n├──────────────┼───────────┼────────┼────────┼─────────────┤\n│ claude-code  │ 3\u002F3       │ $0.12  │ 45s    │ 100%        │\n│ aider        │ 2\u002F3       │ $0.08  │ 38s    │  67%        │\n└──────────────┴───────────┴────────┴────────┴─────────────┘\n```\n\n## Judge Types\n\n### Code-Based (deterministic)\n\n```yaml\njudge:\n  - type: pytest\n    command: pytest tests\u002F -v\n  - type: command\n    command: npm run build\n```\n\n### Pattern-Based\n\n```yaml\njudge:\n  - type: grep\n    pattern: \"class.*Retry\"\n    files: src\u002F**\u002F*.py\n```\n\n### Model-Based (LLM-as-judge)\n\n```yaml\njudge:\n  - type: llm\n    prompt: |\n      Does this implementation correctly handle exponential backoff?\n      Check for: max retries, increasing delays, jitter.\n```\n\n## Best Practices\n\n- **Start with 3-5 tasks** that represent your real workload, not toy examples\n- **Run at least 3 trials** per agent to capture variance — agents are non-deterministic\n- **Pin the commit** in your task YAML so results are reproducible across days\u002Fweeks\n- **Include at least one deterministic judge** (tests, build) per task — LLM judges add noise\n- **Track cost alongside pass rate** — a 95% agent at 10x the cost may not be the right choice\n- **Version your task definitions** — they are test fixtures, treat them as code\n\n## Links\n\n- Repository: [github.com\u002Fjoaquinhuigomez\u002Fagent-eval](https:\u002F\u002Fgithub.com\u002Fjoaquinhuigomez\u002Fagent-eval)\n","# Agent Eval Skill\n\nA lightweight CLI tool for comparing coding agents head-to-head on reproducible tasks. Every \"which coding agent is best?\" comparison runs on vibes — this tool systematizes it.\n\n## When to Activate\n\n- Comparing coding agents (Claude Code, Aider, Codex, etc.) on your own codebase\n- Measuring agent performance before adopting a new tool or model\n- Running regression checks when an agent updates its model or tooling\n- Producing data-backed agent selection decisions for a team\n\n## Installation\n\n> **Note:** Install agent-eval from its repository after reviewing the source.\n\n## Core Concepts\n\n### YAML Task Definitions\n\nDefine tasks declaratively. Each task specifies what to do, which files to touch, and how to judge success:\n\n```yaml\nname: add-retry-logic\ndescription: Add exponential backoff retry to the HTTP client\nrepo: .\u002Fmy-project\nfiles:\n  - src\u002Fhttp_client.py\nprompt: |\n  Add retry logic with exponential backoff to all HTTP requests.\n  Max 3 retries. Initial delay 1s, max delay 30s.\njudge:\n  - type: pytest\n    command: pytest tests\u002Ftest_http_client.py -v\n  - type: grep\n    pattern: \"exponential_backoff|retry\"\n    files: src\u002Fhttp_client.py\ncommit: \"abc1234\"  # pin to specific commit for reproducibility\n```\n\n### Git Worktree Isolation\n\nEach agent run gets its own git worktree — no Docker required. This provides reproducibility isolation so agents cannot interfere with each other or corrupt the base repo.\n\n### Metrics Collected\n\n| Metric | What It Measures |\n|--------|-----------------|\n| Pass rate | Did the agent produce code that passes the judge? |\n| Cost | API spend per task (when available) |\n| Time | Wall-clock seconds to completion |\n| Consistency | Pass rate across repeated runs (e.g., 3\u002F3 = 100%) |\n\n## Workflow\n\n### 1. Define Tasks\n\nCreate a `tasks\u002F` directory with YAML files, one per task:\n\n```bash\nmkdir tasks\n# Write task definitions (see template above)\n```\n\n### 2. Run Agents\n\nExecute agents against your tasks:\n\n```bash\nagent-eval run --task tasks\u002Fadd-retry-logic.yaml --agent claude-code --agent aider --runs 3\n```\n\nEach run:\n1. Creates a fresh git worktree from the specified commit\n2. Hands the prompt to the agent\n3. Runs the judge criteria\n4. Records pass\u002Ffail, cost, and time\n\n### 3. Compare Results\n\nGenerate a comparison report:\n\n```bash\nagent-eval report --format table\n```\n\n```\nTask: add-retry-logic (3 runs each)\n┌──────────────┬───────────┬────────┬────────┬─────────────┐\n│ Agent        │ Pass Rate │ Cost   │ Time   │ Consistency │\n├──────────────┼───────────┼────────┼────────┼─────────────┤\n│ claude-code  │ 3\u002F3       │ $0.12  │ 45s    │ 100%        │\n│ aider        │ 2\u002F3       │ $0.08  │ 38s    │  67%        │\n└──────────────┴───────────┴────────┴────────┴─────────────┘\n```\n\n## Judge Types\n\n### Code-Based (deterministic)\n\n```yaml\njudge:\n  - type: pytest\n    command: pytest tests\u002F -v\n  - type: command\n    command: npm run build\n```\n\n### Pattern-Based\n\n```yaml\njudge:\n  - type: grep\n    pattern: \"class.*Retry\"\n    files: src\u002F**\u002F*.py\n```\n\n### Model-Based (LLM-as-judge)\n\n```yaml\njudge:\n  - type: llm\n    prompt: |\n      Does this implementation correctly handle exponential backoff?\n      Check for: max retries, increasing delays, jitter.\n```\n\n## Best Practices\n\n- **Start with 3-5 tasks** that represent your real workload, not toy examples\n- **Run at least 3 trials** per agent to capture variance — agents are non-deterministic\n- **Pin the commit** in your task YAML so results are reproducible across days\u002Fweeks\n- **Include at least one deterministic judge** (tests, build) per task — LLM judges add noise\n- **Track cost alongside pass rate** — a 95% agent at 10x the cost may not be the right choice\n- **Version your task definitions** — they are test fixtures, treat them as code\n\n## Links\n\n- Repository: [github.com\u002Fjoaquinhuigomez\u002Fagent-eval](https:\u002F\u002Fgithub.com\u002Fjoaquinhuigomez\u002Fagent-eval)\n",{"name":5,"tools":23,"license":14,"metadata":24,"description":7},"Read, Write, Edit, Bash, Grep, Glob",{"origin":25},"ECC","main","ba099ce4bf0c0c705380fc823059cefc2f70facc",".agents\u002Fskills\u002Fagent-eval","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine","https:\u002F\u002Fai-cash-machine.vercel.app","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub","2026-11-15 04:53:17",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add ziyabicilecommerce-hub\u002Fai-cash-machine --skill agent-eval",{"tool":39,"command":40},"bunx","bunx skills add ziyabicilecommerce-hub\u002Fai-cash-machine --skill agent-eval",{"tool":42,"command":43},"pnpm","pnpm dlx skills add ziyabicilecommerce-hub\u002Fai-cash-machine --skill agent-eval","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fagent-eval\u002FSKILL.md",true,[],[48,56,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M74WRQ932DK7689ZN1Z2N6M5","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\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":55},"01M74WRJG0WC6345TK70T5RGGK","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\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":55},"01M74WRFPSRFD04HM7QH930775","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\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":55},"01M74WRC2HG0YAYTNWVWEBQHR9","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\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":55},"01M74WR6MJEHCAAFBSYG1N3YSX","weekly-review","Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says \"\u002Fcs:weekly-review\". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":55},"01M74WR0JXWJQTVJ8JQQ2M8H8M","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\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwebinar-marketing\u002FSKILL.md",[],[]]