skills.rest
good-idea
good-ideaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

opencode-config-validation

Validate OpenCode configuration files for frontmatter, naming, and cross-references.

3|Updated May 12, 2019
Search Tags:#validation#agent#config#skill#validate#yaml-frontmatter#OpenCode
One-click install
npx skills add https://github.com/good-idea/dotfiles --skill opencode-config-validation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: opencode-config-validation
Source: https://github.com/good-idea/dotfiles/tree/main/opencode/skill/opencode-config-validation
Command: npx skills add https://github.com/good-idea/dotfiles --skill opencode-config-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates OpenCode configuration files for correctness and best practices, helping teams catch misconfigurations before they impact CI/CD and runtime behavior.

Core Features & Use Cases

  • Frontmatter & Structure Validation: Ensures required fields exist (name, description) and that the skill's directory structure and file naming follow the OpenCode conventions.
  • Naming Consistency & Best Practices: Enforces lowercase, hyphenated identifiers, and consistent naming across agents, skills, and commands.
  • Cross-Reference & Dependency Validation: Verifies references between components and checks for missing or invalid dependencies.

Quick Start

Run the validator against opencode/skill/opencode-config-validation/SKILL.md to verify compliance.

Frequently Asked Questions about opencode-config-validation

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

FAQPage Schema
How do I validate OpenCode configuration files for correct frontmatter and structure?▼

Validate OpenCode configuration files by checking that required frontmatter fields like name and description exist, and verifying that directory structures and file naming follow OpenCode conventions.

What are the naming conventions for OpenCode agents, skills, and commands?▼

OpenCode naming conventions require lowercase, hyphenated identifiers to ensure consistency across agents, skills, and commands during structural validation.

How do I check for missing dependencies and cross-references in OpenCode configurations?▼

Check for missing dependencies in OpenCode configurations by running a cross-reference validation that verifies references between components and identifies invalid links.

Can I validate OpenCode skill configurations before deploying to CI/CD?▼

You can validate OpenCode skill configurations before CI/CD by running the validator against your SKILL.md file to catch misconfigurations and ensure structural integrity.

Why does my OpenCode configuration fail naming consistency checks?▼

OpenCode configuration naming consistency checks fail when identifiers are not lowercase and hyphenated, or when directory naming does not follow OpenCode conventions.

What frontmatter fields are required for OpenCode configuration validation?▼

Required frontmatter fields for OpenCode configuration validation include name and description, which are enforced to ensure frontmatter validity and compliance.

Related Skills

Explore More Software Engineering Skills→
jasonz-ncc42jasonz-ncc42
7

opencode-docs

Provide OpenCode documentation references for installation, configuration, and usage.

Community
Intermediate
pradyumnasagarpradyumnasagar
6

cross-reference-mapper

Generate and validate cross-references between ORS skills.

Community
Intermediate
ddttomddttom

md-workflow

Create, edit, and lint Markdown files with YAML frontmatter awareness.

Community
Intermediate
open-haxopen-hax
6

opencode-tool-authoring

Define and validate OpenCode tool schemas with YAML frontmatter.

Official
Intermediate