prompt-engineer
Prompt engineering. Craft, analyze, harden, convert, design tool prompts, and build PromptOps/eval plans. Use for system, agent, tool, RAG prompts. NOT for running prompts or building agents.
Prompt engineering. Craft, analyze, harden, convert, design tool prompts, and build PromptOps/eval plans. Use for system, agent, tool, RAG prompts. NOT for running prompts or building agents.
Quick Start
Section titled “Quick Start”Install:
npx skills add github:wyattowalsh/agents --skill prompt-engineer -y -g --agent claude-code --agent codex --agent gemini-cli --agent antigravity --agent github-copilot --agent opencodeUse: /prompt-engineer <mode> [target]
Works with Claude Code, Gemini CLI, Codex, and other agentskills.io-compatible agents.
What It Does
Section titled “What It Does”prompt-engineer designs and audits the full prompt context, not only the wording of a system prompt. It covers prompt structure, target-model fit, trust boundaries, tool definitions, eval design, and production PromptOps controls.
$ARGUMENTS | Action |
|---|---|
craft <description> | Craft a new prompt from scratch |
analyze <prompt or path> | Diagnose and improve an existing prompt |
audit <prompt or path> | Read-only prompt review |
convert <source-model> <target-model> <prompt or path> | Port between model families |
evaluate <prompt or path> | Build an eval framework |
harden <prompt or path> | Stress-test injection, trust boundaries, and robustness |
tool <tool definition or schema> | Design or review model-facing tool definitions |
promptops <prompt or path> | Plan versioning, rollout, monitoring, and rollback |
| Raw prompt text | Auto-detect existing prompt and audit |
| Natural-language prompt request | Auto-detect craft mode |
| Empty | Show mode menu |
Shared Preflight
Section titled “Shared Preflight”All modes start with the same checks:
-
Ingest — Read prompt text or the supplied file path.
-
Classify — Identify mode, target model/provider, model class, deployment context, and trust boundary.
-
Load selectively — Read only the reference files needed for the selected mode.
-
Evidence-scope claims — Classify non-obvious recommendations as official docs, provider guide, research, community heuristic, local practice, or single-study.
-
Refuse wrong scope — Do not run prompts, build agents, or perform implementation work from this skill.
Production Modes
Section titled “Production Modes”Harden
Section titled “Harden”Use harden for prompts that handle user input, retrieved documents, tool results, external content, user-facing output, or write-capable tools. The output maps attack surfaces, controls, residual risk, and required adversarial evals.
Use tool for function schemas, MCP tools, OpenAPI fragments, or model-facing tool-selection guidance. The review checks name clarity, description specificity, parameters, errors, permission class, adjacent-tool overlap, and tool-result injection risk.
PromptOps
Section titled “PromptOps”Use promptops to turn prompt changes into a deployable workflow: versioning, linked evals, rollout stages, monitoring, provider fact refresh, and rollback.
Model-Class Detection
Section titled “Model-Class Detection”| Model Class | Examples | Guidance |
|---|---|---|
| Instruction-following | GPT-4.1-style, non-thinking Gemini/Claude modes, standard Llama variants | More explicit structure and examples can help; test before adding complexity |
| Reasoning | GPT-5.5/GPT-5.x reasoning modes, Claude extended thinking, Gemini thinking, o-series models, reasoning Llama variants | Avoid mandatory hidden CoT transcripts; use provider-supported reasoning controls or concise planning/preambles when current docs support them |
Critical Rules
Section titled “Critical Rules”- Do not recommend mandatory hidden chain-of-thought transcripts for reasoning models.
- Use clear delimiters for multi-section prompts; XML is a strong default for Claude and many complex prompts, but provider guidance wins.
- Run security review for any prompt handling untrusted input.
- Recommend evals for any non-trivial prompt.
- Cite reference files and last-verified dates for provider-specific claims.
- Keep
auditreport-only and read-only. - Refuse and redirect requests to run prompts, build agents, or do non-prompt implementation work.
- Update evals when dispatch behavior or modes change.
- Run
scripts/validate-references.pyafter reference, dispatch, or eval changes.
| Field | Value |
|---|---|
| Name | prompt-engineer |
| License | MIT |
| Version | 1.2.0 |
| Author | wyattowalsh |
| Field | Value |
|---|---|
| Model | opus |
| Argument Hint | <mode> [target] |