create-opencode-skill
Use this skill to create or update OpenCode Skills or skill files.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install bingud-filemat-create-opencode-skill
Repository
Skill path: .opencode/skills/create-opencode-skill
Use this skill to create or update OpenCode Skills or skill files.
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: bingud.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install create-opencode-skill into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/bingud/filemat before adding create-opencode-skill to shared team environments
- Use create-opencode-skill for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
---
name: create-opencode-skill
description: Use this skill to create or update OpenCode Skills or skill files.
---
## Context
OpenCode uses a "Skills" system to store reusable project knowledge. Skills are stored in `.opencode/skills/` with a specific folder-based structure.
## Rules for Creating Skills
When I ask you to "save this as a skill" or "create a skill for X":
1. **Directory Structure**: Create a new directory inside `.opencode/skills/` named after the skill (use `kebab-case`).
2. **File Naming**: Inside that directory, create a file exactly named `SKILL.md` (must be uppercase).
3. **Frontmatter**: Every `SKILL.md` MUST start with this YAML block:
---
name: [kebab-case-name]
description: [One sentence describing when to use this skill]
---
4. **Content**:
- Use clear headings (##).
- Use imperative language ("Always do X", "Never use Y").
- Provide a short code example of the pattern if applicable.
## Workflow
- Check if a skill with a similar name already exists before creating a new one.
- If updating an existing skill, always ask for confirmation.