Create or review an AGENTS.md file so coding agents get stable repo-local instructions: environment setup, testing, style, security boundaries, PR policy, and handoff rules.
SkillScore77Maintained
Automatic
◆AI Engineer pack
Last verified 8/18/2026
What it changes
Passed 15 of 19 test cases with the skill, and 11 of 19 without it.
Without skill59%
With skill77%
Checks it passed that the model alone missed
The response includes PR instructions or agent handoff guidelines.
The response replaces the vague wording with a concrete, runnable verification command.
The output requires local execution of build, lint, and test checks prior to PR creation.
and 2 more in the full report
4 fixed13 passed either way5 still failing0 broke
Pass-rate lift
+18 pp
Tokens
-12%
Agent turns
0%
Response time
-28%
Model gemini-3.6-flashMeasured 8/18/2026v117 of 22 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 4
Prompt
Our draft agent instructions include the rule: 'Be careful when changing database schemas and make sure everything is clean.' How should this guideline be rewritten for automated coding agents?
What was checked, without and with the skill
Checked
Without skill
With skill
The response replaces the vague wording with a concrete, runnable verification command.
Missed
Passed
The output advises removing non-actionable advice like 'be careful' in favor of deterministic checks.
Passed
Passed
case-09 · gemini-3.6-flash · 8/18/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md45 linessingle file
AGENTS.md Protocol
Purpose
Create or tighten a repository-level AGENTS.md contract for coding agents.
Treat it as durable operating context, not a chat prompt.
When to Use
Repo has no AGENTS.md, CLAUDE.md, or equivalent agent instructions.
Existing instructions are stale, vague, or missing test commands.
A custom/API/local harness needs stable context it can load every run.
A multi-agent workflow needs explicit handoff and review rules.
Procedure
Inspect repo layout, package managers, CI files, and test commands.
Capture only durable facts and team rules.
Keep commands exact and runnable from the documented directory.
Add security and destructive-operation boundaries.
Add PR/review expectations and required verification.
Keep the file short enough to load every session.
Recommended Sections
Dev environment tips
Testing instructions
Build and lint
Code style
Security boundaries
PR instructions
Agent handoff notes
Quality Bar
Every command has a working directory or clear scope.
No secrets, tokens, or private URLs.
No vague rules such as "be careful" without a concrete check.
No roadmap or marketing text.
Instructions match current CI and package metadata.
Review a Git diff against repository standards and its originating requirements. Use for pull requests, branches, work-in-progress changes, or changes since a commit, tag, or merge-base.