# Calibrate

Use when workflow components are inconsistent, naming conventions vary, or a new team...

- Repository: https://github.com/sharpdeveye/maestro (592 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-04-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add sharpdeveye/maestro --skill calibrate -g -a claude-code -y`
Codex: `npx skills add sharpdeveye/maestro --skill calibrate -g -a codex -y`
Cursor: `npx skills add sharpdeveye/maestro --skill calibrate -g -a cursor -y`
Gemini CLI: `npx skills add sharpdeveye/maestro --skill calibrate -g -a gemini-cli -y`

## Description

Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## MANDATORY PREPARATION

Invoke /agent-workflow, it contains workflow principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding, if no workflow context exists yet, you MUST run /teach-maestro first.
Consult the prompt-engineering reference in the agent-workflow skill for naming and style consistency patterns.


---

Ensure consistency across all workflow components. Inconsistency creates confusion, for the model, for developers, and for users.

### Calibration Dimensions

**Naming Conventions**

- Tool names follow consistent pattern (verb_noun, noun.verb, or camelCase, pick one)
- Agent names follow consistent pattern
- Configuration keys follow consistent pattern
- File names follow consistent pattern

**Prompt Style**

- All prompts use the same structural pattern (4-zone)
- Consistent delimiter style (XML tags, markdown headers, triple-dash)
- Consistent output schema format (JSON schema, markdown template)
- Consistent instruction style (imperative, numbered steps)

**Error Handling**

- All tools return errors in the same format
- Error codes follow consistent scheme
- Error messages follow consistent tone
- Retry logic uses consistent strategy

**Logging**

- All logs use the same format (JSON structured, text, etc.)
- Consistent field names across all log entries
- Consistent log levels (debug, info, warn, error)
- Consistent PII redaction approach

### Calibration Process

1. **Identify the standard**: What's the most common pattern in the existing codebase? That's the standard.
2. **List deviations**: Find all components that deviate from the standard.
3. **Prioritize**: Fix the most impactful deviations first (user-facing > internal).
4. **Apply**: Make the changes, ensuring tests still pass.
5. **Document**: Update `.maestro.md` with the established conventions.

### Consistency Audit Table

The rest: https://github.com/sharpdeveye/maestro/blob/HEAD/source/skills/calibrate/SKILL.md