Scaffold codewhale local plugin directories and activation notes. Use when the user asks to create, package, or sketch a plugin for codewhale.
Design, build, configure, or debug Model Context Protocol servers for codewhale, including stdio and HTTP/SSE transports.
Create or improve codewhale skills. Use when the user wants a new skill, wants to update an existing skill, or needs guidance on when a skill should be a skill versus MCP, hooks, tools, or a plugin scaffold.
Create, edit, inspect, or convert Word documents and DOCX deliverables such as memos, reports, letters, templates, and forms.
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
Read, extract, split, merge, rotate, watermark, fill, OCR, or create PDF files with verification of page counts and text extraction.
Create, edit, inspect, or convert PowerPoint decks and PPTX slide presentations with practical layout and verification steps.
| 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.