From cd9f8932093148f6fd908bd7554a0b7361b4b99f Mon Sep 17 00:00:00 2001 From: Gaurav Saxena Date: Thu, 28 May 2026 00:27:37 +0530 Subject: [PATCH] Clarify skill reference path guidance --- skills/skill-creator/SKILL.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/skills/skill-creator/SKILL.md b/skills/skill-creator/SKILL.md index 65b3a402..8bca6313 100644 --- a/skills/skill-creator/SKILL.md +++ b/skills/skill-creator/SKILL.md @@ -94,7 +94,8 @@ These word counts are approximate and you can feel free to go longer if needed. **Key patterns:** - Keep SKILL.md under 500 lines; if you're approaching this limit, add an additional layer of hierarchy along with clear pointers about where the model using the skill should go next to follow up. -- Reference files clearly from SKILL.md with guidance on when to read them +- Reference files clearly from SKILL.md with guidance on when to read them. +- When referring to bundled files such as `references/foo.md`, tell the model to resolve them from the skill's own directory. If the runtime file tool requires absolute paths, instruct the model to first determine the installed skill directory and then read the bundled file by absolute path instead of assuming `references/foo.md` resolves from the current working directory. - For large reference files (>300 lines), include a table of contents **Domain organization**: When a skill supports multiple domains/frameworks, organize by variant: