fix(skills): remove references to nonexistent init/package scripts

Replace init_skill.py and package_skill.py references with manual
mkdir and validation checklist — the scripts were never created.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-02-11 21:45:42 +01:00
co-authored by Claude Opus 4.6
parent c35248f103
commit f160f07e6d
+11 -17
View File
@@ -149,14 +149,14 @@ Establish a list of reusable resources: scripts, references, and assets.
### Step 3: Initialize the Skill
Run the init script to generate a template skill directory:
Create the skill directory manually:
```
scripts/init_skill.py <skill-name> --path <output-directory>
mkdir -p <output-directory>/<skill-name>
```
Creates: skill directory, SKILL.md template with TODO placeholders, example
resource directories with sample files.
Then create `SKILL.md` with frontmatter and body. Add `scripts/`, `references/`,
and `assets/` subdirectories only as needed.
Skip if iterating on an existing skill.
@@ -184,20 +184,14 @@ For design patterns, consult:
**Body:** Instructions for using the skill and its bundled resources.
### Step 5: Package the Skill
### Step 5: Validate the Skill
```
scripts/package_skill.py <path/to/skill-folder>
```
Optional output directory:
```
scripts/package_skill.py <path/to/skill-folder> ./dist
```
The script validates (frontmatter, naming, description, file organization) then
packages into a `.skill` file (zip with .skill extension). Fix any validation
errors and re-run if needed.
Check the skill manually:
- Frontmatter has `name` and `description`
- SKILL.md body is under 500 lines
- No extraneous files (README.md, CHANGELOG.md, etc.)
- Scripts are executable and tested
- References are referenced from SKILL.md
### Step 6: Iterate