创建一个 Skill

Guide users through structured creation of multi-step automation playbooks for DeepTutor.

57.2k|7.0k|Updated Dec 28, 2025

Search Tags:#workflow automation #skill creation #content organization #playbook authoring #procedural instruction

Ready to run

npx skills add https://github.com/HKUDS/DeepTutor --skill skill-hkuds

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: 创建一个 Skill
Source: https://github.com/HKUDS/DeepTutor/tree/main/deeptutor/capabilities/creator/prompts/zh
Command: npx skills add https://github.com/HKUDS/DeepTutor --skill skill-hkuds

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Users need clear, structured guidance to author Skills—multi-step automation playbooks that coordinate execution logic, reference materials, and asset resources—without confusing them with Persona creation (personality/tone presets) or mixing operational workflows with style guidance. ## Core Features & Use Cases - Step-by-step Skill authoring: Walk through naming, description refinement, and playbook drafting with immediate feedback via proposal cards. - Distinction from Personas: Clarify when to use Skill (procedural automation) vs. Persona (system-level tone/behavior preset). - Reference material guidance: Help users organize large reference content (schemas, examples, lookup tables) into `references/*.md` instead of cluttering main playbook text. - Use Case: A user wants to automate code review workflows. This Skill guides them to write a clear trigger description ("Review pull requests for common patterns"), structure 5-8 verification steps, and separate detailed linting rules into a reference file. ## Quick Start Describe what automation workflow you want to create, and I will guide you through naming it, writing a clear trigger description, and drafting the step-by-step playbook.

Frequently Asked Questions about 创建一个 Skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a Skill instead of a Persona?▼

A Skill is an executable playbook—use imperative step-by-step instructions starting with action verbs ("Extract", "Validate", "Format"). A Persona is system-level tone guidance written in second person ("You are..."). If you want to automate a workflow, create a Skill; if you want to set communication style, create a Persona.

Where should I put large reference materials in a Skill?▼

Large schemas, lookup tables, and detailed examples belong in `references/*.md` files. Reference them in the main playbook with clear instructions like "See references/validation-rules.md for the complete schema."

How detailed should my Skill playbook be?▼

Write 500 lines or fewer for core playbook. Include concrete execution steps, decision branching, and handling of common errors. Save extensive background, schemas, and examples for `references/` directory.

What makes a good Skill description?▼

A strong description states what the Skill does, what problem it solves, and when to use it—concise enough for the system prompt but specific enough that users recognize if it applies. Example: "Parse and validate JSON API responses, extracting payload data and flagging schema violations."

Can I edit a Skill after proposing it?▼

Yes. Use the same name and call propose_creation again with your revised content. Each proposal generates a new draft card; you can iterate until satisfied before final confirmation.