Skills

Skills give KnightCode specialized instructions and supporting files for a particular kind of work. KnightCode advertises each available skill by name and description, then loads its full instructions only when the task calls for them.

Use a skill when a workflow needs more context than a prompt template but does not need a new executable integration point. Skills can bundle scripts, references, and assets alongside their instructions.

KnightCode implements the Agent Skills specification. Most invalid fields produce warnings rather than stopping startup.

Create a skill

A skill is a directory containing SKILL.md:

pdf-tools/
├── SKILL.md
├── scripts/
│   └── extract.sh
├── references/
│   └── formats.md
└── assets/
    └── template.json

Start SKILL.md with frontmatter followed by direct instructions:

---
name: pdf-tools
description: Extract text and tables from PDF files. Use when reading, converting, or inspecting PDFs.
---

# PDF tools

Read `references/formats.md` before converting a document. Run scripts relative to this skill directory.

The description determines when the model considers loading the skill. State both what the skill does and when it applies. Avoid descriptions such as “Helps with PDFs,” which do not provide enough routing information.

Use relative paths from the skill directory when referring to bundled files. KnightCode tells the model where the skill lives so it can resolve those paths.

Understand how skills load

At startup, KnightCode scans configured skill locations and adds each skill’s name, description, and path to the system prompt. It does not add the full instructions.

When a task matches, the model reads SKILL.md and follows its instructions. This keeps detailed guidance out of context until it is needed. A model might fail to load a relevant skill, so use /skill:name when you need to force it.

Arguments after /skill:name are appended to the loaded instructions as a user request:

/skill:pdf-tools extract report.pdf

Set disable-model-invocation: true in frontmatter when a skill should be available only through its explicit command. The enableSkillCommands setting controls whether skill commands appear in interactive command discovery; manually entered /skill:name commands still work.

Add it to KnightCode

Place the skill in your user or project skills directory. Directories containing SKILL.md are discovered recursively.

KnightCode also supports the Agent Skills locations ~/.agents/skills/ and .agents/skills/. Project .agents/skills/ directories are discovered from the working directory through its ancestors, stopping at the repository root when one exists.

KnightCode accepts some standalone Markdown skills, but a directory containing SKILL.md is the portable form and should be preferred. See Settings and KnightCode Packages for additional locations.

Project skills can instruct the model to run scripts or modify files. Review unfamiliar skills and their supporting files before granting project trust.

Write portable frontmatter

The Agent Skills specification defines these fields:

Names use lowercase letters, numbers, and hyphens, with no leading, trailing, or consecutive hyphens. They can contain at most 64 characters; descriptions can contain at most 1024.

KnightCode neither requires nor warns when the declared name differs from the parent directory. Other Agent Skills implementations may enforce that requirement, so matching names remain the portable choice.

Malformed SKILL.md files and declared skills without descriptions are not loaded. Name collisions keep the first discovered skill and produce a warning.

Validate and share a skill

Run KnightCode from a location where the skill is discoverable, then inspect the startup diagnostics and /skill:name command. Run /reload after editing a skill during an active session.

Use a KnightCode package to distribute one or more skills through npm or git. Keep environment setup inside the skill and declare any required runtime dependencies in the package.

For examples, see the Anthropic skills collection.