quantification-metrics-step-1-establish-baseline
Sub-skill of quantification-metrics: Step 1: Establish Baseline (+4).
Best use case
quantification-metrics-step-1-establish-baseline is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of quantification-metrics: Step 1: Establish Baseline (+4).
Teams using quantification-metrics-step-1-establish-baseline should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/step-1-establish-baseline/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How quantification-metrics-step-1-establish-baseline Compares
| Feature / Agent | quantification-metrics-step-1-establish-baseline | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of quantification-metrics: Step 1: Establish Baseline (+4).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Step 1: Establish Baseline (+4) ## Step 1: Establish Baseline **Actions:** 1. Identify current state metrics 2. Measure actual time/cost/effort 3. Document pain points with frequency 4. Quantify error rates or issues **Questions to Answer:** - How long does the current process take? - How often is it performed? - What is the current cost? *See sub-skills for full details.* ## Step 2: Define Target State **Actions:** 1. Specify desired improvement 2. Set realistic targets 3. Identify automation opportunities 4. Define success criteria **Questions to Answer:** - What is the ideal state? - What level of improvement is realistic? - What can be automated vs. optimized? *See sub-skills for full details.* ## Step 3: Calculate Metrics **Actions:** 1. Apply time savings formula 2. Calculate cost savings 3. Determine efficiency gains percentage 4. Aggregate across use cases **Validation:** - Are calculations accurate? - Are assumptions documented? - Are ranges provided where uncertain? *See sub-skills for full details.* ## Step 4: Validate and Document **Actions:** 1. Verify calculations 2. Check for reasonableness 3. Document assumptions 4. Provide evidence or benchmarks **Validation Criteria:** - Math is correct - Assumptions are explicit - Comparisons are valid - Evidence supports claims **Example:** ```markdown ## Validation **Assumptions:** - Hourly rate: $75/hour (blended rate for administrative work) - Current invoice time: 15 minutes (observed average) - Target invoice time: 2 minutes (based on similar automation) - Frequency: 10 invoices/month (12-month average) **Evidence:** - Industry benchmark: 80-90% time reduction from invoice automation - Internal pilot: 85% reduction achieved in test period - Comparable systems: $10K-30K annual savings typical ```
Related Skills
portable-config-baseline-pattern
Extract machine-agnostic settings into portable template files while keeping machine-specific hooks and plugins separate
portable-baseline-pattern-implementation
Implement portable configuration baselines by separating machine-agnostic settings from machine-specific hooks and plugins
portable-baseline-pattern-extraction
Extract and separate portable baseline config from machine-specific overrides in multi-environment projects
portable-baseline-configuration-pattern
Separate portable/universal config from machine-specific settings to enable safe template reuse across environments
portable-baseline-config-pattern
Separate machine-portable baseline config from environment-specific hooks and plugins
metrics-tracking
Define, track, and analyze product metrics with frameworks for goal setting and dashboard design
hidden-folder-audit-step-1-inventory-all-hidden-folders
Sub-skill of hidden-folder-audit: Step 1: Inventory All Hidden Folders (+4).
skill-creator-step-1-name
Skill-creator checklist template. Use when scaffolding a new skill with step-by-step instructions and verification items.
skill-creator-step-1-define-the-skill-scope
Define skill scope and write frontmatter. Use when creating a new skill to establish problem, inputs, outputs, and YAML metadata.
clean-code-step-1-api-compatibility-check-mandatory-before-wr
Sub-skill of clean-code: Step 1: API Compatibility Check (MANDATORY before writing shims) (+2).
nextflow-pipelines-step-3-run-test-profile
Sub-skill of nextflow-pipelines: Step 3: Run Test Profile.
nextflow-pipelines-step-2-select-pipeline
Sub-skill of nextflow-pipelines: Step 2: Select Pipeline.