2
GitHub Stars
1
Bundled Files
3 weeks ago
Catalog Refreshed
2 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstart where the catalogue uses aiagentskills.
npx veilstart add skill fusengine/agents --skill prompt-creation- SKILL.md2.7 KB
Overview
This skill teaches techniques and templates for creating high-performance prompts that follow Anthropic conventions. It packages a 9-element system structure, emphasis strategies, and a tested creation workflow to produce consistent, reliable prompts. The content focuses on clarity, guardrails, and repeatable templates for developer and product use.
How this skill works
The skill inspects a prompt objective, audience, and constraints, then applies the 9-element Anthropic structure to produce a complete system prompt. It provides recommended wording levels for rules, examples for few-shot learning, and output-format templates. A step-by-step workflow guides prompt design, testing, and iteration to surface edge cases and add guardrails.
When to use it
- Designing system or assistant prompts for Anthropic-style agents
- Creating few-shot examples and structured output formats
- Onboarding new models or integrating prompts into code pipelines
- Building guardrails and safety rules for agent behavior
- Testing prompt robustness against edge cases
Best practices
- Start with a single-sentence objective and identify the target audience before drafting
- Always include explicit mandatory and forbidden behaviors; never leave error cases unspecified
- Use the 9-element structure: context, tone, rules, examples, input, task, scratchpad, output format, and prefill
- Prefer clear, graded instruction strength (e.g., Please → You should → Always → CRITICAL)
- Iterate with mental testing and edge-case examples before deploying prompts
Example use cases
- Generate a system prompt for a technical assistant that returns JSON with Analysis, Solution, and Recommendations
- Create few-shot examples for clarifying ambiguous user intents in customer support flows
- Draft a prompt that enforces strict privacy and data-handling rules for a medical domain agent
- Build a template for code-review agents that include a scratchpad and final answer tags
- Create adaptive tone prompts that switch between concise and detailed based on user preference
FAQ
Emphasize elements that affect correctness and safety first: Task Description + Rules, Examples, and Output Formatting. Tone and Prefill can be lighter unless user experience depends on them.
What strength of wording should I use for safety rules?
Use graded strength: start with direct recommendations for routine behaviors, escalate to MUST or CRITICAL for safety, legal, or privacy constraints to ensure zero tolerance is communicated.