Skip to content
cccskills
FreePublished on GitHub

refine

Use when the workflow works but needs polish, or as the final step in a diagnose → fix → refine cycle before shipping.

The English summary is being prepared. Showing the original description.

sharpdeveye/maestro591 stars(GitHub 591 + cccskills 0)

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.


This is the final quality pass. The workflow works — now make it excellent.

Refinement Checklist

Prompts

  • Every prompt follows the 4-zone pattern (role, context, instructions, output)
  • Output schemas are explicit and validated
  • Negative instructions clarify what NOT to do
  • No contradictory instructions
  • Few-shot examples included for ambiguous tasks
  • Chain-of-thought used for multi-step reasoning tasks

Tool Descriptions

  • Every tool has a multi-line description: what, when to use, when NOT to use, returns
  • Input parameters have descriptions and types
  • Error responses are documented
  • At least one example input/output in the description

Error Messages

  • Error messages are specific (not "an error occurred")
  • Error messages suggest corrective action
  • Errors include context (what was being attempted)
  • Errors are structured (code + message + details)

Logging

  • Every model call is logged (input tokens, output tokens, latency, cost)
  • Tool calls are logged with inputs and outputs
  • Errors are logged with full context
  • PII is redacted from logs
  • Workflow ID traces through all log entries

Configuration

  • All magic numbers are named constants
  • Environment-specific values are in config, not code
  • Defaults are sensible — config is for overrides
  • Cost ceilings are set
  • Timeout values are set for all external calls

Output

For each checklist item that fails, provide:

  1. What's wrong (specific finding)
  2. Where it is (file, line, or component)
  3. How to fix it (concrete suggestion)
  4. Priority (critical / important / nice-to-have)

Priority Matrix

PriorityCriteriaMaestro Action
CriticalAffects correctness or safety/fortify or /guard before shipping
ImportantAffects quality or maintainability/calibrate in current cycle
Nice-to-haveCosmetic or minor inconsistencyNote for next /refine pass

Recommended Next Step

After refinement is complete, run /evaluate to verify the polished workflow against realistic scenarios.

NEVER:

  • Skip the checklist — go through every item
  • Mark items as passing without checking
  • Suggest changes that alter behavior (this is polish, not redesign)
  • Refine before the workflow is functionally correct (fix first, refine last)

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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

The English summary is being prepared. Showing the original description.

sharpdeveye/maestro591Updated Apr 29, 2026

Use when porting a workflow to a different AI provider, deployment environment, model tier, or organizational context.

The English summary is being prepared. Showing the original description.

sharpdeveye/maestro591Updated Apr 29, 2026

Use when any Maestro command is invoked — provides foundational workflow design principles across prompt engineering, context management, tool orchestration, agent architecture, feedback loops, knowledge systems, and guardrails.

The English summary is being prepared. Showing the original description.

sharpdeveye/maestro591Updated Apr 29, 2026

Use when the workflow works but needs to handle more complex cases or produce higher-quality output through better tools, context, prompts, or models.

The English summary is being prepared. Showing the original description.

sharpdeveye/maestro591Updated Apr 29, 2026

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

The English summary is being prepared. Showing the original description.

sharpdeveye/maestro591Updated Apr 29, 2026

Capture a session summary — what was done, what decisions were made, and what to do next.

The English summary is being prepared. Showing the original description.

sharpdeveye/maestro591Updated Apr 29, 2026

See all skills by sharpdeveye

Report a problem with this skill