Menu
Helps the user create, install, and test new OpenCode skills with a self-correction feedback loop.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when exercising or debugging the complete ocint daemon LCH lifecycle, from a labelled GitHub issue through task execution, pull-request publication, and issue reply.
Use when adding, moving, or reviewing ocint modules, shared models, configuration, repositories, CLI commands, rendering, or package imports.
Use ocint ctx when specifically asked to search OpenCode history. This can be useful for anlyazing OpenCode sessions to find context or citations however it is not fuzzy search and requires exact terms for searching.
Use tmux for manual terminal testing of CLI and TUI behavior. Use when validating real TTY rendering, ANSI styling, wrapping at different widths, interactive output, progress displays, or long-running terminal commands.
A skill for processing PDFs, including creation, merging, and info extraction.
| name | skill-creator |
| description | Helps the user create, install, and test new OpenCode skills with a self-correction feedback loop. |
I help you manage the lifecycle of OpenCode skills in this repository, ensuring they are not just discoverable but functionally correct.
Before creating a skill, I:
tool help <command>) to learn correct syntax and schemas.just create <name> to set up the directory and SKILL.md template.I draft the SKILL.md to be extremely specific. For tools with complex inputs (like JSON schemas or specific flags), I include valid examples in the skill content to ensure the loading agent has a baseline.
After using just install <name>, I verify the skill by executing a functional test:
opencode run "..." with a prompt that exercises the skill's unique capabilities.SKILL.md instructions to address the failure (e.g., "The tool expects 'items' not 'rows'").just install <name>: Symlink to global config.just list: Audit available and active skills.just uninstall <name>: Deactivate a skill.Use this skill when you need to build a new capability that requires specific tool knowledge and verified execution. I am particularly useful for skills that wrap complex CLI tools.