# Skill authoring: your context

Copy this file to CONTEXT.md next to SKILL.md and fill in every blank. Never put passwords, access keys or
card numbers here.

## Where skills live in your tool

(The folder your agent loads skills from, per project and for every project.)
Project skills: ___
Skills for every project: ___
Example: .claude/skills/<name>/ in the repository; ~/.claude/skills/<name>/ for all projects.

## How your tool loads a skill

(Automatically from the description, by a command, or both. If your tool has no skill system, where the instructions go instead.)
Example: loads automatically when the description matches, or by typing /<name>. A tool without skills: paste into the project instruction file.

## House conventions

(Language of skill files, heading style, whether every skill ships a context template, maximum body length you want.)
Language: ___
Context template in every skill: yes / no
Body length you want to stay under: ___
Example: English, a context template whenever any value differs per user, body readable in one pass with reference moved to separate files.

## Never in a skill file

(Your own list of things that must stay out: the kinds of private facts specific to your work. They go in CONTEXT.md as blanks instead.)
Example: client names, internal hostnames, account ids, prices, file paths on my machine, anything from customer records.

## Where you test

(How you open a fresh session for the trigger and cold-follow tests.)
Example: a new terminal session in a scratch copy of the project.