SuperAPI AI Directory

skill-prompt-convert

Writing & research

View repository

Updated 10-16 01:31

About this skill

Skill and Prompt mutual conversion

When to use

  • The user needs to convert a Skill into a Prompt that can be copied directly into a chatbox
  • The user needs to convert a Prompt into a Skill in SKILL.md format
  • The user mentions Skill and Prompt mutual conversion or format conversion

Step 1: Get the input and confirm the direction

Get the content to be converted from the user message or pasted/attached content, and determine the direction:

  • A. Skill → Prompt: The input is SKILL.md content, and the output is a Prompt usable in a chatbox
  • B. Prompt → Skill: The input is Prompt content (including ``` code block), output in SKILL.md format

Step 2: Perform the conversion

When Skill → Prompt: Incorporate name、description into # Role and # Task; convert "When to use" into applicable scenarios; convert Step 1/2... into # Workflow or # Constraints; add # Output Format and # Input placeholders; wrap the output in ```.

When Prompt → Skill: Extract from # Role、# Task the name(English lowercase hyphenated) and description; extract "When to use" from # Task or # Constraints ; break down # Workflow、# Constraints into Step 1, Step 2...; preserve # Output Format into "Notes"; output a complete SKILL.md,must conform to the standard Skill format。

Step 3: Output the result

  • Part 1 [Conversion notes]: Briefly explain the mapping relationship (e.g.: Step 1 maps to the first step of Workflow)
  • Part 2 [Conversion result]: The complete converted content (ready to paste and use)

Notes

  • Zero information loss: Do not delete or reduce core logic, steps, or constraints
  • Format adaptation: Skill emphasizes "when it is triggered" and "how the Agent executes"; Prompt emphasizes "what the user inputs" and "what format is output"
  • Naming convention:name must be English, lowercase, hyphenated (e.g. wechat-article-writer); the same applies to reference file names (e.g. outline-review-science.md)
  • description quality: Must include "when to use it", "what it is used for", and keywords
  • Skill body structure: Title → When to use → Step 1/2... → Notes/Examples; multi-input tasks need to add "input method when triggered"
  • Standard Skill format: YAML front matter must start and close with --- , using name: and description:(strictly prohibited ## name:), example:
    ---
    name: skill-name
    description: 触发场景与功能描述
    ---
    
    # 标题
    ...