skill-creator

Create modular OpenCode skills with SKILL.md frontmatter and packaging.

41|4|Updated May 6, 2026
One-click install
npx skills add https://github.com/markerikson/opencode-config-example --skill skill-creator-markerikson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/markerikson/opencode-config-example/tree/main/config/skill/skill-creator
Command: npx skills add https://github.com/markerikson/opencode-config-example --skill skill-creator-markerikson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users design and package high-quality OpenCode skills by providing a clear, reusable process for turning example-driven needs into modular, triggerable skill content with correct structure and metadata.

Core Features & Use Cases

  • Skill design guidance: Define what the skill covers, why it matters, and how it should be triggered using precise YAML frontmatter.
  • Reusable contents planning: Identify when to include scripts for deterministic automation, references for contextual learning, and assets for templated outputs.
  • Packaging and iteration workflow: Validate structure and metadata, package the skill into a distributable zip, and iterate after real-world use.

Quick Start

Use the skill-creator skill to create a new domain skill by running the init_skill workflow, then editing SKILL.md with a clear name and description and packaging the resulting folder for distribution.

Frequently Asked Questions about skill-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a modular OpenCode skill with correct YAML frontmatter?

To create an OpenCode skill, translate your user scenario into a SKILL.md file with correct YAML frontmatter, organize supporting resources like scripts or references, and validate the directory structure before packaging.

What is the best way to structure a skill directory for workflow automation?

A skill directory for workflow automation requires a structured layout containing an explicit SKILL.md entry point with name and description metadata, alongside optional folders for scripts, references, and assets.

How do I package an OpenCode skill into a distributable zip file?

Package an OpenCode skill by validating the SKILL.md metadata and directory structure, then compressing the formatted skill folder into a distributable zip file for deployment and real-world iteration.

When should I include scripts versus references in my skill directory?

Include scripts in your skill directory for deterministic automation, references for contextual learning, and assets for templated outputs to ensure the skill handles specialized workflows effectively.

Do I need prior coding experience to author domain knowledge modules for OpenCode?

Authoring domain knowledge modules requires understanding structured skill directory layout and YAML frontmatter to define metadata, though optional scripts can be added if deterministic automation is needed.

Why is my OpenCode skill not triggering correctly for specialized workflows?

OpenCode skills fail to trigger when the SKILL.md frontmatter lacks a precise description or explicit name metadata, preventing the system from matching the skill to specialized workflow scenarios.