A Claude skill packages instructions and optional resources for a repeatable kind of task. Anthropic recommends giving each custom skill a focused purpose. Start with a problem you can describe in one sentence, such as checking that a release note names the affected feature and its migration steps.
Write the task contract first
Define the minimum information the skill needs, the expected output and its boundary. In the release-note example, the input might be a draft plus a change summary. The output could be a checklist and two rewrite suggestions. If the summary is missing, the desired behavior is to ask for it instead of filling in details.
Create a skill folder whose main Markdown document describes those rules. Anthropic documents the organization and packaging of skill resources for upload. Add example inputs that show when to use the skill and when to leave a request alone. Keep optional resources separate from the essential procedure, so a reader can find the instructions quickly.
Test invocation as well as wording
Test a normal request, a vague request and an unrelated task. The normal request should apply the output format. The vague one should request necessary information. The unrelated task should leave the skill unused. Watch for broad descriptions that make the skill seem relevant to almost everything.
Each time you edit a skill, rerun those three prompts before adding more features. Keep any script or optional data out of the skill until it solves a concrete repeated problem.
Continue with Oakgen Agent
Open in Oakgen Agent
The prompt is filled in for you. Review it before sending.


