engineer-prompt

Diagnose prompt failures and rewrite markdown prompts using minimal prompt-engineering techniques.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Tyler-R-Kendrick/copilot-auto-training --skill engineer-prompt-tyler-r-kendrick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engineer-prompt
Source: https://github.com/Tyler-R-Kendrick/copilot-auto-training/tree/main/skills/engineer-prompt
Command: npx skills add https://github.com/Tyler-R-Kendrick/copilot-auto-training --skill engineer-prompt-tyler-r-kendrick

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires dspy, pyyaml, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Prompts often underperform because of vague instructions, missing output contracts, bloated schemas, or misapplied techniques, and teams waste effort on advanced patterns when simpler fixes would work. This Skill diagnoses the actual failure mode and recommends the smallest effective prompt-engineering technique before rewriting. ## Core Features & Use Cases - Diagnosis-first prompt improvement: Distinguishes prompt problems from retrieval, tooling, or requirements issues before recommending changes. - Technique selection guidance: Compares grounding, structured output, few-shot, chaining, reasoning patterns, RAG variants, and parameter tuning with explicit tradeoffs. - Token-budget optimization: Moves large schemas into referenced JSON Schema files, formalizes workflows as Mermaid or BPMN artifacts, and applies selective interspersed repetition. - Use Case: A team has a prompt that pastes a long JSON schema and a multi-step approval workflow inline. The Skill recommends externalizing the schema, referencing a Mermaid workflow file, and produces a compact rewritten markdown prompt. ## Quick Start Ask the agent to review your markdown prompt file, explain which prompt-engineering technique fits best, and provide a rewritten version with an explicit output contract.

Frequently Asked Questions about engineer-prompt

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

FAQPage Schema
How do I improve a vague or underperforming prompt?

Start by diagnosing the failure mode: unclear objective, missing context, missing output schema, or weak examples. Then apply the smallest fix, such as clearer instructions plus output priming, before escalating to reasoning or retrieval techniques.

When should I use structured output vs few-shot prompting?

Use structured output first when the response feeds a downstream system, API, or evaluator. Add few-shot examples only when edge cases remain messy after the schema is defined, and move large schemas into referenced JSON Schema files.

How do I reduce prompt length without losing instructions?

Keep the live prompt focused on the task and critical constraints, move bulky schemas into referenced JSON Schema files, and formalize long workflows as Mermaid or BPMN artifacts. Use interspersed repetition only for the highest-risk rule near the step where it matters.

Should I fix hallucinations with chain-of-thought or few-shot prompting?

Usually neither, if the root cause is stale retrieval, missing source IDs, or weak source quality. Fix the retrieval and grounding layer first, then add grounding instructions with citations as a secondary prompt-level safeguard.

When is vector RAG a bad fit compared to graph RAG?

Vector RAG fits local questions over large corpora via semantic similarity, but fails for global relationship questions across a dataset. Graph RAG suits entity-relationship reasoning, though its ingestion cost is unjustified for small corpora.

What are the limitations of prompt engineering fixes?

Prompt changes cannot fix application logic bugs, stale retrieval, missing tools, or unclear product requirements. In those cases the Skill explicitly states the real blocker and offers only secondary prompt guidance.