Menü
Guided scenario for creating an Open Design plugin folder that can be installed into My plugins.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
A presentation system for agent-made PPTs — born for the talk, not just the template. It turns raw material into an AST (audience-state-transfer) outline with per-page visual-enhancement decisions (image / SVG diagram / video), hands a production brief to a downstream renderer (HTML-PPT skills or native PPTX), then runs a capped 3-round presentation checkup (演讲体检) on the rendered deck. It never renders slides itself. Use before generating PPT/HTML slides from raw material, and after rendering when the user says things like "给这份 deck 做演讲体检" or "PPT 渲染质检". If all you want is one beautiful template page with no outline and no checkup, a rendering skill alone is enough.
A first-30-days onboarding module for new hospitality hires — the behaviors, the practice, the checks, and the manager follow-up. Built as a decision-grade professional training deck for new hires, managers.
Open Design's feature business case for the plugin marketplace: the user pain, options, tradeoffs, and the measure of success. Built as a decision-grade product management deck for PM, eng, design, leadership.
Open Design + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
Open Design's incident retro: the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups. Built as a decision-grade product management deck for engineering, SRE, leadership.
Open Design's enterprise AI-adoption brief: local-first agents at work, the risk controls, the ROI, and the rollout plan. Built as a decision-grade AI literacy deck for leadership, IT, security.
| name | od-plugin-authoring |
| description | Guided scenario for creating an Open Design plugin folder that can be installed into My plugins. |
| od | {"scenario":"plugin-authoring","mode":"scenario"} |
Use this scenario when the user wants to create their own Open Design plugin.
Produce a folder named generated-plugin/ in the active project workspace.
At minimum, the folder must contain:
SKILL.md with frontmatter and clear agent instructions.open-design.json with valid plugin metadata, od.kind, mode, task kind, capabilities, and inputs when needed.Add examples/, assets/, or other supporting files only when they help the plugin be used or reviewed.
docs/plugins-spec.md and the schema at docs/schemas/open-design.plugin.v1.json.SKILL.md as the canonical behavior description. open-design.json should describe how Open Design installs, applies, and presents that behavior.generated-plugin/
SKILL.md
open-design.json
examples/
assets/
The examples/ and assets/ directories are optional. Do not create empty directories just to match the sketch.