agent-spec

Featured

Specify an autonomous or tool-using AI agent before building it. Use when asked to design an AI agent, define an agent's tools and guardrails, scope what an agent is allowed to do, or write an agent spec/PRD. Produces an agent spec — goal & scope, tools with permissions, the control loop, guardrails & approval gates, memory, escalation/handoff, evaluation, and failure handling.

AI & Automation 1,231 stars 221 forks Updated today MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Agent Spec Skill 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. ## Required Inputs Ask for these only if they aren't already provided: - **Job to be done** — the outcome the agent owns, and the boundary of its authority. - **Tools/actions** — what it can call (read APIs, write actions, code execution), and which are irreversible. - **Autonomy level** — fully autonomous, propose-then-approve, or co-pilot. - **Risk surface** — what's the worst thing a wrong action could do (spend money, send a message, delete data)? - **Success definition & escalation** — how "done" is judged, and when it must hand off to a human. ## Output Format ### Agent Spec: [name] **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...

Details

Author
mohitagw15856
Repository
mohitagw15856/pm-claude-skills
Created
6 months ago
Last Updated
today
Language
HTML
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

specify

Interview the user to produce a complete, agent-ready specification, then emit what is needed to build it: for a coded feature/agent a phase-scoped build prompt, or for a skill / declarative agent the artifact itself (SKILL.md / AGENT.md). Surfaces every assumption for review, slices the work into a phased plan, and runs a build-readiness (model/effort) check. Use when the user wants to design, specify, plan, or scope a new agent, feature, or skill; turn a vague idea, PRD, or plan into a rigorous spec; write requirements in EARS / SHALL with testable acceptance criteria; produce a build prompt for a coding agent; or amend, advance, review, audit or sweep an existing spec under specs/ for drift and staleness. Reasoning-driven, one question at a time.

2 Updated yesterday
hmbseaotter
AI & Automation Listed

spec-coach

Interactive spec design coach. Guides through vision, PRD structure, three-tier boundary definition, INVEST user-story quality, specification by example, and measurable success criteria to produce a complete, deployable spec. Use when designing a new skill, agent, feature, or any AI system that needs explicit behavioral boundaries — writing an agent spec, an SRS/requirements doc, a spec.md/plan.md, or running a spec-kit/specify workflow.

1 Updated 4 days ago
michaelalber
AI & Automation Listed

agent-builder

Generate role-specific agent system prompts, tool permissions, and self-review checklists from organizational design artifacts — saved to $HOME/.ai-first-kit/ with optional framework-specific configuration for Claude Code, OpenAI Agents SDK, Anthropic Agent SDK, CrewAI, or custom frameworks. Reads the organizational genome, governance, gates, and role definitions to produce agent configurations that embody a specific role in the organization. Use when the user says 'create agent instructions', 'build an agent', 'agent system prompt', 'configure an agent', 'agent for this role', 'OpenAI agent', 'CrewAI agent', 'create agent config', 'deploy an agent', or 'what tools should this agent have'. Also use when the user has completed role-value-mapper and wants to actually deploy agents that follow the organizational genome, or when they ask 'how do I make an agent follow our rules' or 'how do I create an OpenClaw agent for our org' — even if they don't use the word 'builder'. This skill MUST be consulted because it

6 Updated today
synaptiai