Standardize recipes with portions, costs, and procedures. TRIGGERS - Use when user needs help with recipe-standardizer related tasks.
Scanned 9/7/2026
Install to Claude Code
Skills Directorynpx -y skills add Winbda/claude-skills-collection --skill recipe-standardizer --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Recipe Standardizer?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/winbda-recipe-standardizer)More formats (shields.io, HTML) on the badges page.
---
name: recipe-standardizer
description: |
Standardize recipes with portions, costs, and procedures.
TRIGGERS - Use when user needs help with recipe-standardizer related tasks.
category: Food & Beverage
version: 1.0
---
# recipe-standardizer
## Workflow
1. **Understand Requirements** - Context, audience, goals, constraints
2. **Research & Analyze** - Best practices, frameworks, background
3. **Create Draft** - Structured, actionable, tailored output
4. **Review & Refine** - Quality check, consistency, completeness
## Output Format
**Context:** [Situation] | **Objective:** [Goal] | **Audience:** [Who]
### Key Components
| Component | Details | Owner | Timeline |
|-----------|---------|-------|----------|
| [Item] | [Specifics] | [Who] | [When] |
### Action Plan
1. **Immediate:** [First steps]
2. **Short-term:** [Build momentum]
3. **Medium-term:** [Scale]
### Success Metrics
| Metric | Target | Method |
|--------|--------|--------|
| [KPI] | [Goal] | [Track] |
## Quality Checklist
- [ ] Tailored to context
- [ ] Actionable steps
- [ ] Measurable criteria
- [ ] Professional format
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
