CtrlK
BlogDocsLog inGet started
Tessl Logo

maintenance

Use when the user asks for a project health audit, maintenance sweep, or multi-category lead-engineer scan followed by interactive issue-by-issue resolution with user approval. Do NOT trigger on routine lint/test runs, single-file cleanups, or standard "check project" requests.

69

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured two-phase maintenance workflow with explicit validation checkpoints, feedback loops, and clean offloading of detail to subagents and reference files. It is mostly lean and actionable; some redundancy in severity rules and inlined format detail leave conciseness and progressive_disclosure at 4.

DimensionReasoningScore

Conciseness

Dense and mostly instruction-driven with little concept over-explanation, but severity rules and FR tags are restated across Rules, Steps 3-4, and Verification, adding some trimming opportunity.

4 / 5

Actionability

Provides concrete formats (issue-line and total-line shapes, accepted reply modes, named agent buckets, retry-once policy); as an instruction-only process skill the guidance is specific, with only minor gaps.

4 / 5

Workflow Clarity

Clear two-phase Scan->Resolve sequence with an explicit verification gate (Step 3), loud-failure reporting, per-finding user-approval feedback loops, and a closing verification checklist.

5 / 5

Progressive Disclosure

SKILL.md acts as an overview/index offloading per-category detail to subagents and three real one-level-deep reference files (verification-gate.md, severity-rubric.md, example-findings.md), with some format detail still inlined.

4 / 5

Total

17

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it answers both what and when, uses natural trigger terms, and adds explicit anti-triggers to avoid false activation. Minor gaps in action specificity and synonym coverage keep specificity and trigger_term_quality at 4 rather than 5.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ("project health audit, maintenance sweep, multi-category...scan", "interactive issue-by-issue resolution"), though "lead-engineer scan" leans slightly abstract, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what (multi-category scan + interactive resolution) and when (clear "Use when..." clause with concrete triggers), matching the anchor for comprehensive completeness.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ("project health audit", "maintenance sweep", "lint/test runs", "check project") but misses some synonyms like "tech debt" or "refactor sweep".

4 / 5

Distinctiveness Conflict Risk

Clear niche with explicit anti-triggers ("Do NOT trigger on routine lint/test runs, single-file cleanups, or standard 'check project' requests") minimizing conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
korchasa/flowai-plugins
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.