CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-automation-orchestrator

Use when running or scheduling periodic repository review cycles that must dispatch the correct reviewer, aggregate findings, and escalate outcomes into reports, issues, or corrective PRs across API contracts, documentation freshness, code quality, and CloudBase skill quality.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/review-automation-orchestrator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A well-organized, lean orchestrator skill with clear sequencing and mostly actionable routing guidance. The main defects are two referenced files that are missing from the bundle and some redundant repetition between the routing table and Phase 2.

Suggestions

Fix the dangling reference paths: either add `references/repo-skill-review.md` and `references/cloudbase-skill-review.md` to the bundle or reword them to clearly point at the `skill-authoring` skill's own files, so readers do not chase nonexistent paths.

Deduplicate the Routing section against Phase 2's dispatch list — one canonical routing map would remove repeated routing rows and tighten the token budget.

Add an explicit mid-workflow validation checkpoint (e.g., verify each finding is normalized with scope/severity/confidence before escalation) to convert the end-loaded self-check into per-phase feedback.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — no space is wasted explaining what reviews or PRs are, and phases are compact checklists. Minor duplication (the Routing table restates the Phase 2 dispatch list, and the skill-authoring non-duplication point is made twice) keeps it just below anchor 5.

4 / 5

Actionability

As an instruction-only skill it gives concrete, executable routing rules (finding type → named skill), explicit escalation criteria ("confirmed, mechanically fixable, and small enough"), and points to a real matrix file. It stops short of fully copy-paste-ready guidance — e.g., no example invocation of the escalation matrix or a worked finding-normalization example — so it sits at anchor 4 rather than 5.

4 / 5

Workflow Clarity

The five phases are clearly sequenced and confidence/severity gating in Phase 4 plus the closing "Minimum self-check" checklist provide real checkpoints. Validation is end-loaded rather than per-phase (there is no explicit verify step after dispatch or normalization), matching anchor 4's "most checkpoints present" rather than anchor 5's explicit feedback loops.

4 / 5

Progressive Disclosure

Structure is good — a short overview with a clearly signaled, real one-level reference (`references/escalation-matrix.md`, verified present). However, the body also cites `references/repo-skill-review.md` and `references/cloudbase-skill-review.md`, which do not exist in this skill's references directory; these dangling/ambiguous paths break navigation, pulling the score below anchor 4.

3 / 5

Total

15

/

20

Passed

Description

83%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.

A strong description that explicitly covers both what the skill does and when to use it, with concrete trigger language and a well-scoped orchestrator niche. Its main weaknesses are mild: a few missing natural synonyms and slight overlap risk with generic code-review requests.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "dispatch the correct reviewer, aggregate findings, and escalate outcomes into reports, issues, or corrective PRs" — but the single-sentence construction leaves minor gaps in coverage (e.g., configuring the recurring cycle itself is only implied). It clearly exceeds anchor 3 (only 1-2 actions) but does not fully match the comprehensive multi-action clarity of anchor 5.

4 / 5

Completeness

It explicitly answers "when" ("Use when running or scheduling periodic repository review cycles") and "what" (dispatch reviewers, aggregate findings, escalate into reports/issues/PRs) with concrete trigger phrasing. Both halves are explicit and specific, matching the anchor-5 example structure rather than the anchor-4 case where the "when" could be more specific.

5 / 5

Trigger Term Quality

Natural phrases users would say are present — "running or scheduling periodic repository review cycles", "aggregate findings", "escalate outcomes into reports, issues, or corrective PRs", plus concrete surfaces like "API contracts, documentation freshness". A few common variations (e.g., "audit", "code review", "scheduled/cron", "CI") are missing, so it falls between anchors 3 and 5 rather than fully matching anchor 5's synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

The orchestrator niche (dispatching to specialized reviewers across four named dimensions) is distinct, but "code quality" and "repository review" give minor overlap risk with generic code-review or audit skills. It is mostly distinct with minor overlap risk, not the minimal-conflict clear niche of anchor 5.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

TencentCloudBase/CloudBase-AI-Toolkit

Path

skills/review-automation-orchestrator/SKILL.md

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.