skill-creator

A self-bootstrapping skill uses templates and bootstrap scripts to automatically recreate local state and credentials on first use. This approach ensures skills can be shared and reproduced across machines without manual repository surgery.

To create a portable OpenCode skill, you start with a SKILL.md file containing a frontmatter with name and description. You then add optional scripts, references, and assets, using a bootstrap script to create the local overlay.

Credentials are managed by keeping them in a local overlay directory that is not committed to git. The skill provides example credential templates, such as a .skill.config.example file, to guide users in setting up required environment values.

Yes, this skill template supports optional scripts, references, and assets within its structured folder layout. These components support deterministic bootstrapping and can be integrated into your existing OpenCode workflow.

The best way to deploy an OpenCode skill across multiple machines is using a standardized blueprint with deterministic bootstrap scripts. This ensures portability by recreating the local overlay state and credentials automatically on first use.

OpenCode skills often break when moved between machines because local state and credentials are missing. Using a self-bootstrapping template with a local overlay and example configuration files solves this by reproducing the environment deterministically.