Sc2
Skill SPRIC76/sc2
Skill Creator 2 (sc2) — dual-packaging and quality standards for Cursor/Claude agent skills.
npx -y skills add SPRIC76/sc2Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Enhanced skill creator with mandatory dual-packaging (.skill + .zip), validation, and comprehensive reference material. Piggybacks the base Anthropic skill-creator with stricter output standards. Use when creating, improving, or packaging skills. ALWAYS produces both .skill (interface-loadable) and versioned .zip (manual deployment). Enforces documentation completeness and user-friendly reference material in every skill.
SKILL.md
3.5 KB, as published. Nobody here has run it
Skill Creator — Packaging & Quality Standards
This skill supplements the base skill-creator (in /mnt/skills/examples/).
Read base SKILL.md first for full workflow, then apply these standards on top.
Mandatory Packaging Standard
Every skill output MUST include both formats:
| Format | Purpose | Naming |
|---|---|---|
.skill | Direct interface loading (drag-and-drop) | {name}.skill |
.zip | Manual download/deployment to /mnt/skills/user/ | {name}-v{X.Y}.zip |
Both are zip archives with {skillname}/SKILL.md as root entry.
The .skill file has no version in filename (always current).
The .zip includes version for archive/deployment clarity.
Packaging Procedure
ALWAYS use scripts/package_dual.py instead of the base package_skill.py:
scripts/package_dual.py <path/to/skill-folder> --version <X.Y> [--output <dir>]
This produces both files in one command. If the script is unavailable, package manually:
cd <parent-of-skill-folder>
zip -r <output>/skillname.skill skillname/
cp <output>/skillname.skill <output>/skillname-vX.Y.zip
Present BOTH files to the user. Never present only one format.
Pre-Package Checklist
Before packaging, verify:
| Check | Requirement |
|---|---|
| SKILL.md frontmatter | name (kebab-case) + description (with triggers) |
| SKILL.md body | < 500 lines, progressive disclosure to references |
| References | All referenced files exist, concise, user-friendly |
| Scripts | All referenced scripts exist, documented, runnable |
| No orphans | Every file referenced from SKILL.md or another file |
| No junk | No __pycache__, .pyc, .DS_Store, node_modules |
Documentation Completeness
Every skill MUST have:
- SKILL.md — Core instructions, triggers, workflow, anti-patterns
- references/ — Any supporting docs referenced from SKILL.md
- Each reference file must justify its existence (not duplicating SKILL.md)
- Concise and scannable (tables over prose, imperative form)
- Include version/date header
- scripts/ (if applicable) — Executable code with docstrings
User-friendly standard: A new user reading only SKILL.md should understand what the skill does, when it triggers, and how to use it. References provide depth, not prerequisites.
Version Tracking
Every skill file set should note:
- Skill version in archive filename
- Creation date in SKILL.md or references
- Former names/versions in footnote if renamed
Integration with Base Skill-Creator
This overlay modifies these base workflow steps:
"Package and Present" (line ~340): Replace single .skill output with
dual packaging. Always present both files via present_files.
"Final Report" (line ~555): After copying best skill back, run dual
packaging. Present both .skill and .zip to user.
"Immediate Feedback Loop": When showing early outputs, still use dual packaging if presenting a testable skill.
All other base workflow steps (interview, research, init, writing guide, eval, improve, benchmark) remain unchanged.