ai-agent-design

Designs provider-neutral production AI agent subsystems with contracts, policies, and governance.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill ai-agent-design-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-agent-design
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/ai-agent-design
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill ai-agent-design-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams building AI agents often over-engineer with unnecessary multi-agent topologies or under-specify safety, durability, and evaluation controls. This Skill produces a decision-complete logical architecture that classifies each capability correctly and applies production-grade contracts, policies, and governance before any code is written. ## Core Features & Use Cases - Behavior Classification: Classifies each capability as deterministic code, direct model call, deterministic AI workflow, or agent, then selects the smallest sufficient agent pattern. - Governed System Design: Defines task, tool, context, memory, approval, durability, failure, and evaluation contracts with deterministic control outside model discretion. - AI Stack Handoff: Delegates model, runtime, retrieval, and observability technology selection to ai-stack only when a model-backed capability remains. - Use Case: When asked to design a customer-support agent that drafts answers and sends them after human approval, the Skill classifies the flow as a deterministic AI workflow, defines exact approval binding and idempotent send effects, and hands frozen requirements to ai-stack for component selection. ## Quick Start Ask the agent to design a production AI agent subsystem for your workload, for example: use ai-agent-design to design a bounded diagnostic agent with read-only tools and explicit budgets.

Frequently Asked Questions about ai-agent-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a production AI agent architecture?

Start by freezing a workload contract, then classify each capability as deterministic code, direct model call, deterministic AI workflow, or agent. Apply the smallest sufficient agent pattern, define contracts for tools, context, memory, and approvals, and delegate technology selection to ai-stack.

When should I use a multi-agent pattern instead of a single agent?

Start with one bounded agent and escalate only for a named requirement such as dynamic decomposition, parallel independent work, or real ownership boundaries. Orchestrator-workers, remote agents, and choreography each require explicit justification and conflict policies.

Does this skill select the AI model and framework to use?

No, it freezes behavior, policy, and workload constraints, then hands component and technology selection to ai-stack. If every capability is deterministic code, it records that no AI component is required and skips the handoff entirely.

Can this skill write code or deploy the agent it designs?

No, the skill is advisory and produces only a logical architecture and implementation handoff. It never writes code, assigns repository paths, installs packages, provisions infrastructure, or mutates live systems.

How are approvals and side effects handled in agent designs?

Every consequential effect requires explicit approval bound to the exact action, arguments, approver identity, expiry, and current state. Effects define idempotency keys, duplicate-delivery handling, and reconciliation so ambiguous outcomes are verified before any retry.