opencode-skills

Name: opencode-skills
Availability: InStock
Author: justinlevinedotme

Create and validate OpenCode skills with standardized frontmatter and directory structure.

7|2|Updated Jan 18, 2026

Search Tags:#markdown #validation #modularity #organization #skill #frontmatter #opencode

Ready to run

npx skills add https://github.com/justinlevinedotme/jalco-opencode --skill opencode-skills

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organize and standardize the creation of OpenCode skills to ensure consistent naming, structure, and discovery.

Core Features & Use Cases

Create, validate, and publish skills using a consistent frontmatter schema (name and description) and optional directories for scripts, references, and assets.
Enforce discovery paths and permission patterns to control which agents can load which skills.
Use cases include designing new skills for agent capabilities, organizing shared skill libraries, and validating skill structure before deployment.

Quick Start

Create a new skill by adding a folder named after the skill under .opencode/skill or ~/.config/opencode/skill, place SKILL.md with proper frontmatter, and optionally include scripts, references, and assets.

Frequently Asked Questions about opencode-skills

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

FAQPage Schema

How do I create and structure modular agent skills with consistent frontmatter?▼

To create modular agent skills, place a SKILL.md file with required name and description frontmatter under .opencode/skill or ~/.config/opencode/skill. You can optionally include directories for scripts, references, and assets to maintain consistent organization.

What is the required frontmatter schema for validating OpenCode skills?▼

The required frontmatter schema for validating OpenCode skills mandates only the name and description fields. Optional directories support scripts, references, and assets, ensuring standardized discovery and permission patterns across project-scoped and global skill libraries.

How do discovery paths and permissions control which agents can load specific skills?▼

Discovery paths and permission patterns control agent skill loading by defining project-scoped or global library locations under .opencode/skill or ~/.config/opencode/skill. Enforcing these paths ensures only authorized agents can discover and deploy the modular capabilities.

Can I use optional scripting and asset directories when building agent capabilities?▼

Yes, you can use optional scripting, references, and assets directories when building agent capabilities. These directories sit alongside the required SKILL.md frontmatter file, allowing developers to organize shared skill libraries and validate structure before deployment.

What is the best way to organize shared skill libraries for agent deployment?▼

The best way to organize shared skill libraries is to standardize naming and structure using a consistent frontmatter schema. Group skills into project-scoped or global directories, validate the structure, and enforce permission patterns to control agent access.

Why does my agent fail to discover newly created skills in the library?▼

Agent skill discovery fails when the SKILL.md file lacks the required name and description frontmatter, or when the skill is placed outside the defined .opencode/skill or ~/.config/opencode/skill discovery paths. Validate the structure and permissions before deployment.