無料GitHub で公開

calibrate

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

日本語の概要は準備中です。原文の説明を表示しています。

sharpdeveye/maestroスター 591(GitHub 591 + cccskills 0)

実行スコア未検証

インストール方法を見る

含まれるファイル（1）

SKILL.md3.1 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

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

Consistency Audit Table

Dimension	Standard	Deviations Found	Priority
Tool naming	?	? of ? tools	High/Med/Low
Prompt structure	?	? of ? prompts	High/Med/Low
Error format	?	? of ? tools	High/Med/Low
Log format	?	? of ? entries	High/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

Recommended Next Step

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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

同じリポジトリのスキル

accelerate

無料

Use when the workflow is too slow, too expensive, or both and needs latency, cost, or token usage optimization.

日本語の概要は準備中です。原文の説明を表示しています。