Use when you need to create a new custom skill for a profile - guides through gathering requirements, creating directory structure, writing SKILL.md, and optionally adding bundled scripts
npx skills add https://github.com/microsoft/FluidFramework --skill creating-skills
<required>
*CRITICAL* Add the following steps to your Todo list using TodoWrite:
</required>
This skill guides you through creating custom skills that persist across sessions. Skills are stored in profile directories and can include markdown instructions, checklists, and optional bundled scripts.
Every skill must start with a required checklist block:
<required>
*CRITICAL* Add the following steps to your Todo list using TodoWrite:
1. <step 1>
2. <step 2>
...
</required>
This is the *most important* part of a skill.
Each step may have guidelines underneath. For example:
1. Create a directory.
Use `mkdir foo/bar`
2. Make a file.
...
Skills may be bundled with scripts. Scripts are simple code cli tools that do various things deterministically.
Any scripts you write should be entirely self contained. Ask the user which
language they prefer.
The scripts should be callable from the Bash tool.
The script should be stored in the same place as the skill. Add a section to the
SKILL.md on how to use the script. If the script is required to be called, add
that instruction to the <required> block.
Document which tools are necessary for the skill.
The SKILL should explicitly encourage writing code. The agent should be told to write code to call a tool any time the agent needs to call any tools more than once. The agent should write code instead of calling tools itself.
Steps that reference tools and APIs should inline them in the step by step process.
<good-example>
<system-reminder> Auth credentials can be found at /home/foobar/authentication/auth.txt
</good-example>
<bad-example>
Tools: Slack, Gmail API
</bad-example>
<good-example>
Read https://raw.githubusercontent.com/tilework-tech/nori-skillsets/96012bcfcd9482b248debed7b9a7fc7c345f76e1/src/cli/features/claude-code/profiles/config/amol/skills/finishing-a-development-branch/SKILL.md
</good-example>
<good-example>
Read https://raw.githubusercontent.com/tilework-tech/nori-skillsets/96012bcfcd9482b248debed7b9a7fc7c345f76e1/src/cli/features/claude-code/profiles/config/amol/skills/webapp-testing/SKILL.md
</good-example>
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Curated collection of high-quality prompts for various use cases. Includes role-based prompts, task-specific templates, and prompt refinement techniques. Use when user needs prompt templates, role-play prompts, or ready-to-use prompt examples for coding, writing, analysis, or creative tasks.
Convert abstract edge concepts into strategy draft variants and optional exportable ticket YAMLs for edge-candidate-agent export/validation.
INVOKE THIS SKILL when writing ANY LangGraph code. Covers StateGraph, state schemas, nodes, edges, Command, Send, invoke, streaming, and error handling.
Analyze the protocol layer between agent harness and LLM model. Use when (1) understanding message wire formats and API contracts, (2) examining tool call encoding/decoding mechanisms, (3) evaluating streaming protocols and partial response handling, (4) identifying agentic chat primitives (system prompts, scratchpads, interrupts), (5) comparing multi-provider abstraction strategies, or (6) understanding how frameworks translate between native LLM APIs and internal representations.
Translate SKILL.md and README.md files into multiple languages for sharing skills internationally
| Shared workflow for editing Langfuse's repo-owned agent setup under `.agents/`. Use when changing AGENTS files, shared skills, `.agents/config.json`, generated shim behavior, provider discovery paths, or install-time agent sync.
>- Summarizes Google Cloud Data Lineage graphs to help users debug data quality issues and understand data provenance for BQ/GCS. Use when summarizing upstream and downstream data flows, and presenting complex lineage data as an intuitive Markdown report. Don't use for generic BigQuery queries, editing lineage relationships, or downstream deprecation. Don't use for downstream blast-radius impact analysis (use datalineage-bigquery-asset-impact-analysis skill instead).
Take microsoft/creating-skills from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.