Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mohitagw15856/agent-spec
Specify an autonomous or tool-using AI agent before building it.
Passed 17 of 22 test cases with the skill, and 3 of 22 without it.
and 25 more in the full report
15 fixed2 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
I'm building an AI assistant to handle e-commerce support tickets. It needs to look up order histories via API, issue full or partial refunds, and send discount vouchers to customers. Refund actions can't be undone and cost money. Can you write a formal agent specification document for this system? Please include the core scope, a breakdown table of tools and permissions, control loop limits, guardrail rules, memory management, human handoff triggers, evaluation criteria, and failure recovery protocols.
| Checked | Without skill | With skill |
|---|---|---|
| The document title uses the structure '### Agent Spec: E-commerce Support Assistant' or similar name in the heading format. | Missed | Passed |
| The tool table includes headers for Tool, Purpose, Reversible?, and Gate. | Missed | Passed |
| The refund action is marked as irreversible with a required human approval gate. | Missed | Passed |
The instructions your model reads when the skill loads.
An agent is a model plus tools plus a loop — and the danger lives in the tools and the loop, not the model. This skill specifies an agent so its authority is explicit: what it can do, what needs a human yes, and what happens when it's wrong. Scope and guardrails first; cleverness second.
Ask for these only if they aren't already provided:
1. Goal & scope — the job in one sentence; explicit non-goals and authority limits.
2. Tools / actions — a table; mark each action's reversibility and required permission.
| Tool | Purpose | Reversible? | Gate |
|---|---|---|---|
| search_kb | read context | yes | none |
| send_email | notify | no | human approval |
3. Control loop — plan → act → observe → reflect; the stopping condition; and a hard max-steps / max-cost budget so it can't loop forever.
4. Guardrails & approval gates — which actions require a human yes (default: anything irreversible, outbound, or spending), input/output validation, and allow/deny lists. Pair irreversible actions with a dry-run preview (see action-runner).
5. Memory & state — what it remembers within a task vs. across tasks, and where (link a professional-brain for durable memory).
6. Escalation & handoff — the triggers that stop the agent and route to a human (low confidence, repeated failure, out-of-scope request, high-risk action).
7. Evaluation — task success rate, action correctness, and safety (false-action rate). Define with an ai-eval-plan, and test on adversarial/trap tasks.
8. Failure handling — timeouts, tool errors, hallucinated tool calls, and the safe default (stop and ask, never guess on a high-risk action).
test cases passed, vs 3 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.