Menu
Scaffold codewhale local plugin directories and activation notes. Use when the user asks to create, package, or sketch a plugin for codewhale.
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
Run cargo check on the current Rust project to find compile errors
Use before claiming CodeWhale release work is done: run the full gate sweep and list the manual QA targets.
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
Close resolved CodeWhale issues only after verifying the landed commit/behavior, with a positive crediting comment; never from title alone.
Triage N GitHub issues into a coverage matrix: fetch each, check current code, classify already-done/quick-fix/design/defer with cited evidence.
Harvest one community PR into a release branch with authorship and credit preserved, verified green, and a warm thank-you.
| name | plugin-creator |
| description | Scaffold codewhale local plugin directories and activation notes. Use when the user asks to create, package, or sketch a plugin for codewhale. |
Use this skill when a user wants a DeepSeek plugin scaffold or a plan for a plugin-style extension.
DeepSeek plugins are currently a documented packaging convention, not an auto-loaded runtime. Be explicit about that. A plugin becomes active only when it is referenced from a skill, hook, MCP server, or future plugin loader.
~/.deepseek/plugins/<plugin-name>/<workspace>/plugins/<plugin-name>/PLUGIN.md with frontmatter:---
name: my-plugin
description: What this plugin packages or enables.
status: draft
---
# My Plugin
What it does, how to enable it, and any scripts or MCP servers it expects.
skills/ for model instructionsscripts/ for helpers invoked by a skill or hookmcp/ for an MCP server package or config notesassets/ for templates, examples, or fixturesPLUGIN.md that says exactly how the user
should turn it on today.PLUGIN.md has
name and description frontmatter.Do not claim that dropping a folder into plugins/ changes runtime behavior by
itself. If the user asks for a live plugin system, propose a loader design
separately and keep the scaffold honest.