Plugin Creator
Developmentplugin-creatorPlugin Creator is an Agent Skill for development published in the Hmbown/CodeWhale repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Scaffold codewhale local plugin directories and activation notes. Use when the user asks to create, package, or sketch a plugin for codewhale.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/Hmbown/CodeWhale/blob/HEAD/crates/tui/assets/skills/plugin-creator/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/plugin-creator, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Plugin Creator
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.
Workflow
- Pick the location:
- Global user plugin:
~/.deepseek/plugins/<plugin-name>/ - Workspace plugin:
<workspace>/plugins/<plugin-name>/
- Global user plugin:
- Normalize names to lower-case hyphen-case.
- Create
PLUGIN.mdwith 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.
- Add companion folders only when useful:
skills/for model instructionsscripts/for helpers invoked by a skill or hookmcp/for an MCP server package or config notesassets/for templates, examples, or fixtures
- Include an activation section in
PLUGIN.mdthat says exactly how the user should turn it on today. - Validate by listing the created files and checking that
PLUGIN.mdhasnameanddescriptionfrontmatter.
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.