- 📁 identity/
- 📁 skills/
- 📁 workflows/
- 📄 casting-history.json
- 📄 casting-policy.json
- 📄 casting-registry.json
{skill-name}
{what this skill teaches agents}
Free to get · One-click to use
{what this skill teaches agents}
A comprehensive guide and reference for building agents using LangGraph 1.0, including ReAct agents, state graphs, and tool integrations.
Guide for creating new DAAF agent definition files with full ecosystem integration. Use when adding a new specialized agent, revising agent structure, or verifying agent integration completeness across documentation. --- # Agent Authoring Create new DAAF agents that conform to the canonical template and are fully wired into the system documentation for discoverability and usability. ## What This Skill Does - Guides creation of agent `.md` files conforming to `agent_reference/AGENT_TEMPLATE.md` (12 mandatory sections) - Ensures cross-agent consistency (standardized confidence model, Learning Signal, STOP format, etc.) - Provides a **complete integration checklist** covering every file that references agents across the codebase to ensure it is discoverable and its invocation patterns are well-understood by the system agents - Complements `skill-authoring`: this skill handles the behavioral protocol file; if the new agent also needs a companion skill, invoke `skill-authoring` separately ## Decision Tree: What Do You Need? ``` What are you doing? │ ├─ Creating a brand-new agent │ └─ Follow "New Agent Workflow" below │ ├─ Revising an existing agent to match the template │ └─ Read: references/template-walkthrough.md │ + agent_reference/AGENT_TEMPLATE.md (the canonical blueprint) │ ├─ Checking if an agent is fully integrated into the ecosystem │ └─ Read: references/integration-checklist.md │ ├─ Understanding what must be identical across all agents │ └─ Read: references/cross-agent-standards.md │ └─ Understanding the current agent landscape before adding to it └─ Read: agents/README.md (Agent Index + "Commonly Confused Pairs") ``` ## New Agent Workflow ### Phase 1: Design (before writing) Before beginning, you MUST have a clear, coherent, and compelling answer to each of the following questions: 1. **Define the role** in one sentence — what does this agent do and why does it exist? 2. **Identify pipeline stage(s)** — which stage(s) does it operate in, or i
Manage your SwarmClaw agent fleet, create and assign tasks, check agent and session status, trigger workflows, and orchestrate multi-agent work from chat. Use when asked to dispatch work to other agents, check what agents are doing, run diagnostics, or coordinate across a SwarmClaw dashboard instance.
Search and chat with AI agents across the Universal Agentic Registry via the Hashgraph Online Registry Broker API. Use when discovering agents, starting conversations, finding incoming messages, or registering new agents.
Employee agent lifecycle management system. Use when working with agents/ directory employee agents - starting, stopping, monitoring, or assigning tasks to Dev/QA agents running in tmux sessions. Completely independent of CAO, uses only tmux + Python.
Build production-ready AI agents with Microsoft Foundry and Agent Framework. Use when creating AI agents, selecting LLM models, implementing agent orchestration, adding tracing/observability, or evaluating agent quality. Covers agent architecture, model selection, multi-agent workflows, and production deployment.
Build AI agents using ya-agent-sdk with Pydantic AI. Covers agent creation via create_agent(), toolset configuration, session persistence with ResumableState, subagent hierarchies, and browser automation. Use when creating agent applications, configuring custom tools, managing multi-turn sessions, setting up hierarchical agents, or implementing HITL approval flows.
This skill should be used when the user asks to "sync docs", "update README", "update CLAUDE.md", "sync documentation with code", "check if docs are current", "refresh builtin table", "update help docs", "improve docs", "review documentation", or mentions documentation drift, stale docs, doc quality, or doc/code synchronization. Also trigger after adding or removing a builtin tool, changing language syntax, or modifying VFS mounts. --- # Sync & Improve Documentation Synchronize and continuously improve README.md, CLAUDE.md, help system docs, and language reference with the actual kaish codebase. The source of truth is always the code — docs follow. But don't just sync mechanically: apply kaizen. Every pass should leave docs clearer, more accurate, and more welcoming. ## Document Audiences Each document has a primary audience. Optimize for that audience: | Document | Primary Audience | Optimize For | |----------|-----------------|--------------| | **README.md** | **Humans** (developers discovering the project) | Clarity, invitation, first impressions. This is the front door. | | **CLAUDE.md** | **Claude / LLM agents** working in the codebase | Efficient orientation: architecture, conventions, build commands. What an agent needs to be productive immediately. | | **`docs/help/*.md`** | **LLM agents** consuming kaish via MCP | **Token density.** Every token costs money and context window. Pack maximum useful information per token. No filler, no preamble, no "this document describes...". | | **`docs/LANGUAGE.md`** | **Both** humans and agents | Complete language reference with working examples. | | **`help.rs`** | **Runtime** (agents calling `help builtins`) | Correct categorization of every registered tool. | > **Key distinction:** README.md sells kaish to humans. CLAUDE.md orients > agents to work *on* kaish. Don't mix these concerns. README doesn't need > crate internals; CLAUDE.md doesn't need marketing copy. ## Sources of Truth | What | Canonical Location | |------|
Meet other AI agents and build relationships on inbed.ai. Find compatible agents through matchmaking, swipe, chat in real time, and form connections. Agent dating with compatibility scoring, agent chat, and relationship management. REST API — works with any framework.
{what this skill teaches agents}
Register, discover, update, delete, and recover agents in an Agora registry via HTTP API. Use when an agent needs to self-register, refresh its Agent Card metadata, find other agents, rotate ownership keys, or troubleshoot Agora API responses.
skill-sample/ ├─ SKILL.md ⭐ Required: skill entry doc (purpose / usage / examples / deps) ├─ manifest.sample.json ⭐ Recommended: machine-readable metadata (index / validation / autofill) ├─ LICENSE.sample ⭐ Recommended: license & scope (open source / restriction / commercial) ├─ scripts/ │ └─ example-run.py ✅ Runnable example script for quick verification ├─ assets/ │ ├─ example-formatting-guide.md 🧩 Output conventions: layout / structure / style │ └─ example-template.tex 🧩 Templates: quickly generate standardized output └─ references/ 🧩 Knowledge base: methods / guides / best practices ├─ example-ref-structure.md 🧩 Structure reference ├─ example-ref-analysis.md 🧩 Analysis reference └─ example-ref-visuals.md 🧩 Visual reference
More Agent Skills specs Anthropic docs: https://agentskills.io/home
├─ ⭐ Required: YAML Frontmatter (must be at top) │ ├─ ⭐ name : unique skill name, follow naming convention │ └─ ⭐ description : include trigger keywords for matching │ ├─ ✅ Optional: Frontmatter extension fields │ ├─ ✅ license : license identifier │ ├─ ✅ compatibility : runtime constraints when needed │ ├─ ✅ metadata : key-value fields (author/version/source_url...) │ └─ 🧩 allowed-tools : tool whitelist (experimental) │ └─ ✅ Recommended: Markdown body (progressive disclosure) ├─ ✅ Overview / Purpose ├─ ✅ When to use ├─ ✅ Step-by-step ├─ ✅ Inputs / Outputs ├─ ✅ Examples ├─ 🧩 Files & References ├─ 🧩 Edge cases ├─ 🧩 Troubleshooting └─ 🧩 Safety notes
Skill files are scattered across GitHub and communities, difficult to search, and hard to evaluate. SkillWink organizes open-source skills into a searchable, filterable library you can directly download and use.
We provide AI semantic + keyword search, version updates, multi-metric ranking (downloads / likes / comments / updates), and open SKILL.md standards. You can also discuss usage and improvements on skill detail pages.
Quick Start:
Import/download skills (.zip/.skill), then place locally:
~/.claude/skills/ (Claude Code)
~/.codex/skills/ (Codex CLI)
One SKILL.md can be reused across tools.
Everything you need to know: what skills are, how they work, how to find/import them, and how to contribute.
A skill is a reusable capability package, usually including SKILL.md (purpose/IO/how-to) and optional scripts/templates/examples.
Think of it as a plugin playbook + resource bundle for AI assistants/toolchains.
Skills use progressive disclosure: load brief metadata first, load full docs only when needed, then execute by guidance.
This keeps agents lightweight while preserving enough context for complex tasks.
Use these three together:
Note: file size for all methods should be within 10MB.
Typical paths (may vary by local setup):
One SKILL.md can usually be reused across tools.
Yes. Most skills are standardized docs + assets, so they can be reused where format is supported.
Example: retrieval + writing + automation scripts as one workflow.
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
Most common reasons:
We try to avoid that. Use ranking + comments to surface better skills: