opencode-config-validator

Name: opencode-config-validator
Availability: InStock
Author: jieni777

Validate OpenCode configurations against official standards for JSON syntax and schemas.

1|Updated Jan 30, 2026

Search Tags:#validation #mcp #json #config #lsp #validator #opencode

Ready to run

npx skills add https://github.com/jieni777/opencode-config-backup --skill opencode-config-validator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: opencode-config-validator
Source: https://github.com/jieni777/opencode-config-backup/tree/main/skills/opencode-config-validator
Command: npx skills add https://github.com/jieni777/opencode-config-backup --skill opencode-config-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenCode configurations often drift from official standards, causing client-side errors and inconsistent deployments. This skill automatically detects deviations in skill metadata, directory structure, and JSON schemas.

Core Features & Use Cases

Skills naming and structure validation: ensures SKILL.md name matches slug, proper directory presence, and frontmatter completeness.
Configuration file and schema validation: checks opencode.json syntax and schema conformance.
MCP/LSP/Tools spec checks: verifies parameters for MCP/LSP server settings against official docs and tooling configurations.
Use cases: after adding a new skill or modifying opencode.json, run the validator to catch structural or schema drift early.

Quick Start

Validate the current OpenCode configuration against official standards.

Frequently Asked Questions about opencode-config-validator

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

FAQPage Schema

How do I validate OpenCode configuration files against official schemas?▼

Validate OpenCode configuration by checking opencode.json syntax and schema conformance against official standards. The validator returns a deterministic pass or fail result with actionable remediation steps for any detected drift.

What causes MCP and LSP client errors when changing OpenCode configurations?▼

Client errors in MCP and LSP typically arise from configuration drift. Validating MCP and LSP server parameters against official specifications catches these deviations early, preventing inconsistent deployments and runtime failures.

How do I check if my SKILL.md name matches the directory structure?▼

Check skill naming and structure by validating that the SKILL.md name matches the slug, verifying proper directory presence, and ensuring frontmatter completeness. This prevents structural errors when adding new skills to your workflow.

Can I use this validator to catch JSON schema drift after modifying opencode.json?▼

Yes, you can use the validator to catch JSON schema drift after modifying opencode.json. It enforces checks on JSON syntax and config schemas, verifying conformance across MCP, LSP, and general opencode usage in development workflows.

When should I run an OpenCode config validation in my development workflow?▼

Run OpenCode config validation when skills are added, configurations are changed, or validation is explicitly triggered. Running it after modifying opencode.json or adding a new skill catches structural or schema drift early in development.

Does the validator check both skill metadata and tooling configurations?▼

Yes, the validator checks both skill metadata and tooling configurations. It enforces checks on skill naming and frontmatter completeness while verifying parameters for MCP, LSP server settings, and general opencode.json schema conformance.