Evolve agent definitions in agents/*.md via multi-agent self-review. Spawns agents to review themselves, enforces Content Gate and 500-line budget, applies edits. Trigger: "evolve agents", "improve agents", "grow the team", "refine agents".
AI agent orchestrator — manage teams of AI agents that work on your codebase in parallel. Use when the user wants to: run multiple agents, coordinate AI work, deploy agent teams, manage tasks/goals/agents, check orchestrator status, or mentions 'orch', 'orchestry', 'agents team', 'agent orchestration'.
Expose orxhestra agents as A2A protocol endpoints or connect to remote A2A agents.
API-first email for AI agents. Create inboxes, send/receive emails, webhooks, agent identity. Use when agents need email identity, sending emails, or email-based workflows.
Improve or create AGENTS.md files that serve as shared instructions for AI coding agents (Claude, Gemini, etc.). Use this skill whenever the user mentions AGENTS.md, CLAUDE.md, GEMINI.md, agent instructions, agent configuration, or wants to improve how AI agents behave in their project. Also trigger when the user says "improve my instructions", "agents file", "update my rules", or asks about best practices for configuring coding agents. If in doubt and the task involves AI agent instruction files, use this skill. --- You help users write and improve AGENTS.md files — shared instruction files that AI coding agents (Claude, Gemini, etc.) read at the start of every session. The goal is a single file that works across platforms via symlinks. Read `references/BEST_PRACTICES.md` before analyzing or writing any AGENTS.md content. It contains the patterns extracted from official documentation that inform every decision below. ## Core Workflow ### 1. Assess the Current State Before proposing changes, read the target file and evaluate it against these dimensions: - **Length** — is it under 200 lines? Ideally under 100? Agents have a budget of ~150 instructions they can reliably follow, and the system prompt already uses ~50. - **Structure** — does it use markdown headers to group related instructions? Or is it a wall of text / a single giant list? - **Specificity** — are instructions concrete and verifiable ("use 2-space indentation") or vague ("write clean code")? - **Contradictions** — do any rules conflict with each other? - **Scope mixing** — does it blend personal preferences with project-level standards? - **Signal-to-noise** — does every instruction pass the conciseness test ("would removing this cause the agent to make mistakes")? Are there instructions the agent would follow anyway without being told? - **Completeness** — is it missing key sections (Priorities, Never/Hard Rules, Common Commands, Architecture, Workflow, Tooling)? Score: 1 = all present, 2 = 1-2 missin
Author, edit, review, or refactor meridian agent profiles — the markdown files with YAML frontmatter that live in an `agents/` directory and define reusable spawn configurations (model, system prompt, tools, permissions, skills). Load this skill whenever you're writing an agent from scratch, tweaking an existing profile, splitting one agent into several, reviewing an agent for quality, or deciding whether something should be an agent at all. Phrases that should trigger this skill: "write an agent", "create a profile", "edit this agent", "add a reviewer agent", "refactor the coder agent", "this agent's prompt needs work", "add tools to this profile", "tighten up this agent's description". --- # agent-creator A guide for writing meridian agent profiles that are reusable, caller-agnostic, and age well as models and workflows evolve. Load this skill before touching any file under a `meridian-base/`, `meridian-dev-workflow/`, or similar source submodule's `agents/` directory. ## Hard rule: edit source, never `.agents/` `.agents/` is generated output from `meridian mars sync`. Anything you edit there is overwritten the next time someone runs sync, so the edit is invisible to everyone else and disappears on the next pull. Edit the source submodule instead — `meridian-base/agents/<name>.md`, `meridian-dev-workflow/agents/<name>.md`, or whichever repo owns the profile.
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.
Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4) Establishing review and quality gates, (5) Managing async communication and artifact sharing between agents.
Scan running Claude sessions to see what other agents are working on. Use when asked "what are the other agents doing", "check other sessions", "what's running", "scan agents", "who's working on what", or before picking up new work to avoid overlap. --- # Agents: Scan Running Claude Sessions Runs `scan.sh` to inspect all tmux sessions running Claude and report what each is doing. ## Usage ```bash bash ~/.claude/skills/agents/scripts/scan.sh # all sessions bash ~/.claude/skills/agents/scripts/scan.sh floom # only floom/* sessions bash ~/.claude/skills/agents/scripts/scan.sh openpaper # only openpaper/* sessions ``` ## What It Shows
This skill should be used when the user asks to "configure agents", "create a custom agent", "set up agent permissions", "customize agent behavior", "switch agents", or needs guidance on OpenCode agent system.
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.
Protect .env secrets from AI agents. Real credentials encrypted in a vault — agents see structurally valid sandbox values on disk.
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 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:
