Support skills with associated resources and scripts

[sirkitree]

Problem

Skills in the prompt library can reference external resources like helper scripts, configuration files, or other assets. For example, the Cloudflare Tunnel skill references a helper script at ~/.claude/skills/cloudflare-tunnel/scripts/tunnel.sh, but the library only stores the markdown skill definition — not the script itself.

This means:

• Users who discover a skill in the library have no way to obtain its required scripts/resources
• There's no standard way to submit or review skill resources alongside the skill definition
• Skills that depend on external scripts are incomplete without those assets

Proposed Solution

Add support for skills to include associated resources (scripts, config files, templates, etc.) alongside their markdown definitions. This could involve:

1. Directory structure for skill resources: Allow skills to have a companion directory for resources, e.g.:

   development/skills/cloudflare-tunnel.md
   development/skills/cloudflare-tunnel/
     scripts/tunnel.sh
     resources/config-template.yml
   

2. Installation/setup instructions: Define a convention for how users install skill resources to their local ~/.claude/skills/ directory (or equivalent).

3. Updated submission process: Extend the skill submission issue template to accept resource files or link to them.

4. Display on the site: Show associated resources on the skill's page so users can download or copy them.

Examples of Skills That May Need Resources

• Cloudflare Tunnel: scripts/tunnel.sh helper script
• Skills that generate boilerplate from templates
• Skills that wrap CLI tools with custom scripts
• Skills that include reference data or lookup tables

Acceptance Criteria

• Define a directory convention for skill resources
• Update the 11ty build to handle skill resource directories
• Update the skill submission template to support resource files
• Add a mechanism for users to install/download skill resources
• Document the convention in CLAUDE.md and/or contributor docs