メニュー
Find opportunities to add metrics and estimate numbers when exact data is unavailable. Use when the user wants to quantify achievements, add numbers, percentages, or impact metrics to a resume.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Persistent dietary safety layer for DoorDash CLI (dd-cli) ordering. Stores a personal/household dietary profile (allergens with severity tiers, diets, dislikes) that every cart is vetted against before checkout, with a deterministic tripwire — the vetting step saves the full cart contents to a vetted-cart dump, and a PreToolUse hook re-greps that dump against the anaphylaxis-severity allergen list before any checkout URL is allowed. Use when the user mentions allergies or dietary restrictions, when ordering food for someone with restrictions, or on every dd-cli cart flow while this skill is installed. A tripwire, not medical-grade — the human checkout page is the final check.
Group food ordering through the DoorDash CLI (dd-cli) from a persistent team roster. One request ("lunch for the team") fans out into a single merged cart with every line attributed to its eater via a person-to-cart-item-id ledger, per-person cost split with fee proration, payer rotation history, and a checkout gate that re-derives allergen conflicts against the roster live. Use when ordering for multiple people — team lunch, incident-response food, "collect orders from the thread" — or for /whose-turn payer rotation questions. Handles paste-a-thread intake: paste a Slack/chat thread and it builds the order ledger from it.
Accountability layer for agent-driven DoorDash ordering. Works with the doordash-audit-log hook (which appends every dd-cli invocation to an append-only audit log) and the /doordash-report command to answer "what has my AI been ordering and what did it cost" from data instead of memory. Use when the user asks about their DoorDash spending, ordering patterns, what the agent did in past sessions, or wants jq recipes for querying the audit log. Covers log schema, query patterns, rotation, and privacy guidance.
Named, context-bound saved DoorDash orders ("post-gym", "late-night deploy") recalled through the DoorDash CLI (dd-cli) with a mandatory cart-diff before any checkout link is handed over. Use when the user names a saved order ("order my post-gym bowl", "the usual", "my Friday ramen"), wants to save the order they just placed as a playbook, or asks to list/remove saved orders. Persists name→order-uuid playbooks across sessions, catches silent menu/price drift on every recall, and self-heals stale playbooks when a restaurant's menu changes. Requires dd-cli (macOS Apple Silicon, waitlist-gated).
Hard spending policy for agent-driven DoorDash ordering through the DoorDash CLI (dd-cli). Per-order ceiling, daily/weekly/monthly caps, cooldown between orders, and blocked hours — enforced deterministically by routing every cart-mutation and checkout through the dd-guard wrapper script, which prices the cart, checks the policy against a persistent spend ledger, and refuses out-of-policy checkouts with exit code 2. Use when the user wants budget limits on agent food ordering, asks "how much have I spent on DoorDash", wants to set spending caps, or whenever building carts / checking out with dd-cli while this skill is installed. Pairs with a PreToolUse hook that denies raw dd-cli checkout calls that bypass the wrapper.
Segment a SKU portfolio on value (ABC) and demand variability (XYZ), produce the 9-box with a planning policy per cell, and reallocate planner attention accordingly. Use when the user mentions ABC analysis, inventory segmentation, SKU rationalization, stok segmentasyonu, envanter sınıflandırma, or asks which items deserve forecasting effort. Differentiator - ABC alone is treated as half an answer; policy lives in the value x variability combination.
| name | resume-quantifier |
| description | Find opportunities to add metrics and estimate numbers when exact data is unavailable. Use when the user wants to quantify achievements, add numbers, percentages, or impact metrics to a resume. |
Use this skill when the user:
The Problem:
Studies Show:
1. Money
2. Time
3. Percentages
4. Volume/Scale
5. Quality
6. Frequency
For any experience, ask:
Scale Questions:
Impact Questions:
Comparison Questions:
Sales:
Marketing:
Customer Service:
Operations:
Engineering:
Project Management:
HR/Admin:
When you don't have exact numbers:
Principle: Estimate low to maintain credibility
Example:
Format: "X-Y" or "X to Y"
Examples:
Format: "X+" or "at least X"
Examples:
Format: Calculate from known totals
Example:
Format: Work backwards from frequency
Example:
"Improved [X] from [before number] to [after number], resulting in [Y]% improvement"
Example:
"Improved page load time from 8 seconds to 2 seconds, resulting in 75% reduction and 20% increase in user engagement"
"[Verb] [number] [things], resulting in [impact]"
Example:
"Managed 25 concurrent projects worth $3M, delivering 95% on-time with zero budget overruns"
"Processed [number] [items] per [time period], achieving [quality metric]"
Example:
"Resolved 50+ customer tickets daily, maintaining 98% satisfaction rating and 4-hour average response time"
"Ranked #[X] out of [Y] in [metric], [context]"
Example:
"Ranked #2 out of 45 sales representatives nationally, generating $3.2M in annual revenue"
Solution: Focus on YOUR contribution
Example:
Solution: Quantify activities and inputs
Example:
Solution: Measure the work itself
Example:
Solution: Use percentages or ranges
Example:
Solution: Quantify learning, throughput, accuracy
Example:
When quantifying a resume:
# RESUME QUANTIFICATION
## Analysis Summary
**Bullets without numbers:** X
**Bullets with numbers:** Y
**Target:** 100% of bullets should have at least one metric
## Quantified Bullets
### Original Bullet #1:
"Managed customer accounts"
### Questions to Find Metrics:
- How many accounts? → [User answer: ~40]
- What was the revenue? → [User answer: ~$2M]
- What results did you achieve? → [User answer: retained most]
### Quantified Version:
"Managed portfolio of 40 enterprise accounts representing $2M ARR, achieving 95% retention rate"
### Metrics Added:
- Account count: 40
- Revenue: $2M ARR
- Retention: 95%
---
### Original Bullet #2:
[Continue for each bullet]
## Estimation Notes
- [Metric]: Estimated based on [reasoning]
- [Metric]: Conservative estimate using [method]
## Remaining Questions
- [Questions to ask user for missing information]
For each bullet:
Every bullet can be quantified. If you think your work can't be measured, you haven't asked the right questions yet.
The goal isn't to have impressive numbers—it's to have SPECIFIC numbers that show the scope and impact of your work.