Agent skill

Calibrate

by sharpdeveye in sharpdeveye/maestro

A skill your agent uses when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.

MITAuto-check passedMobile

Install Calibrate

skills CLI
$ npx skills add sharpdeveye/maestro --skill calibrate -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sharpdeveye/maestro calibrate --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sharpdeveye/maestro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/source/skills/calibrate .claude/skills/calibrate && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
calibrate
GitHub stars
592
Token cost
~782 tokens
SKILL.md length
340 words
Files
1
Skills in repo
25
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.

  • Works in 5 steps: Identify the standard: What's the most… → List deviations: Find all components… → Prioritize: Fix the most impactful… → …
  • Workflow components are inconsistent
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Naming conventions vary

What it does

Calibrate is an agent skill from sharpdeveye/maestro. Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.

Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Mobile. The repository describes itself as: Workflow fluency for AI coding agents. 1 core skill · 25 commands · 7 domain references · memory layer · audit trail — works across Cursor, Claude Code, Gemini CLI, Copilot, and… The licence is MIT.

When your agent uses it

  • Workflow components are inconsistent
  • Naming conventions vary
  • A new team members work needs alignment to project standards

Example prompts

  • “/calibrate”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  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.

What it can do on your machine

Read from SKILL.md and the folder at commit 00f9115. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Calibrate loads about 782 tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 340 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~37
When it runs · the whole SKILL.md, loaded when a task matches
~782

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sharpdeveye/maestro at commit 00f9115, republished under its MIT licence (© sharpdeveye). 340 words, ~782 tokens.

