benchmark-e2e

Runs end-to-end benchmark pipelines testing skill injection across realistic projects.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/sharad07072007/paras --skill benchmark-e2e-sharad07072007
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark-e2e
Source: https://github.com/sharad07072007/paras/tree/main/.agents/plugins/vercel/.claude/skills/benchmark-e2e
Command: npx skills add https://github.com/sharad07072007/paras --skill benchmark-e2e-sharad07072007

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Manually verifying that a Claude plugin injects the right skills into realistic projects is slow and error-prone. This Skill automates the full loop: creating test projects, exercising skill injection via claude --print, launching dev servers, verifying they respond, analyzing conversation logs, and producing actionable improvement reports. ## Core Features & Use Cases - Four-Stage Pipeline: Chains runner, verify, analyze, and report stages sequentially, aborting on failure and logging NDJSON events to events.jsonl. - Structured Contracts: Uses run-manifest.json to correlate JSONL sessions with projects precisely, and emits machine-readable report.json with verdicts, gaps, and suggested frontmatter patterns. - Self-Improvement Loop: Supports overnight automation with cooldown loops so report.json verdicts can be compared across runs, trending from fail to pass. - Use Case: Run the quick mode (--quick, 3 projects) before committing a change to the vercel-plugin to confirm expected skills like auth, payments, or cron-jobs are still injected correctly. ## Quick Start Ask the AI to run the benchmark-e2e pipeline in quick mode to verify skill injection across the first three test projects.

Frequently Asked Questions about benchmark-e2e

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an end-to-end benchmark for a Claude plugin?

Run `bun run scripts/benchmark-e2e.ts` to execute the full nine-project suite, or add `--quick` to run only the first three projects. The pipeline creates projects, exercises skill injection, verifies dev servers, and generates a report.

How do I verify that skills are injected correctly by a plugin?

The pipeline runs `claude --print` with trace logging, then the analyze stage matches JSONL sessions to projects via run-manifest.json. The report lists expected versus actual skills and flags any missing injections per project slug.

What does the benchmark report.json contain?

report.json includes a runId, timestamp, an overall verdict of pass, partial, or fail, plus gaps listing missing skills per project, recommendations, and suggestedPatterns with copy-pasteable YAML frontmatter fixes.

Can I run the benchmark pipeline overnight automatically?

Yes, wrap the command in a while loop with a sleep cooldown, such as `sleep 3600` between iterations. Each run produces timestamped reports you can diff to track whether the verdict trends from fail toward pass.

Why does the benchmark pipeline abort before finishing all projects?

The orchestrator chains four stages sequentially and aborts on the first failure, recording an abort event in events.jsonl with the failed stage and project slug. Check that file to identify whether the runner, verify, analyze, or report stage failed.