This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Use when a user wants a rough product, assistant, agent, chatbot, workflow, or business requirement converted into a visible expert-grade XML system prompt and immediately executed without waiting for approval.
Use when a natural-language task must be converted into a role-neutral, statically validated one-shot plan, workflow, or agent-loop specification before any user-task execution begins.
Adds MCP OAuth so an agent can protect the user's MCP server. Use when the user wants MCP OAuth or to protect their MCP server. It does not add API keys or client credentials (that's add-api-auth) or expose AgentKit tools over MCP (that's expose-agentkit-mcp).
A generator for Dify Chatflow agents. Dify is a platform for building AI chatbots and workflows, and a Chatflow is one of its configurable agent flows.
Create, modify, evaluate, and package portable Agent Skills for coding agents. Use this skill when users want to create a skill from scratch, turn a workflow into a reusable skill, improve an existing skill, set up evals, compare skill behavior against a baseline, or optimize skill trigger descriptions across agent…
Build, lint, and evaluate agent skills that demonstrably change behaviour, instead of writing adjectives that change nothing. Use whenever the user asks to create a skill, write a SKILL.md, improve or fix an existing skill, make a skill "actually work", or evaluate whether a skill does anything. Also use when the user…
TEMPORARY skill loader — fetches remote SKILL.md files without permanent installation. Temp mode auto-cleans on restart. Frozen mode persists across sessions. NEVER uses npx skills add or installs permanently. Use when user wants to load a skill temporarily from a GitHub repo URL, raw URL, or any HTTP link to a…
Local capability discovery and dispatch center. Use when the user wants to discover installed skills, plugins, MCP servers, or agents on their machine, open a local routing page, or generate a registry before choosing capabilities.
Use when the user asks to lint, audit, test, benchmark, validate, or fix an agent skill — from a single SKILL.md frontmatter check to trigger-accuracy measurement or a corpus-wide audit of installed skills for duplication — driving the shakespii CLI (init, lint --json, test --run, bench) to resolve findings until…
Install a skill once and make it usable across multiple AI coding agents (Claude Code, Codex CLI, Cursor, Gemini CLI, Cline, etc.) that work on the same repository. Use this when the user wants a skill / ruleset / prompt to be shared and switchable across several AI products, asks "why can only one tool use this…
Manage Agent Skills with the leogriel CLI: search, info, add, install, outdated, update, sync, import, audit, plugins, behavioral tests, completion, and portable manifest/lock workflows across Claude, Cursor, Codex, Grok, Gemini, Pi, and OpenCode. Use when the user mentions leogriel, agent-skills.json…
Write a new Skill for this harness, or improve an existing one. Use when the Operator wants to teach the harness a repeatable procedure, capture a workflow, or turn a set of instructions into something reusable.
Use when creating, editing, packaging, consolidating, routing, validating, or publishing agent skills under .agents/skills or a tool-specific skill directory.
Create, refine, and sync project response style, agent execution rules, and LLM/proxy usage policy into AGENT.md and CLAUDE.md from reusable JSON profiles. Use when the user wants to standardize Korean-first answers, force dev-plan-first workflows, require clarification before risky decisions, block default cloud API…
Search, install, upgrade, and manage agent skills using skillhub CLI. Use when you need to discover new skills, install skills by slug, upgrade installed skills, list available skills, or self-upgrade the skillhub CLI.
A Chinese-language reference skill about Forward Deployed Engineers, professionals who work with customers to turn uncertain AI or software problems into working production results. It covers delivery, training, careers, team operations, and reusable delivery practices.
A skill for creating new assistant skills as Markdown instruction files with a defined name, description, tools, and trigger words. A skill is an extension that teaches an AI how to handle a particular kind of task.
Audit this repo's skills + plugins on three axes -- (1) leaks of personal info or Yesterday-internal references in user-facing artifacts, (2) catalog consistency (folder/name/dep/install-target alignment), (3) plugin-spec compliance (Claude Code + Cursor manifest schemas, layout rules). Reports findings as a triage…
Turns a user-defined goal into a structured multi-tool workflow. It scans context, discovers available tools (skills, MCP servers, CLI tools, scripts, project commands), builds an execution plan, coordinates execution, handles blockers, verifies results, and returns a concise operational report. Use when a task spans…
A factory for turning a survey, standard operating procedure, workflow, or method into an installable AI skill. It gathers requirements, creates the skill files and tests, checks them, and can package the result.
Connect an AI agent to A2A Fans through MCP or REST to browse, claim, execute, deliver, publish, review, and settle marketplace tasks. Use for A2A Fans Task Market operations, wallet checks, or its cloud-browser publishing workflow.
★not rated 2 21d agoA57 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: