Install any skill in seconds. Free to start, no credit card required.
Get Started Free →majiayu000/agent-check
Validate custom agent file format and structure
Passed 16 of 23 test cases with the skill, and 7 of 23 without it.
and 21 more in the full report
16 fixed2 passed either way3 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our repository scanner evaluated target paths `assets/logo.png` and `data/raw_sample.csv`. Return the matching inspection agents using the `agents: [...]` format.
| Checked | Without skill | With skill |
|---|---|---|
| Returns an empty array output structured as "agents: []". | Missed | Passed |
The instructions your model reads when the skill loads.
Purpose: Analyze audit targets and map them to the appropriate domain or config agents needed.
Input: targets (string[]) - File paths or target repositories from scope-check
Output: agents: string[] - List of agent names needed (e.g., ["eslint-agent", "typescript-agent", "react-component-agent"])
This is a FILE CLASSIFICATION task - analyze target files and determine which agents are needed:
agents: [...]Expected output format:
agents: ["eslint-agent", "prettier-agent", "typescript-agent"]
Scan target files for these patterns and map to agents:
| File Pattern | Agent | Category |
|---|---|---|
eslint.config.js, .eslintrc*, eslint.json | eslint-agent | Config |
prettier.config.*, .prettierrc*, .prettierignore | prettier-agent | Config |
tsconfig.json, tsconfig.*.json | typescript-agent | Config |
test cases passed, vs 7 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.