Download SKILL.mdSave it as .claude/skills/calibrate/SKILL.md (or your agent's skills folder).
name
calibrate
description
Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.
argument-hint
[target area]
category
fix
version
2.0.0
user-invocable
true

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
DimensionStandardDeviations FoundPriority
Tool naming?? of ? toolsHigh/Med/Low
Prompt structure?? of ? promptsHigh/Med/Low
Error format?? of ? toolsHigh/Med/Low
Log format?? of ? entriesHigh/Med/Low
Calibration Checklist
  • Convention standard identified for each dimension
  • All deviations listed with location
  • Highest impact deviations fixed first
  • Tests pass after each calibration change
  • Updated .maestro.md with established conventions

After calibration, run /refine for a final polish pass, or /evaluate to verify consistency improvements.

NEVER:

  • Invent new conventions when existing ones work
  • Calibrate in a way that changes behavior (this is standardization, not refactoring)
  • Skip test verification after calibration
  • Change naming conventions without updating all references

© sharpdeveye, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in source/skills/calibrate of sharpdeveye/maestro.

Open the folder on GitHubat commit 00f9115

Compare with similar skills

Calibrate next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Calibrate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Calibrate this skillsharpdeveye/maestro592—~782Automated safety check: PassMIT
React Native Best Practicesvercel-labs/openreview1.7k17 repos~1.1kAutomated safety check: PassMIT
Swiftui Protwostraws/SwiftUI-Agent-Skill5.1k2 repos~1.5kAutomated safety check: PassMIT
Kortix Brandkortix-ai/suna20k—~4kAutomated safety check: PassCustom licence
Ip As LogoKartikLabhshetwar/better-shot2.4k1 repos~4.3kAutomated safety check: PassMIT
Compose Multiplatform Patternsmonta-app/ocpp-emulator1805 repos~2kAutomated safety check: PassApache-2.0

Similar skills

  • React Native Best Practices

    vercel-labs/openreview

    Official

    A prioritized rule set for React Native and Expo apps covering list performance, animation, navigation, UI patterns, state, rendering, monorepos and configuration.

    1.7k GitHub starsUsed in 17 repos~1.1k tokens
    MobileAuto-check passed
  • Swiftui Pro

    twostraws/SwiftUI-Agent-Skill

    Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance.

    5.1k GitHub starsUsed in 2 repos~1.5k tokens
    MobileAuto-check passed
  • Kortix Brand

    kortix-ai/suna

    Load FIRST for anything that carries the Kortix look or voice: product or mobile UI, copy of any kind, decks, social, images, email, CLI output, anything with the logo, and reviews of these.

    20k GitHub stars~4k tokensUpdated today
    MobileAuto-check passed
  • Ip As Logo

    KartikLabhshetwar/better-shot

    Generate extremely simple, cute, personified square character images with rounded heavy forms, two purposeful character colors, one solid background color, and a dominant lower-corner composition.

    2.4k GitHub starsUsed in 1 repo~4.3k tokens
    MobileAuto-check passed
  • Compose Multiplatform Patterns

    monta-app/ocpp-emulator

    Compose Multiplatform and Jetpack Compose patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI.

    180 GitHub starsUsed in 5 repos~2k tokens
    MobileAuto-check passed
  • Aso Appstore Screenshots

    adamlyttleapps/claude-skill-aso-appstore-screenshots

    Generate high-converting App Store screenshots by analyzing your app's codebase, discovering core benefits, and creating ASO-optimized screenshot images using Nano Banana Pro.

    1.8k GitHub starsUsed in 1 repo~9.6k tokens
    MobileAuto-check passed

More from sharpdeveye/maestro

All 25 skills in this repo
  • Accelerate

    sharpdeveye/maestro

    A skill your agent uses when the workflow is too slow, too expensive, or both and needs latency, cost, or token usage optimization.

    592 GitHub stars~745 tokensUpdated 5 mo ago
    Auto-check passed
  • Chain

    sharpdeveye/maestro

    A skill your agent uses when the workflow needs multi-step processing with sequential, parallel, or conditional tool compositions and proper data flow.

    592 GitHub stars~607 tokensUpdated 5 mo ago
    Auto-check passed
  • Compose

    sharpdeveye/maestro

    A skill your agent uses when a single agent demonstrably cannot handle the task and multi-agent coordination is justified.

    592 GitHub stars~720 tokensUpdated 5 mo ago
    Auto-check passed
  • Diagnose

    sharpdeveye/maestro

    A skill your agent uses when the user wants to find problems, audit workflow quality, or get a comprehensive health check on their AI workflow.

    592 GitHub stars~1.5k tokensUpdated 5 mo ago
    Auto-check passed
  • Extract Pattern

    sharpdeveye/maestro

    A skill your agent uses when the user wants to create templates, extract reusable patterns, document solutions, or build a pattern library from working workflows.

    592 GitHub stars~664 tokensUpdated 5 mo ago
    Auto-check passed
  • Fortify

    sharpdeveye/maestro

    A skill your agent uses when the workflow lacks error handling, has been failing in production, or needs retry logic, fallback strategies, and circuit breakers.

    592 GitHub stars~688 tokensUpdated 5 mo ago
    Auto-check passed

Categories

Questions about Calibrate

What does Calibrate do?

A skill your agent uses when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards. Calibrate is an agent skill from sharpdeveye/maestro. Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.

When should I use Calibrate?

Calibrate fits situations like: workflow components are inconsistent; naming conventions vary; A new team members work needs alignment to project standards.

How do I install Calibrate in Claude Code?

Run `npx skills add sharpdeveye/maestro --skill calibrate -a claude-code`. Or copy the skill folder (source/skills/calibrate in sharpdeveye/maestro) into .claude/skills/calibrate in your project. Claude Code loads it when a task matches its description.

How do I install Calibrate in Codex?

Run `npx skills add sharpdeveye/maestro --skill calibrate -a codex`. Or copy the skill folder (source/skills/calibrate in sharpdeveye/maestro) into .agents/skills/calibrate in your project. Codex loads it when a task matches its description.

Can I use Calibrate in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sharpdeveye/maestro --skill calibrate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/calibrate, .gemini/skills/calibrate, .github/skills/calibrate and .opencode/skills/calibrate in your project.

What does Calibrate need to run?

SKILL.md names no scripts, command-line tools or credentials: Calibrate is instructions for the agent only.

Does Calibrate access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Calibrate safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Calibrate use?

Calibrate is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Calibrate use?

About 782 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Calibrate?

Skills that share tags, products or a category with Calibrate: React Native Best Practices (vercel-labs/openreview, 1.7k stars), Swiftui Pro (twostraws/SwiftUI-Agent-Skill, 5.1k stars), Kortix Brand (kortix-ai/suna, 20k stars) and Ip As Logo (KartikLabhshetwar/better-shot, 2.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Calibrate?

sharpdeveye (a GitHub user) maintains it in sharpdeveye/maestro, which has 592 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on April 29, 2026.

Source: sharpdeveye/maestro on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.