Thomashighbaugh/config-sync
skills/config-sync/SKILL.md
Synchronize opencode.jsonc with the latest OpenCode config schema from Context7. Checks schema, detects drift, and updates config to remain compliant.
$ install --global
skillsauthnpx skillsauth add Thomashighbaugh/opencode config-syncInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 13, 2026, 2:27 AM16.1s2 files scanned
SKILL.md
- name:
- config-sync
- description:
- Synchronize opencode.jsonc with the latest OpenCode config schema from Context7. Checks schema, detects drift, and updates config to remain compliant.
- level:
- 3
Config Sync
Enforce that opencode.jsonc stays compliant with the latest OpenCode configuration schema.
Why This Exists
OpenCode's config schema evolves. Keys get deprecated (mode → agent, autoshare → share), new keys are added (tool_output, compaction, experimental.policies), and invalid keys that don't exist in the schema can silently cause config load failures.
This skill fetches the latest schema from https://opencode.ai/config.json, compares it against the current config, and reports any compliance issues.
When to Use
- After OpenCode updates
- When config load errors occur
- Before major config changes
- As part of
/project audit
Workflow
1. Fetch Current Schema
Fetches https://opencode.ai/config.json via web fetch and extracts valid top-level keys, deprecated keys, and new additions.
2. Compare Against Local Config
Reads opencode.jsonc, parses all top-level keys, and checks:
- Each key exists in schema → valid
- Each key is not
@deprecated→ warn if still used - No unknown/invalid keys present → flag as error
3. Report & Fix
- Reports all issues grouped by severity (error, warning, info)
- Can auto-fix: remove deprecated keys, add recommended missing keys
- Saves schema to
.opencode/context/research/opencode-config-schema.mdfor offline reference
Script
scripts/check-schema-compliance.mjs — Standalone compliance checker
node scripts/check-schema-compliance.mjs # Check only
node scripts/check-schema-compliance.mjs --fix # Auto-fix issues
node scripts/check-schema-compliance.mjs --save # Save schema to context
Cached Schema
The last-fetched schema is stored at:
.opencode/context/research/opencode-config-schema.md
This serves as the durable reference and diff baseline.
Related Skills
Thomashighbaugh/provision
tools
VerifiedTrustedCommunity
Analyze a codebase and auto-generate project-specific agents, skills, tools, and rules into .opencode/. Project wrappers inject deep project context into subagents for dramatically more effective AI assistance.
1SKILL.mdUpdated Jun 13, 2026
Thomashighbaugh/agent-format-enforcer
development
VerifiedTrustedCommunity
Enforce the <Agent_Prompt> XML wrapper convention across all agent definition files. Scan, validate, and auto-fix non-compliant agents.
1SKILL.mdUpdated Jun 13, 2026
Thomashighbaugh/vectorize-context
development
VerifiedTrustedCommunity
Auto-maintained vector DB for semantic search over .opencode/context/ — zero manual triggers needed
1SKILL.mdUpdated Jun 9, 2026
Thomashighbaugh/orchestrate-router
tools
VerifiedTrustedCommunity
Natural language intent router — takes amorphous user requests and routes to the correct /orchestrate, /ideation, or /harvest-context subcommand
1SKILL.mdUpdated Jun 9, 2026