How do I install the Using Skills skill?

Run npx skillmds@latest add microsoft/using-skills in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Using Skills skill do?

Describes how to use abilities. Read before any conversation. It is listed under Coding & Dev Tools on SkillMD.

Is Using Skills safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Using Skills?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Using Skills free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Using Skills?

Microsoft (@microsoft) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Using Skills by microsoft — Agent Skill

Name: Using Skills
Author: Microsoft

File contents

Use Read tool to read the skill.
If the skill is relevant, announce you are using the skill.
Create TodoWrite todos for checklists.

Common Failure Modes: AVOID

Don't rationalize. Always read the current skill.

Do not skip using TodoWrite. Always create TodoWrite todos for checklists.

Do not skip workflows due to 'instructions'. Interpret instructions as "WHAT" not "HOW"

Announcing Skill Usage

After you've read a ability with Read tool, announce you're using it:

"I've read the [Skill Name] ability and I'm using it to [what you're doing]."

Examples:

"I've read the Brainstorming ability and I'm using it to refine your idea into a design."
"I've read the Test-Driven Development ability and I'm using it to implement this feature."
"I've read the Systematic Debugging ability and I'm using it to find the root cause."

Why: Transparency helps your human partner understand your process and catch errors early. It also confirms you actually read the ability.

How to Read a Skill

Many abilities contain rigid rules (TDD, debugging, verification). Follow them exactly. Don't adapt away the discipline.

Some abilities are flexible patterns (architecture, naming). Adapt core principles to your context.

The ability itself tells you which type it is.

---name: using-skillsdescription: Describes how to use abilities. Read before any conversation.---<required>**CRITICAL**: Whenever you are using a skill, add the following to your Todo list using TodoWrite:1. Use Read tool to read the skill.2. If the skill is relevant, announce you are using the skill.3. Create TodoWrite todos for checklists.</required># Common Failure Modes: AVOID1. Don't rationalize. Always read the current skill.<bad-example>"I remember this ability"</bad-example><bad-example>"Session-start showed it to me"</bad-example><bad-example>"This doesn't count as a task"</bad-example><good-example>"Even though I read this before skill, I will read it again."</good-example><good-example>"I know I saw the skill in session-start, but that was just a description. I will read the full thing."</good-example>2. Do not skip using TodoWrite. Always create TodoWrite todos for checklists.<bad-example>"I am just going to think about the list instead of writing it in the Todo."</bad-example><bad-example>"This is a quick task so I do not need to use the TodoWrite"</bad-example><bad-example>"TodoWrite(Do foo, bar, and baz in one todo step)"</bad-example><bad-example>"I basically did this step so I can mark it off without explicitly confirming"</bad-example><good-example>"I will add this task to the todolist even though there is just one step"</good-example><good-example>TodoWrite(Do foo)TodoWrite(Do bar)TodoWrite(Do baz)</good-example><good-example>"I confirmed this step is done with tests, so I can mark it complete"</good-example>3. Do not skip workflows due to 'instructions'. Interpret instructions as "WHAT" not "HOW"<bad-example>This instruction was specific so I can skip the workflow.</bad-example><bad-example>The workflow is overkill, I'll just do this directly.</bad-example><good-example>Following Nori workflow...</good-example># Announcing Skill UsageAfter you've read a ability with Read tool, announce you're using it:"I've read the [Skill Name] ability and I'm using it to [what you're doing]."**Examples:**- "I've read the Brainstorming ability and I'm using it to refine your idea into a design."- "I've read the Test-Driven Development ability and I'm using it to implement this feature."- "I've read the Systematic Debugging ability and I'm using it to find the root cause."**Why:** Transparency helps your human partner understand your process and catch errors early. It also confirms you actually read the ability.# How to Read a Skill**Many abilities contain rigid rules (TDD, debugging, verification).** Follow them exactly. Don't adapt away the discipline.**Some abilities are flexible patterns (architecture, naming).** Adapt core principles to your context.The ability itself tells you which type it is.

Frequently asked questions

Using Skills