Skip to content
Skills Library
Management & product · Review & audit

evaluate

/evaluate

Use when the user wants a quality review, interaction audit, or to test the workflow against realistic scenarios.

Repository
maestro ↗
Licence
MIT
Last repository change
29.04.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 29.04.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when the user wants a quality review, interaction audit, or to test the workflow against realistic scenarios.

Arguments

/evaluate [workflow or scenario]
Original author description

Use when the user wants a quality review, interaction audit, or to test the workflow against realistic scenarios.

How it works

  1. MANDATORY PREPARATION
Original SKILL.md headings · 84 lines, 450 words
SKILL.md preview
---
name: evaluate
description: "Use when the user wants a quality review, interaction audit, or to test the workflow against realistic scenarios."
argument-hint: "[workflow or scenario]"
category: analysis
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 feedback-loops reference in the agent-workflow skill for evaluation patterns, golden test sets, and regression detection.

---

Evaluate the workflow's actual interaction quality by testing it against scenarios that represent real usage.

### Evaluation Dimensions

**1. Task Completion**

- Does the workflow actually accomplish what it's supposed to?
- Does it handle the complete task or only the happy path?
- Are edge cases addressed or silently dropped?

**2. Output Quality**

- Is the output accurate, complete, and well-formatted?
- Does it match the defined output schema (if any)?
- Would a domain expert approve the output?

**3. Error Behavior**

- What happens when input is malformed?
- What happens when a tool fails?
- What happens when the model is uncertain?
- Is the error message useful or generic?

**4. User Experience**

- Is the interaction natural and intuitive?
- Are confirmations requested for destructive operations?
- Is the response time acceptable?
- Does the workflow communicate its limitations?

**5. Consistency**

- Does the same input produce consistent output quality?
- Are there random failures that aren't reproducible?
- Does quality degrade over long conversations?

### Scenario Testing

Create and run test scenarios:

| Scenario | Input | Expected | Actual | Grade |
|----------|-------|----------|--------|-------|
| Happy path | Normal input | Correct output | ? | A-F |
| Edge case | Unusual input | Graceful handling | ? | A-F |
| Error case | Bad input | Helpful error | ? | A-F |
| Stress case | Large/complex input | Reasonable handling | ? | A-F |
| Adversarial | Tricky/malicious input | Safe response | ? | A-F |

### Evaluation Report

Produce a structured report with:

1. Overall quality grade (A-F)
2. Per-dimension scores with evidence
3. Specific scenario results
4. Priority improvements with recommended Maestro commands

### Evaluation Checklist

- [ ] All 5 dimensions tested with concrete scenarios
- [ ] At least one edge case and one adversarial case tested
- [ ] Results documented in the scenario table
- [ ] Overall grade assigned with justification
- [ ] Improvement actions reference specific Maestro commands

### Recommended Next Step

After evaluation, run `/fortify` to address error behavior gaps, `/refine` for output quality improvements, or `/iterate` to set up continuous quality monitoring.

**NEVER**:

- Evaluate theoretically — run actual scenarios
- Give an A grade unless the workflow handles all scenario types well
- Skip adversarial testing for user-facing workflows
- Evaluate only the happy path

Versions

RepositoryScoreLicence
This page · sharpdeveye/maestro100MIT
skillberry-ai/cap-evolve100Apache-2.0
q00/ouroboros100MIT
ghaida/intent100CC0-1.0
manykind-ai/plugin100MIT
nexadevapp/nexa-claude-skills-marketplace100Apache-2.0
minhuw/claude-writer100MIT
suboss87/FDEOps90MIT

Database snapshot: 13.11.2026 · package version fac615df07dc (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100skill-improve
    Evaluate and improve existing agent skills using observed failures and realistic task scenarios. Use for auditing skill behavior and instructions rather than creating a new skill from scratch.
  • 100evaluate-skill
    Evaluate an Agent Skill's routing, execution quality, reliability, composition, and incremental value with isolated realistic cases and evidence. Use when deciding readiness, investigating missed or false triggers, comparing skill versions, or hardening a skill after observed failures.
  • 100code-review-specialist
    Comprehensive code review with security, performance, and quality analysis. Use when users ask to review code, analyze code quality, evaluate pull requests, or mention code review, security analysis, or performance optimization.
  • 90ui-ux-designer
    Use when user experience, visual flow, interaction quality, or interface coherence needs a dedicated design-oriented pass.
  • 90ui-ux-designer
    Use when user experience, visual flow, interaction quality, or interface coherence needs a dedicated design-oriented pass.
  • 100evaluate-prompt-management
    Evaluate Prompt Management — audit prompt quality scores, injection resilience, version hygiene, A/B test significance, template compliance. Use when: evaluate, audit prompt quality.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.