AgentSkillsCN

prompt-refiner

运用OpenAI的最佳实践，优化初稿提示词。适用于准备复杂任务时使用，这些任务需要明确的角色与人物设定、清晰的步骤流程、规范的输出格式，或具体而生动的示例。

SKILL.md
--- frontmatter
name: prompt-refiner
description: Refine draft prompts using OpenAI best practices. Use when preparing complex tasks that need a clear role/persona, procedural steps, explicit output formatting, or concrete examples.

Prompt Refiner

When to Use

Invoke this skill when you have a task that:

  • •Requires a specific persona or expertise
  • •Involves procedural steps
  • •Needs structured output
  • •Benefits from explicit examples

Refinement Process

1. Analyze the Draft Prompt

Review for:

  • • Clear role/persona definition
  • • Step-by-step breakdown (if procedural)
  • • Output format specification
  • • Concrete examples

2. Apply GPT-Specific Patterns

Role framing: Start with "You are a [specific role] working on [specific context]..."

Numbered procedures: Break complex tasks into numbered steps that build on each other.

Output specification: Be explicit: "Return as JSON", "Format as markdown with headers", etc.

Chain of thought: For reasoning tasks, add: "Think through this step by step."

3. Structure the Prompt

Effective order:

  1. •Role definition (who/what)
  2. •Context (background info)
  3. •Task (what to do)
  4. •Steps (how to do it, if procedural)
  5. •Output format (what to return)
  6. •Examples (optional clarification)

4. Output the Refined Prompt

Present with:

  • •Clear role statement
  • •Numbered steps where applicable
  • •Explicit output requirements

Example Transformation

Before: "Review this code for security issues"

After:

code
You are a senior security engineer conducting a security audit of a Node.js payment processing service.

Context: This service handles credit card transactions and communicates with Stripe's API. It runs in AWS ECS.

Task: Review the code in src/payments/ for security vulnerabilities.

Steps:

1. Check for proper input validation on all endpoints
2. Verify secrets are not hardcoded or logged
3. Review authentication and authorization logic
4. Check for SQL injection and XSS vulnerabilities
5. Verify proper error handling that doesn't leak sensitive info

Output format:
Return a security report in markdown with:

* **Critical**: Issues that must be fixed before deployment
* **High**: Significant risks that should be addressed soon
* **Medium**: Improvements to consider
* **Recommendations**: General security enhancements

For each issue, include:

* File and line number
* Description of the vulnerability
* Recommended fix with code example