When a task needs the same explanations every time, there is an opportunity to turn those instructions into a procedure. A skill organizes that method so it can be found and reused.

In our setup, project knowledge is separate from assistant procedures. This lets us improve a routine without rewriting the context of every project.

Choose a small deliverable

Start with a task whose input and output are easy to recognize. For example: turn an account of your work into a note covering the situation, attempt, evidence and next step. The quality criterion is to preserve the information provided.

Create the skill file

In local Claude Code, a project skill can live at .claude/skills/registrar-aprendizado/SKILL.md. The file combines identification fields with Markdown instructions. Skills documentation ↗.

Terminal · inside a test project
mkdir -p .claude/skills/registrar-aprendizado

Create the SKILL.md file in that folder using this example:

SKILL.md · learning example
---
name: registrar-aprendizado
description: Organizes an experience into a reusable note.
---
Read the full account before writing.
Return: situation, attempt, evidence and next step.
Separate observed facts from hypotheses.
If information is missing, mark it as "not provided".
Do not invent results or publish the note.

Test for missing information

Open Claude Code in that project and use /registrar-aprendizado with a fictional account. Run two tests: one with all the information and another with no outcome provided. In the second case, the response should preserve the gap without inventing an ending.

If the output varies too much, refine the delivery criteria. If the skill has become long, check whether it is trying to solve more than one task.

Share without duplicating

In IA Configuração, we use a canonical source for procedures and adapters for each assistant. This arrangement needs its own integration: creating the folder in Claude Code does not automatically install the skill in another tool. The method can be reused; loading must be checked in each environment.

A useful next step is to separate examples and references from the main procedure, keeping the initial instructions short.

Draft for Davi Wallace’s review. The examples are for learning purposes. This article has not been published yet.