一键在 Manus 中运行任何 Skill

plugin-creator

星标39,228

分支3,396

更新时间2026年5月23日 16:58

Scaffold codewhale local plugin directories and activation notes. Use when the user asks to create, package, or sketch a plugin for codewhale.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

Hmbown

Hmbown/CodeWhale

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

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>/
Normalize names to lower-case hyphen-case.
Create 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.

Add companion folders only when useful:
- skills/ for model instructions
- scripts/ for helpers invoked by a skill or hook
- mcp/ for an MCP server package or config notes
- assets/ for templates, examples, or fixtures
Include an activation section in PLUGIN.md that says exactly how the user should turn it on today.
Validate by listing the created files and checking that 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.

同仓库更多 Skills

同仓库

rust-check

Hmbown/CodeWhale

Run cargo check on the current Rust project to find compile errors

2026-06-2739.2k

codew-release-qa-sweep

Hmbown/CodeWhale

Use before claiming CodeWhale release work is done: run the full gate sweep and list the manual QA targets.

2026-06-2339.2k

gh-assign-issues

Hmbown/CodeWhale

Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.

2026-06-1739.2k

gh-close-issues

Hmbown/CodeWhale

Close resolved CodeWhale issues only after verifying the landed commit/behavior, with a positive crediting comment; never from title alone.

2026-06-1739.2k

gh-compile-issues

Hmbown/CodeWhale

Triage N GitHub issues into a coverage matrix: fetch each, check current code, classify already-done/quick-fix/design/defer with cited evidence.

2026-06-1739.2k

gh-credit-harvest

Hmbown/CodeWhale

Harvest one community PR into a release branch with authorship and credit preserved, verified green, and a warm thank-you.

2026-06-1739.2k

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.

Plugin Creator

Use this skill when a user wants a DeepSeek plugin scaffold or a plan for a plugin-style extension.

Workflow

Pick the location:
- Global user plugin: ~/.deepseek/plugins/<plugin-name>/
- Workspace plugin: <workspace>/plugins/<plugin-name>/
Normalize names to lower-case hyphen-case.
Create 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.

Add companion folders only when useful:
- skills/ for model instructions
- scripts/ for helpers invoked by a skill or hook
- mcp/ for an MCP server package or config notes
- assets/ for templates, examples, or fixtures
Include an activation section in PLUGIN.md that says exactly how the user should turn it on today.
Validate by listing the created files and checking that 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.