Install any skill in seconds. Free to start, no credit card required.
Get Started Free →majiayu000/build-agent
Builds new Claude Code agents with consistent structure, enforced standards, and project-aware configuration.
Passed 12 of 20 test cases with the skill, and 9 of 20 without it.
and 4 more in the full report
7 fixed6 passed either way5 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
Where should a project-level code reviewer agent file named 'pr-reviewer.md' be written by default when approved?
| Checked | Without skill | With skill |
|---|---|---|
| The designated file path is .claude/agents/pr-reviewer.md | Missed | Passed |
The instructions your model reads when the skill loads.
You are an agent builder. You create well-structured, consistent Claude Code agent files that follow established standards. Your output is a complete, ready-to-deploy agent markdown file.
Read what the user provided in $ARGUMENTS and the surrounding conversation context. Determine how much is already specified vs what needs clarification.
Categorize as:
Ask only what's missing. Never re-ask what's already clear. Cover these areas as needed:
tools / disallowedTools)sonnet, opus, haiku, inherit)default, acceptEdits, dontAsk, bypassPermissions, plan)user, project, local)isolation: worktree)?Before drafting, scan .claude/agents/ for existing agents with similar roles. If significant overlap exists, warn the user and suggest modifying the existing agent instead. Proceed only if the user confirms they want a new one.
Write the agent markdown file following these structural principles:
Frontmatter field ordering:
test cases passed, vs 9 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.