skill-creator: packaging step skipped in Claude Code due to present_files gate

Summary

The skill-creator skill gates its "Package and Present" step behind the present_files tool:

### Package and Present (only if present_files tool is available) Check whether you have access to the present_files tool. If you don't, skip this step.

present_files appears to be a Claude.ai-specific tool. In Claude Code, this tool doesn't exist, so the packaging step is always skipped. This means skills created via the skill-creator in Claude Code never get packaged as .skill files — they end up as loose directories that don't install into the "My skills" UI panel.

Expected behavior

In Claude Code, the skill-creator should still run package_skill.py and open the resulting .skill file (e.g., via open /tmp/my-skill.skill), since packaging and installation work fine — only the present_files presentation mechanism is unavailable.

Suggested fix

Replace the present_files gate with environment-aware logic, something like:

• Claude.ai: Use present_files to offer the .skill download
• Claude Code: Run package_skill.py, then open the .skill file to trigger the installer
• Cowork: Run package_skill.py, then tell the user the file path

The Cowork-specific section already mentions "Packaging works — package_skill.py just needs Python and a filesystem" but doesn't override the present_files gate in the main instructions.

Reproduction

1. In Claude Code, invoke the skill-creator to build a new skill
2. Complete the full workflow (draft, test, iterate)
3. Observe that the "Package and Present" step is skipped because present_files is not available
4. The skill is never packaged as a .skill file

Environment

• Claude Code (CLI)
• macOS