skill-creator

Generate OpenCode skill units with SKILL.md YAML frontmatter and runtime instructions.

2|Updated Jul 29, 2025
One-click install
npx skills add https://github.com/kurojs/EnderDots --skill skill-creator-kurojs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/kurojs/EnderDots/tree/main/.config/opencode/skills/skill-creator
Command: npx skills add https://github.com/kurojs/EnderDots --skill skill-creator-kurojs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Produces new OpenCode skills with consistent runtime contracts, reliable YAML frontmatter, and repo-compliant structure so agents can activate them predictably.

Core Features & Use Cases

  • Reusable skill triggering: Creates LLM instruction contracts when a workflow pattern is repeated and needs guidance.
  • Repo-style compliance: Applies docs/skill-style-guide.md when available, otherwise uses the inline fallback rules.
  • Correct supporting resources: Places templates/schemas in assets/ and points to local docs in references/ for long explanations and references.

Quick Start

Create a new skill named "my-skill" that follows the required SKILL.md frontmatter and section order, targeting a reusable workflow pattern and adding only references to local files.

Frequently Asked Questions about skill-creator

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

FAQPage Schema
How do I generate LLM agent skills with valid YAML frontmatter?

To generate LLM agent skills with valid YAML frontmatter, use this tool to create a SKILL.md file containing a one-line YAML-safe description with trigger words and an LLM runtime instruction body. It ensures repo-specific style compliance and organizes supporting content in assets and references directories.

What is the correct structure for an OpenCode SKILL.md file?

The correct structure for an OpenCode SKILL.md file includes valid YAML frontmatter, an LLM runtime instruction body, and an output contract. Supporting templates and schemas are placed in the assets directory, while extensive explanations and references point to local documentation.

When should I create a reusable skill for agent workflows?

You should create a reusable skill for agent workflows when a non-trivial pattern is repeated and requires decision gates, guardrails, and concise operational instructions. This ensures agents can activate the workflow predictably across different contexts.

Does skill creation work with a repo style guide?

Yes, skill creation works with a repo style guide by automatically applying docs/skill-style-guide.md when available to enforce repo-specific rules. If no style guide exists, it falls back to inline rules to maintain structure and compliance.

What are the limitations of automating skill generation for documentation?

The limitation of automating skill generation is that it targets repeated, non-trivial workflow patterns requiring decision gates and guardrails. It is not intended for simple, one-off tasks that do not need structured LLM runtime contracts or operational instructions.