skill-development

Create and validate OpenCode skills with required frontmatter and references.

2|Updated Jun 21, 2019
One-click install
npx skills add https://github.com/helmecke/dotfiles --skill skill-development-helmecke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-development
Source: https://github.com/helmecke/dotfiles/tree/main/dot_config/opencode/skill/skill-development
Command: npx skills add https://github.com/helmecke/dotfiles --skill skill-development-helmecke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides teams and AI agents to create consistent, high-quality OpenCode skills by standardizing frontmatter, structure, and resource references.

Core Features & Use Cases

Defines a repeatable workflow for sketching skill scope, validating frontmatter, and organizing bundled resources (references, scripts, assets) for scalable reuse.

Quick Start

Outline the skill’s purpose, define explicit triggers, and specify required frontmatter.

Frequently Asked Questions about skill-development

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

FAQPage Schema
How do I create and validate OpenCode skills with proper frontmatter?

To create OpenCode skills, outline the skill purpose, define explicit triggers, and enforce required frontmatter fields. This skill validation process analyzes content and guides progressive disclosure with references and examples to ensure reliable skill creation.

What is progressive disclosure when building OpenCode skills?

Progressive disclosure in OpenCode skills organizes bundled resources like references, scripts, and assets so agents access context incrementally. This approach structures skill content to scale efficiently without overwhelming the initial prompt.

What's the best way to standardize OpenCode skill structure for team reuse?

Standardizing OpenCode skill structure requires a repeatable workflow that validates frontmatter, organizes bundled resources, and enforces consistent metadata fields. This standardization ensures teams and AI agents can scale and reuse skills reliably.

Do I need to define explicit triggers before generating an OpenCode skill?

Yes, defining explicit triggers is a required quick start step for OpenCode skill creation. Specifying triggers alongside the skill purpose and required frontmatter ensures the generated skill activates correctly within the intended workflows.

Can I use this skill development workflow to iterate on existing skill descriptions?

Yes, this skill development workflow applies directly to iterating on descriptions and validating existing OpenCode skills. It analyzes skill content and enforces frontmatter requirements to refine and improve current skill definitions.

Why does my OpenCode skill fail frontmatter validation?

OpenCode skill frontmatter validation fails when required fields are missing or improperly defined. This skill development process enforces required frontmatter fields and analyzes skill content to ensure metadata meets validation standards.