prompter

Crafts structured prompts for delegating tasks to subagents using a seven-step framework.

1|Updated May 4, 2026
One-click install
npx skills add https://github.com/wesbragagt/nixos-config --skill prompter-wesbragagt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prompter
Source: https://github.com/wesbragagt/nixos-config/tree/main/home/skills/prompter
Command: npx skills add https://github.com/wesbragagt/nixos-config --skill prompter-wesbragagt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Delegating work to subagents often fails because prompts are vague, lack context, or omit success criteria, producing low-quality or unusable results. This Skill provides a systematic framework for writing delegation prompts that consistently yield high-quality subagent output. ## Core Features & Use Cases - 7-Step Prompt Framework: Covers intent definition, context, XML structuring, few-shot examples, role assignment, verification criteria, and return requirements. - Ready-to-Use Templates: Provides a reusable XML delegation template plus specialized patterns for code, research, and analysis tasks. - Quality Checklist & Anti-Patterns: Includes a pre-delegation checklist and a list of common mistakes (vague instructions, missing context, no verification) to avoid. - Use Case: Before asking a subagent to refactor a payment-processing function, use this Skill to build a prompt that specifies the role, constraints, verification steps, and exact return format so the subagent delivers reviewable, correct code. ## Quick Start Ask the AI to use the prompter skill to write a delegation prompt for a subagent that reviews your code for security issues.

Frequently Asked Questions about prompter

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

FAQPage Schema
How do I write a good prompt for delegating tasks to a subagent?

Follow the seven-step framework: define clear intent and output, provide context and motivation, structure with XML tags, add few-shot examples, specify the role and behavior, define verification criteria, and set explicit return requirements.

What structure should a subagent delegation prompt use?

Use XML tags to separate concerns: role, context, task, constraints, input, output_format, verification, and return. This unambiguous structure helps the subagent parse instructions, data, and success criteria independently.

Why do subagent prompts produce poor results?

Common causes are vague instructions, missing context about why the task matters, negative-only constraints, no verification criteria, and unspecified output format. The Skill's anti-patterns section lists these mistakes with corrections.

How many examples should a delegation prompt include?

Include three to five relevant, diverse few-shot examples wrapped in XML example tags, each showing a sample input and its expected output. Examples are most important for complex or ambiguous tasks.

When should I not use a structured delegation prompt?

Very simple, single-step tasks may not need the full template. The framework is designed for delegating substantive work where correctness matters, such as code changes, research, or multi-file analysis.