prompt-engineering

Generate, improve, and debug LLM prompts with success criteria and structured sections.

3|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Muvon/octomind-tap --skill prompt-engineering-muvon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prompt-engineering
Source: https://github.com/Muvon/octomind-tap/tree/main/skills/prompt-engineering
Command: npx skills add https://github.com/Muvon/octomind-tap --skill prompt-engineering-muvon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you generate, improve, analyze, and debug LLM prompts when outputs are wrong, inconsistent, poorly formatted, or misaligned with your intent.

Core Features & Use Cases

  • Prompt generation and upgrades: Draft new prompts or revise existing ones into clearer contracts with explicit success criteria, role, format, and constraints.
  • Technique selection for reliability: Choose appropriate reasoning/agent patterns (e.g., few-shot for format, self-consistency for correctness, tree-of-thought for exploration) based on the task type.
  • Failure-mode diagnosis and fixes: Identify common issues like underspecification, instruction attenuation, context rot, sycophancy, and task drift, then apply the smallest effective change.
  • Output control and token efficiency: Improve structure using XML-style sections, reduce hallucination risk, and design prompts for better context handling and caching.

Quick Start

Ask an AI to rewrite your prompt so it meets your stated success criteria, follows a precise output format, and fixes the specific failure mode you observed.

Frequently Asked Questions about prompt-engineering

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

FAQPage Schema
How do I fix inconsistent LLM outputs and format errors in my system prompt?

Fix inconsistent LLM outputs by diagnosing common failure modes like underspecification and context rot, then applying the smallest effective change to your system prompt using explicit success criteria and structured sections.

What is the best way to structure a prompt for reliable structured outputs?

The best way to structure a prompt for reliable structured outputs is using XML-style sections for context placement and applying few-shot prompting techniques to enforce precise formatting and reduce hallucination risk.

When should I use few-shot prompting versus other reasoning techniques in my LLM prompting?

Use few-shot prompting for format-sensitive outputs, self-consistency for correctness, and tree-of-thought reasoning techniques for exploration, selecting the pattern based on your specific task type and reliability requirements.

Why does my AI agent experience task drift and sycophancy during agentic workflows?

Task drift and sycophancy in agentic workflows occur due to instruction attenuation and context rot, fixable by rewriting agent prompts into clearer contracts with explicit constraints and token-efficient context handling.

How do I debug prompt failure modes like underspecification and instruction attenuation?

Debug prompt failure modes by identifying specific issues like underspecification or instruction attenuation, then generating clearer prompt contracts with appropriate role definitions, format constraints, and technique-specific guidance.

Can I improve token efficiency and context handling for format-sensitive LLM outputs?

Improve token efficiency and context handling for format-sensitive outputs by designing prompts with structured sections, optimizing context placement strategy, and applying technique-specific guidance for better caching.