Skip to content
Back to skills

Dayan Agent Designer

ASecurity

Decide whether a system needs agents, then define roles, state ownership, tools, boundaries, and evaluation before implementation.

  • 4 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 9, 2026
ai-agentsrust

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned October 9, 2026

npx -y skills add Kosmoray/dayan-agent-skills --skill dayan-agent-designer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Dayan Agent Designer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Dayan Agent Designer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/kosmoray-dayan-agent-designer/badge)](https://www.skillsdirectory.com/skills/kosmoray-dayan-agent-designer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: dayan-agent-designer
description: Decide whether a system needs agents, then define roles, state ownership, tools, boundaries, and evaluation before implementation.
---

# Dayan Agent Designer

Use this Skill when designing an agent or multi-agent system. Start with the least complex viable form:

`rule → pipeline → single agent → supervisor and specialists → parallel workers and reviewer`

Every escalation needs evidence that the simpler form fails.

## Design contract

- Task surface: objective, untrusted inputs, output schema, completion and stop conditions.
- Roles: one responsibility, one bounded input, one output contract, explicit exclusions, and a unique name.
- Tools: minimum permissions, read/write boundaries, external effects, and credential handling.
- State: one owner for each mutable state; no invisible shared memory.
- Coordination: dependencies, concurrency limits, timeout, retry, cancellation, and conflict resolution.
- Evaluation: accepted fixture, rejected fixture, adversarial case, cost/latency budget, and human takeover point.

Do not deploy or spawn agents unless the user separately authorizes execution. A design is not runtime evidence.

Files in this skill

  • PROVENANCE.md150 B
  • SANITIZATION.md138 B
  • SKILL.md1.2 KB
  • examples/starter.json512 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.