// Create or improve DeepSeek TUI 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.
Design, build, configure, or debug Model Context Protocol servers for DeepSeek TUI, including stdio and HTTP/SSE transports.
Read, extract, split, merge, rotate, watermark, fill, OCR, or create PDF files with verification of page counts and text extraction.
Scaffold DeepSeek local plugin directories and activation notes. Use when the user asks to create, package, or sketch a plugin for DeepSeek TUI.
Create, edit, inspect, or convert PowerPoint decks and PPTX slide presentations with practical layout and verification steps.
| name | skill-creator |
| description | Create or improve DeepSeek TUI 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. |
| metadata | {"short-description":"Create DeepSeek skills"} |
Use this skill to create small, useful DeepSeek TUI skills that match the runtime this repository actually ships.
A skill is a local folder with a SKILL.md file. DeepSeek reads the skill name
and description during discovery, then loads the body only when the user or task
matches the skill.
Discovery paths, in precedence order:
<workspace>/.agents/skills<workspace>/skills<workspace>/.opencode/skills<workspace>/.claude/skills<workspace>/.cursor/skills~/.agents/skills~/.claude/skills~/.deepseek/skillsUse skills for model instructions, workflows, and lightweight conventions. Use MCP for live external APIs or durable tools. Use hooks for automatic local events. Use plugin folders only as packaging/scaffolding until a real plugin loader exists.
my-skill/
`-- SKILL.md
---
name: my-skill
description: Use when DeepSeek should follow this specific workflow.
---
# My Skill
Instructions for the agent.
Frontmatter parsing is intentionally simple. Keep name and description as
plain single-line values. Use lower-case hyphen-case names.
description action-oriented and trigger-specific. It is the main
signal DeepSeek sees before loading the body.references/ and mention exactly when to open them.scripts/ only for deterministic helpers that are worth maintaining.assets/ only for templates, fixtures, examples, or files reused by the
workflow.<skill-name>/SKILL.md.name and description./skills or by running the relevant
skill discovery tests if editing this repository.SKILL.md starts with ---.name matches the directory name unless there is a deliberate reason.description says when to use the skill, not just what it is.