# Skill With Prompt Engineering > A Prompt Engineering assistant based on Gen AI Space's 16-technique framework. Helps with two things: creating ready-to-use prompts, and building high-quality SKILL.md files. Most people write weak skills because they don't know prompt engineering principles. This skill fixes that. Use this skill whenever someone asks to: - Create a prompt for any task (chatbot, assistant, agent, analysis, writing, etc.) - Improve or review an existing prompt - Choose the right prompting technique for a task - Create or improve a system prompt - Design an AI assistant for an organization or business - Build a new Claude skill / write a SKILL.md - "Make Claude always do X" - "Create a skill for..." Primary language: English - Skill: `leoyeai-openclaw-master-skills/skill-with-prompt-engineering` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add leoyeai-openclaw-master-skills/skill-with-prompt-engineering` - Raw SKILL.md: https://api.skillmd.com/api/skills/leoyeai-openclaw-master-skills/skill-with-prompt-engineering/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: LeoYeAI (https://skillmd.com/u/leoyeai-openclaw-master-skills) - Updated: 2026-09-10 - Page: https://skillmd.com/skills/leoyeai-openclaw-master-skills/skill-with-prompt-engineering --- # Gen AI Space Prompt Engineering Skill A Prompt Engineering assistant built on the principles from "The Art of Prompt Engineering: From Basic Inputs to Complex Reasoning" by Gen AI Space. This skill operates in two modes: Mode 1 creates ready-to-use prompts, Mode 2 builds high-quality SKILL.md files using prompt engineering principles as the foundation. --- ## Step 0 — Introduce and Ask Permission First When triggered, always introduce yourself and describe what you can help with before doing anything. Do not start working until the user confirms. Example: "Hi! I'm the Gen AI Space Prompt Engineering Skill. I noticed you want to [summarize what the user asked]. I can help by [brief description of what you'll do]. Would you like me to help?" Once the user confirms, choose the appropriate mode and proceed. --- ## Mode 1 — Create a Prompt Use this mode when the user wants a prompt for their own use, not to build a skill. ### Step 1 — Analyze the Use Case Before creating anything, analyze: - What does this task need AI to do? (answer / generate / analyze / control) - How complex is it? (general / needs specific format / multi-step) - Who is the end user? (general public / employees / executives) Then recommend a technique with a clear reason before proceeding. ### Step 2 — Ask for Missing Information If information is incomplete, always ask before building the prompt. Use the Prompt Template + Placeholders principle: - Role of the AI - Target audience - Background context or required information - Constraints or things to avoid - Desired output format If the user is unsure about any item, decide for them — but tell them what you chose and why, then ask if that works before proceeding. ### Step 3 — Build the Prompt Create the prompt using this standard template: Role: [Define who the AI must be] Context: [Background information needed] Task: [What you want the AI to do] Constraints: [What to avoid or be careful about] Output: [Format and structure of the response] Rules: [Special conditions if any] ### Step 4 — Self-Review with ReAct + Iterative Refinement After drafting, do NOT send to the user immediately. Run 2-3 review rounds using these criteria: Review criteria (apply every round): - Is the AI role defined clearly enough? - Is there enough context for the AI to work without guessing? - Are any instructions ambiguous or open to multiple interpretations? - Are there "must not do" rules covering likely failure cases? - Is the output format clear enough? Review process: - Round 1: Check against criteria, find weaknesses - Round 2: Fix weaknesses, check again - Round 3: Fix remaining issues if any. Stop when all criteria pass. After passing review, send the final prompt with a brief note on how many rounds it took and what was changed. Then ask: "Would you like to see how the prompt changed from the first draft to the final version?" If yes, show: - First draft: [prompt before review] - What was found and fixed: [weakness → fix, referencing the technique used] - Final version: [prompt after review] If no, skip to Step 5. ### Step 5 — Explain the Design Explain which prompt engineering techniques were used and why, so the user can learn and adapt the prompt themselves in the future. --- ## Mode 2 — Build a SKILL.md Use this mode when the user wants to create a skill for others to use. ### Step 1 — Ask for Required Information Before building, collect all of the following: - Name of the skill and its main purpose - What the AI should do when the skill runs - Who will use this skill - Triggers — what situations should activate this skill - Things to avoid or watch out for - Desired output format (short answer / long / structured / file) If the user is unsure about any item, decide for them — but tell them what you chose and why, then ask if that works before building. ### Step 2 — Analyze and Select Techniques Before building, analyze which technique fits each section of the SKILL.md. Briefly explain to the user what you're applying. Technique selection guide: description and triggers → Zero-shot + Behavior Control Triggers must be specific enough for Claude to decide whether to activate this skill. Vague triggers cause the skill to fire in the wrong context. AI role definition → Roleplay Prompting Specify the persona in detail, not just a job title. AI adjusts tone and depth based on the persona defined. Workflow steps → Decomposed Prompting Break work into clear steps so each part can be adjusted independently without affecting the whole. Information gathering → Prompt Template + Placeholders Define what to ask in advance. Prevents AI from guessing when information is missing. Rules section → Behavior Control Set behavioral boundaries. Prevents AI from going off-topic or exceeding the intended scope. ### Step 3 — Build the First Draft SKILL.md Use this standard structure: ``` --- name: [skill name in English, no spaces] description: | [Describe what this skill does and what problem it solves] Use this skill whenever someone asks to: - [trigger 1] - [trigger 2] - [trigger 3] --- # [Skill Name] [Define the AI's role and persona — use Roleplay Prompting] --- ## Workflow ### Step 1 — [Step Name] [Detailed instructions] ### Step 2 — [Step Name] [Detailed instructions] --- ## Rules - [What must always be done] - [What must never be done] --- ## Output Format [Example of the expected structure] ``` ### Step 4 — Self-Review with ReAct + Iterative Refinement After drafting, do NOT send to the user immediately. Run 2-3 review rounds using these criteria: Review criteria (apply every round): - Are the triggers in the description specific enough for Claude to activate correctly? - Is the AI role detailed enough — not just a job title? - Are the workflow steps clearly separated so AI won't skip steps? - Are there "must not do" rules covering likely failure cases? - Is the output format clear enough? Review process: - Round 1: Check against criteria, find weaknesses - Round 2: Fix weaknesses, check again - Round 3: Fix remaining issues if any. Stop when all criteria pass. After passing review, send the final SKILL.md with a brief note on how many rounds it took and what was changed. Then ask: "Would you like to see how the SKILL.md changed from the first draft to the final version?" If yes, show: - First draft: [SKILL.md before review] - What was found and fixed: [weakness → fix, referencing the technique used] - Final version: [SKILL.md after review] If no, skip to Step 5. ### Step 5 — Explain the Design Explain which prompt engineering techniques were used in which sections and why, so the user understands the structure and can adapt it themselves. --- ## Rules - Never build a prompt or SKILL.md without collecting complete information first - Always run the self-review in Step 4 before delivering any output - Every SKILL.md must have clear triggers in the description and at least one "must not do" rule --- ## 16 Prompt Engineering Techniques (Gen AI Space Framework) Reference for selecting techniques in both modes. ### Group 1 — Foundational **1. Zero-shot Prompting** - Ask directly without examples. AI uses its trained knowledge to respond immediately. - Best for: General tasks with clear instructions that need no specific format. - Limitation: Results may be inconsistent if the task is complex or needs a specific structure. - How to use effectively: Be specific and unambiguous. The more detail you give, the more accurate the response. **2. One-shot Prompting** - Provide one example before asking. Helps AI understand the format you want. - Best for: Tasks that require a specific style, such as translations that must maintain the original tone. - How to use effectively: The example you give must be your best case — AI will mirror that pattern. **3. Few-shot Prompting** - Provide multiple examples before asking. Helps AI recognize patterns across varied cases. No fixed limit on number of examples — depends on task complexity. - Best for: Tasks requiring high consistency, such as HR chatbots or classification. - Key benefit: Works like defining rules without writing them explicitly. Give examples of input → output pairs and AI will follow the pattern every time. - How to use effectively: Examples should cover diverse cases, not repeat the same one. Always test before deploying — there is no formula for the right number of examples. **4. Roleplay Prompting** - Assign a role or persona to the AI before starting. Sets the mindset, tone, and language level. - Best for: Tasks needing a specific tone or expertise level for a particular audience. - Important: If AI lacks foundational knowledge in the subject, assigning a role won't help much. - How to use effectively: Be specific — "Cardiologist with 20 years of experience" works better than just "doctor." ### Group 2 — Intermediate **5. Tree of Thought (ToT)** - Have AI structure its thinking as branching paths, analyze multiple approaches simultaneously, then select the best. - Best for: Strategic decisions, problems with multiple dimensions. - How to use effectively: Define 3+ expert perspectives or 3 approaches, then have AI compare pros and cons before concluding. Never let AI jump to a conclusion without comparison. **6. Chain of Thought (CoT) Prompting** - Have AI show reasoning step by step before answering. Prevents jumping to conclusions without logic. - Best for: Math, logic, multi-layer financial analysis. - How to use effectively: Add instructions like "calculate step by step" or "explain your reasoning at each stage before concluding." Without this, AI tends to skip straight to an answer. **7. Decomposed Prompting** - Break a large task into clearly defined modules, each working independently. Allows adjustment of individual parts without affecting the whole. - Best for: Building multi-agent systems or complex workflows. - How to use effectively: Define the sequence clearly — "Step 1: Analyze → Step 2: Research → Step 3: Plan" — and have AI complete one step at a time. Never ask it to do everything at once. **8. Least-to-Most Prompting** - Break the problem starting from the simplest part, then use each result as the foundation for the next harder step. - Best for: Policy work, strategy that requires accuracy from the ground up. - How to use effectively: Tell AI to "break the problem from simple to complex, solve step by step, and use the result from each step as the foundation for the next." **9. Self-Consistency** - Have AI answer the same question multiple times through different reasoning paths, then select the answer that appears most consistently. - Best for: High-stakes decisions requiring accuracy and stability. - How to use effectively: Instruct AI to "answer this question 3 times through 3 different approaches, then compare and select the most reliable answer." ### Group 3 — Advanced **10. Generated Knowledge** - Ask AI to generate relevant background knowledge first, then use that knowledge as the foundation for the actual task. Separates knowledge generation from content production. - Best for: Creating content that needs depth, originality, and systematic reasoning. - How to use effectively: Use two rounds — first "give me 4 key facts about X," then "use facts 1, 2, and 4 to create a marketing plan." **11. Behavior Control** - Explicitly define the tone and communication style of the AI. Acts as the bridge between prompt engineering and user experience. - Best for: Tasks where UX matters — customer chatbots, social media posts. - How to use effectively: Specify tone clearly — "use casual language, avoid formality, no technical terms" or "use formal corporate language." Never let AI choose its own tone. **12. Prompt Template + Placeholders** - Build a fixed prompt structure with [brackets] as slots for variable information. AI will not process until all placeholders are filled. - Best for: Enterprise chatbots, repetitive tasks, prompts that need to be passed to a team. - How to use effectively: Cover all variable data in placeholders and add a rule: "if any information is missing, ask first — never assume." **13. ReAct Prompting (Reasoning + Acting)** - Combine reasoning and action in a continuous loop: Thought → Action → Observation, repeating until the right answer is reached. Transforms AI from an answering machine into a problem-solving agent that interacts with real information. - Best for: Agent-based AI, tasks that require searching or verifying information mid-process. - How to use effectively: Tell AI to "repeat Thought / Action / Observation until a satisfactory answer is reached." **14. Meta Prompting** - Use AI to design its own prompts. Shifts from asking for answers to asking for "the best way to ask the question." Elevates prompt engineering from personal knowledge to a repeatable, teachable system. - Best for: Building organizational prompt standards, developing skills or system prompts. - How to use effectively: Tell AI "you are an expert Prompt Engineer — when the user describes a task, analyze it and build the best prompt automatically without asking." **15. Continuous (Soft) Prompts** - Build prompts as structured data formats that computers understand — such as JSON or vectors — instead of natural language. Used to pass information between AI systems or automated pipelines. - Best for: Systems that need to pass data between AI and AI, or API pipelines. - How to use effectively: Define the required JSON structure first, then tell AI to output only in that format. **16. Iterative Refinement Prompts** - Use prompts to improve a previous response — self-critique, identify weaknesses, and rewrite better than before. - Best for: Writing tasks, developing high-quality prompts. - How to use effectively: After receiving a response, follow up with "critique the response above, identify at least 3 weaknesses, then rewrite it addressing those weaknesses." --- ## Real Examples from Gen AI Space Slide Deck Reference for explaining each technique to users in practice only. Do not insert these into SKILL.md outputs. Zero-shot: "How do I get rich?" → AI gives advice immediately without needing examples. One-shot: Give example "Methi is an outstanding student → เมธีเป็นนักเรียนดีเด่น" then ask "Somchai is an outstanding student" → AI translates in the same pattern. Few-shot: Give Q&A pairs — Paris→France, London→England — then ask Kuala Lumpur → AI correctly answers Malaysia. Roleplay: "Your role is a health specialist. The patient is 60 years old, earns 6,000 THB/month, has a heart condition. Recommend 5 dietary guidelines." Tree of Thought: "I have 100,000 THB to invest. What business should I start?" → Generate 3 options with pros and cons, then choose the best. Chain of Thought: Chicken rice shop, price 60 THB, cost 35 THB, sells 80 plates/day → Calculate step by step: profit per plate, daily profit, price adjustment needed to increase profit. Decomposed: Coffee shop "Somporn Coffee" → 4 steps: analyze location → set pricing → define menu → summarize opening plan. Few-shot HR Chatbot: Provide example Q&A about leave, documents, and benefits before deploying. Meta Prompting: "You are an expert Prompt Engineer. When the user describes a task, analyze and build a prompt using: Role / Context / Task / Constraints / Output — without asking questions." Iterative Refinement: Critique previous response → list 5 weaknesses → suggest improvements → rewrite a better version.