template-design
Creating reusable, parameterised prompt templates for consistent outputs.
- Installs
- 297
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/owl-listener/ai-design-skills --skill template-design- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads template-design automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Template Design
A prompt template is a reusable prompt structure with variable slots that get filled at runtime. Templates create consistency across similar tasks and make prompt management scalable.
Template Anatomy
A template has:
- Fixed text: The parts that stay the same every time (instructions, format, role)
- Variables: Slots that get filled with specific content (user input, retrieved data, configuration)
- Conditional sections: Parts that appear or disappear based on context
- Default values: What fills a variable if no specific value is provided
Designing Variables
Each variable should be:
- Named clearly:
{user_query}not{input1} - Typed: Is it free text, a selection from options, a number, a boolean?
- Bounded: What are valid values? What's the maximum length?
- Documented: What is this variable for? Where does its value come from?
- Defaulted: What happens if the value is missing?
Template Patterns
- Task template: A template for a specific type of task. Variables capture the task-specific details while instructions remain constant.
- Persona template: A template where the persona is variable but the task structure is fixed. Useful for multi-persona products.
- Format template: A template where the output format is variable but the analysis approach is fixed.
- Escalation template: A base template with additional sections that activate at higher complexity levels.
Template Composition
Complex prompts can be built from smaller templates:
- Base template: Core instructions that apply to everything
- Task overlay: Task-specific instructions layered on top
- Context injection: Retrieved information inserted at a specific point
- User preferences: Personal settings that modify behavior
Template Quality Criteria
- Consistency: The template produces reliably similar outputs for similar inputs
- Flexibility: The variables allow enough variation for diverse use cases
- Clarity: The template is easy to read, maintain, and modify
- Testability: You can verify the template works with a standard set of test inputs
- Maintainability: Changes to one part don't break other parts
Design Artefacts
- Template library with documentation
- Variable specifications per template
- Test input sets for each template
- Template versioning and change log
- Composition rules for combining templates
FAQ
What does the template-design skill do?
Creating reusable, parameterised prompt templates for consistent outputs.
How do I install template-design?
Run npx skills add https://github.com/owl-listener/ai-design-skills --skill template-design in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/template-design/ (personal) or .claude/skills/template-design/ (project).
Which AI agents can use template-design?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is template-design safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains template-design?
It is published by owl-listener in owl-listener/ai-design-skills. It has 297 recorded installs.
More from owl-listener/ai-design-skills
system-prompt-structure
owl-listener/ai-design-skills
Anatomy of effective system prompts — role, context, constraints, format.
guardrail-design
owl-listener/ai-design-skills
Open the skill to read its SKILL.md instructions.
constraint-specification
owl-listener/ai-design-skills
Defining output format, length, tone, and content boundaries within prompts.
generative-ui
owl-listener/ai-design-skills
Designing interfaces where AI generates UI components dynamically.
conversation-patterns
owl-listener/ai-design-skills
Turn-taking, repair sequences, grounding, and dialogue structure for human-AI interaction.
progressive-disclosure
owl-listener/ai-design-skills
Open the skill to read its SKILL.md instructions.
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available