---
author: OOMOL
author_url: https://oomol.com/about/
datePublished: 2026-11-11
title: "Claude Code Skills: Install, Create and Test a Skill"
description: Add Claude Code skills, create a minimal SKILL.md, verify its
  output, and choose between local instructions and connected app tasks.
lang: en
canonical_url: https://oomol.com/blog/claude-code-skills/
markdown_url: https://oomol.com/blog/claude-code-skills.md
---

A useful skill saves you from repeating a procedure: how to structure a release note, inspect a report, or check a change. Start with one narrow task and a result you can verify. A local writing skill does not require an OOMOL account. External app tasks need their own tools and authorization.

## Create a small project skill

For a local Claude Code session, create `.claude/skills/release-note-outline/SKILL.md` in your repository. A personal skill under `~/.claude/skills/` is available across local projects; project skills travel with the repository. Cloud and managed environments can have different loading rules. Check the [official skills guide](https://code.claude.com/docs/en/skills) for your environment.

Use this original example. Its manual-only setting makes the first test deliberate:

```markdown
---
name: release-note-outline
description: Turn supplied change notes into a release-note outline.
disable-model-invocation: true
---
Use only the change notes supplied by the user.
If no change notes are provided, ask the user to supply them.
Return three headings: Added, Fixed, Questions.
Put each confirmed change under Added or Fixed.
Put unclear claims under Questions. Do not invent versions or dates.
Do not edit files, run commands, or publish anything.
```

## Run it with a known input

In Claude Code, invoke `/release-note-outline` and supply: “Added CSV export. Fixed duplicate notifications. Faster reports, but no measurement yet.”

Check that the output has Added, Fixed and Questions sections. CSV export and the notification fix should appear as supplied changes. The unmeasured speed claim should remain a question. Start a new conversation in the same project, without the earlier change notes, then invoke `/release-note-outline` with no input. Confirm it asks for notes rather than reusing the previous example or inventing a release.

## Install an existing skill

Read its SKILL.md and any included scripts before installing it. Confirm which task it handles, which files it can change, and whether it needs credentials or paid services. Put a trusted standalone skill folder in the appropriate personal or project location, preserving its supporting files. If it is distributed as a plugin, follow that plugin’s installation instructions instead of copying only one file.

Test with a small input you already understand. A skill appearing in a menu confirms discovery; a correct, reviewable result confirms more of the procedure.

For example, suppose you received a reviewed standalone folder named `release-note-outline` in `~/Downloads/`. Copy that whole folder into `.claude/skills/` at your repository root. The resulting file must be `.claude/skills/release-note-outline/SKILL.md`, not `.claude/skills/release-note-outline/release-note-outline/SKILL.md`. Keep any `scripts/`, `references/` and other supporting files inside the copied folder.

Choose one location: use `~/.claude/skills/release-note-outline/` instead for personal use across projects. If you already created the earlier example, inspect that folder instead of overwriting it. Open Claude Code in the target repository, type `/` to find the command, and run `/release-note-outline` with the known input above.

### Manual or automatic invocation

With `disable-model-invocation: true`, you choose when to run this skill. To allow automatic selection, remove that field or set it to `false`; write a `description` that names the task and when to use it. Test a natural request such as “Turn these change notes into a release-note outline,” then inspect whether the intended skill was used.

## When the skill does not run

Check the directory, the `SKILL.md` filename, frontmatter and the session’s working directory. Confirm you are testing in the environment where the skill was installed. A same-named skill or organization policy can affect availability. This example uses `disable-model-invocation: true`, so test it with its command rather than waiting for automatic selection.

If it runs but produces weak results, tighten the input requirements and output checks. Avoid adding instructions that only repeat “be accurate.” Give one concrete rule for missing information.

## Choose skills by the work they perform

Use the release-note skill above when the input is supplied text; reject a candidate that invents missing changes. For repository review, check whether it reads the relevant files and cites paths before recommending edits. For connected research, check whether it identifies the account, source and query limits and explains any fees.

Browse the [Skills directory](/skills/), [set up OOMOL in Claude Code](/install/claude-code/), or start a task in [OOMOL Chat](https://console.oomol.com/overview).
## Skills, MCP and plugins

A skill describes a procedure. MCP makes tools available through a common interface. A plugin can package capabilities such as skills and tools. Installing instructions does not create access to an account, and connecting a server does not prove that a task returned the intended data.

For a practical next step, use [Jira](/integrations/jira/) to read one issue or [GitHub](/integrations/github/) to inspect one pull request. Keep the source identifier beside the result. See [MCP vs API](/blog/mcp-vs-api/) when choosing how your agent should reach those tools.
