Design Award Pipeline Agent Skill
Route and coordinate an end-to-end design-award workflow across winner research, evidence-based evaluation, award matching, entry-text preparation, and final submission checking. Use when a user asks for a complete award plan, does not know which Design Judge skill to use, wants multiple stages coordinated, or needs a resumable workflow with explicit handoffs. Do not replace the specialist skills, invent project facts, treat scores as winning probabilities, or bypass current official-rule verification.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/SeanJ1ang/design-judge-skills --skill design-award-pipelineThe instruction itself
5 sections, as written by the authorDesign Award Pipeline
Coordinate the specialist Design Judge skills without duplicating their rules.
Route the request
Choose the smallest sufficient route:
| User goal | Route |
|---|---|
| Find comparable winners | design-award-search |
| Diagnose or score the design | design-evaluation |
| Select an award, route, or category | design-award-match |
| Prepare entry fields and copy | design-information-prep |
| Audit a concrete submission package | design-submission-check |
| Complete journey | evaluation or match → information prep → submission check; add search only when precedents are needed |
If the user has not provided enough information to select a route, ask at most one short question. Otherwise proceed with explicit assumptions.
Maintain the handoff
Create or update a compact handoff record using references/handoff-schema.json. Keep these concepts separate:
- user-supplied facts;
- evidence-backed findings;
- model inferences;
- missing facts and live-rule checks;
- decisions already approved by the user;
- the next recommended specialist skill.
Do not copy long specialist outputs into the handoff. Store identifiers, decisions, blockers, source links, and artifact paths.
Coordinate stages
- State the selected route and why it is sufficient.
- Invoke or follow the relevant specialist Skill exactly.
- Preserve its uncertainty labels, evidence confidence, and blockers.
- Stop for user approval when the target award, maturity track, or another consequential choice changes downstream work.
- Hand off only facts supported by user material or cited official sources.
- End with the completed stage, unresolved blockers, and the next optional stage.
Boundaries
- Never merge fit score, design score, and evidence confidence into one number.
- Never claim or estimate a probability of winning.
- Never treat observed winners as official jury weights.
- Never mark a package ready when time-sensitive official rules remain unverified.
- Never invoke all specialist skills when one is enough.
Other skills for the same job
different authors, same section of the catalogue
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.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
How to use it
Take seanj1ang/design-award-pipeline from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.