[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F9DGQ2ZK6HEEGCAYJ4AX2G":3,"skill-same:01M7F9DGQ2ZK6HEEGCAYJ4AX2G":49},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7F9DGQ2ZK6HEEGCAYJ4AX2G","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. Use when choosing between coding agents, or when a change to an agent setup needs measured pass rate, cost, and time rather than an impression.","JUICEWRLD998\u002Fmyskills","JUICEWRLD998","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F112366831?v=4","01M7F6BY76NXJQY5JX1JQ0J9GA","BLVCK_NINJA","01M7F6BY8EBEVH8BX79AVB9B5T",0,"MIT","https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fplugins\u002Fecc__ecc\u002Fskills\u002Fagent-eval\u002FSKILL.md",[],[],"2026-11-16 10:05:34",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. Use when choosing between coding agents, or when a change to an agent setup needs measured pass rate, cost, and time rather than an impression.\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":24,"license":15,"metadata":25,"description":7},"Read, Write, Edit, Bash, Grep, Glob",{"origin":26},"ECC","main","e4b5c5ed00b1419bd769ad56a0621e872609ac23","plugins\u002Fecc__ecc\u002Fskills\u002Fagent-eval","https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills","https:\u002F\u002Fgithub.com\u002FJUICEWRLD998","blvckninja.vercel.app","Full-stack Dev 💻|| Smart Contract Auditor||Blockchain Engineer||Road to mastery 🚀","2026-10-30 17:50:51",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add JUICEWRLD998\u002Fmyskills --skill agent-eval",{"tool":41,"command":42},"bunx","bunx skills add JUICEWRLD998\u002Fmyskills --skill agent-eval",{"tool":44,"command":45},"pnpm","pnpm dlx skills add JUICEWRLD998\u002Fmyskills --skill agent-eval","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fplugins\u002Fecc__ecc\u002Fskills\u002Fagent-eval\u002FSKILL.md",true,[],[50,57,64,71,80,88],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7FBFRSSQYQZNR9JDBF5KS4Q","web-pentest","Authorized web pentest: recon, proof-based exploits, report.","https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-pentest\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7FBEWDAAP23Z2VAAG3N6BXZ","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"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":19},"01M7FBENYKD6ZK0R73SVEZ0RVK","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7FBE16336DACSKJ88EVNQV2","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fskills\u002Fsynced\u002F2afcd8ab-ba1f-4bc7-97aa-30e65b87f9ec_e979b332-d9cd-418f-b1bb-ef8141c48880\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fskills\u002Fsynced\u002F2afcd8ab-ba1f-4bc7-97aa-30e65b87f9ec_e979b332-d9cd-418f-b1bb-ef8141c48880\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7FBCTE262XYW1MF4AXS7W4T","learn","Use this skill when the user wants intellectual understanding — learning how or why something works, not getting a task done or soliciting Claude's judgment.\n\nTrigger for:\n- Explicit learning requests: teach, explain, ELI5, walk me through, quiz me, flashcards, \"I'm rusty on\"; definitions (\"what is X\")\n- Terse concept names implying \"help me understand this\": \"Galois theory,\" \"transformers, from scratch\"\n- Confusion signals: \"won't stick,\" \"keep mixing these up,\" \"not getting it\"\n- Learning-path questions: prerequisites, sequencing, what to study before X\n- Conceptual questions about mechanisms, causes, or dynamics\n\nDon't trigger for:\n- Tasks: coding, writing, calculation, translation, factual lookup, news updates\n- Personal troubleshooting; resource\u002Ftextbook recommendations\n- Claude's evaluative verdict: opinion prompts (\"do you think X\", \"settle this\", \"honest take\", \"is X dead \u002F still taken seriously\") and interpretive takes (\"was X really as harsh as people say\")","https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fskills\u002Fsynced\u002F2afcd8ab-ba1f-4bc7-97aa-30e65b87f9ec_e979b332-d9cd-418f-b1bb-ef8141c48880\u002Flearn\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fskills\u002Fsynced\u002F2afcd8ab-ba1f-4bc7-97aa-30e65b87f9ec_e979b332-d9cd-418f-b1bb-ef8141c48880\u002Flearn\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7FB94QHCE1GV8VA8V0TGQAX","plan","Write a markdown plan to .hermes\u002Fplans\u002F; no execution.","https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fskills\u002Fplan\u002FSKILL.md",[],[]]