prompt

Diagnoses and refines prompts by improving structure, techniques, and wording.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/psw7205/skills --skill prompt-psw7205
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prompt
Source: https://github.com/psw7205/skills/tree/main/skills/prompt
Command: npx skills add https://github.com/psw7205/skills --skill prompt-psw7205

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Drafting effective prompts is hard: instructions are often vague, structure is missing, and advanced techniques get over- or under-applied. This Skill diagnoses a prompt draft or a stated goal, fixes only what is lacking, and verifies the result against a checklist. ## Core Features & Use Cases - Diagnosis-driven refinement: Evaluates structure (Instruction, Context, Input Data, Output Indicator), technique fit, and wording, then applies targeted fixes instead of rewriting everything. - Technique catalog with escalation: Guides selection from zero-shot to few-shot, CoT, self-consistency, and prompt chaining, with special handling for reasoning models like o1/o3 where manual CoT should be removed. - Checklist verification: Validates the final prompt against structure, expression, technique, and safety criteria (e.g., no leaked API keys, fallback responses for factual tasks). - Use Case: You have a rough system prompt for a classification task. The Skill detects missing output format and unbalanced few-shot labels, restructures it with delimiters, and explains each change. ## Quick Start Ask the assistant to refine your draft prompt or create a new prompt for a specific task, for example by saying "refine this prompt for classifying customer feedback into positive, negative, and neutral categories".

Frequently Asked Questions about prompt

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

FAQPage Schema
How do I improve a poorly written prompt?▼

Diagnose the prompt across three axes: structure (missing Instruction, Context, Input Data, or Output Indicator), technique fit, and wording clarity. Fix only the weak areas, then verify against a checklist covering delimiters, output format, and fallback responses.

What prompt engineering technique should I use for my task?▼

Start with the simplest approach and escalate only when needed: zero-shot for clear tasks, few-shot for classification with format consistency, CoT for multi-step reasoning, self-consistency for higher reliability, and prompt chaining for multi-stage workflows.

Should I use chain-of-thought prompting with reasoning models like o1 or o3?▼

No. Reasoning models perform their own internal reasoning, so manual CoT phrases like "step by step" interfere and should be removed. Keep instructions simple and direct, state high-level constraints, and prefer XML-structured output.

When should I not add few-shot examples or CoT to a prompt?▼

Avoid extra techniques when zero-shot instructions already produce adequate results. Adding CoT to simple classification tasks makes responses slower and less stable, and few-shot examples with imbalanced label distributions bias the output.

How do I structure a prompt to prevent prompt injection?▼

Separate user input from system instructions structurally by wrapping user data in XML tags like <user_query>. Place the instruction at the start, use delimiters between sections, and keep critical constraints at the beginning and end of the prompt.