The agent skill stack I’d want before production

I keep seeing agent discussions frame skills as “the agent can use tool X.” That feels too loose for production. A skill should probably be closer to a contract what the agent is allowed to propose what inputs it needs what side effects it can trigger what evidence it must produce and how the runtime recovers if it fails halfway. The skill stack I would want before trusting an agent with a real workflow Planning skill Turns an ambiguous goal into an explicit sequence of steps. The plan should become data not just hidden context. Tool-use skill Knows which tool to call but also emits the exact payload schema version and expected receipt. Permission skill Checks whether this step is allowed now. Not just “this agent has access to CRM” but “this exact update is allowed for this account this user and this policy state.” Recovery skill Decides what happens after a timeout crash duplicate request partial write or unknown external state. This should mostly be deterministic. Observation skill Summarizes current state in a way operators can actually use what happened what is pending what is safe to retry and what needs a human. Budget skill Controls token spend tool spend latency and retry limits. An autonomous agent without a budget is just a very polite denial-of-wallet attack on your own system. Escalation skill Knows when to stop. Some actions should require a human approval token before the system can move forward. My current bias the model can be great at planning interpreting messy inputs and proposing actions. But the execution layer should own permissions receipts idempotency and recovery. Curious how others define “skills” in their agent systems. Are they mostly prompts tool wrappers workflow nodes policies or something else