Add versioning principle to skill-creator: SKILL.md should not contain versions

Critical guideline added:
- Skills should NOT have version sections in SKILL.md
- Version numbers belong in marketplace.json only (plugins[].version)
- SKILL.md should be timeless content focused on functionality
- Marketplace infrastructure manages versioning, not individual skills

Rationale:
- Discovered during ppt-creator development where version history was incorrectly added
- Verified against Anthropic's official skills repository (no version sections found)
- Aligns with marketplace architecture where versions are tracked centrally

Location: Added to "Versioning" subsection under "Privacy and Path References"

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
daymade
2025-10-26 08:40:01 +08:00
parent 061f1a74f3
commit 7d2a7e8a44

View File

@@ -85,6 +85,16 @@ Files not intended to be loaded into context, but rather used within the output
- **Allowed**: Standard placeholders (`~/workspace/project`, `username`, `your-company`)
- **Best practice**: Use generic examples and placeholders; all paths should reference bundled skill files or use standard environment-agnostic patterns
##### Versioning
**CRITICAL**: Skills should NOT contain version history or version numbers in SKILL.md:
- **Forbidden**: Version sections (`## Version`, `## Changelog`, `## Release History`) in SKILL.md
- **Forbidden**: Version numbers in SKILL.md body content
- **Correct location**: Skill versions are tracked in marketplace.json under `plugins[].version`
- **Rationale**: Marketplace infrastructure manages versioning; SKILL.md should be timeless content focused on functionality
- **Example**: Instead of documenting v1.0.0 → v1.1.0 changes in SKILL.md, update the version in marketplace.json only
### Progressive Disclosure Design Principle
Skills use a three-level loading system to manage context efficiently: