CtrlK
BlogDocsLog inGet started
Tessl Logo

review-readiness

PR readiness dashboard — tracks which reviews have been completed per branch and gates merge decisions. Shows code review, tests, security, QA, and linting status.

68

Quality

83%

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

100%

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

The content is well-structured, lean, and highly actionable, with a concrete file format, explicit workflows, and clear verdict logic, all appropriately self-contained without needing external references.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it provides a concrete readiness-file template and exact phrasings without explaining what PRs, CI, or reviews are, with only minor editorializing in 'Effort estimates'.

3 / 3

Actionability

It gives a concrete file path convention, a complete copy-paste-ready readiness-file example with frontmatter and status table, exact response strings, and explicit verdict criteria — fully executable guidance.

3 / 3

Workflow Clarity

The 'Checking readiness' flow is a numbered 5-step sequence with an explicit decision branch (all passed vs. missing), and the verdict logic supplies concrete validation criteria (READY/ALMOST/NOT READY/BLOCKED) as checkpoints; the task is not destructive/batch so no extra feedback loop is required.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the ~70-line body is self-contained and organized into clear sections with no nested references, satisfying the simple-skill allowance for well-organized single-file content.

3 / 3

Total

12

/

12

Passed

Description

67%

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 specific and occupies a distinct niche, but it omits an explicit 'Use when...' trigger clause and relies on the activation block for natural trigger terms, which caps its completeness and trigger-term quality at 2.

Suggestions

Add an explicit trigger clause to the description, e.g. 'Use when the user asks whether a PR is ready to merge, or wants a readiness/merge checklist per branch.'

Surface natural user phrasings directly in the description ('can I merge', 'ready to ship', 'PR status') instead of only in the activation keywords, to improve trigger-term coverage.

Keep the enumerated check list but lead with the trigger context so 'when to use' precedes the capability detail.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('tracks which reviews have been completed per branch', 'gates merge decisions') and enumerates the specific check types (code review, tests, security, QA, linting), matching the multi-action anchor rather than the domain-only level 2.

3 / 3

Completeness

The 'what' is explicit, but there is no 'Use when...' clause or equivalent trigger guidance inside the description field; per the rubric guideline a missing explicit trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

The field contains natural terms like 'PR readiness' and 'merge', but common user variations such as 'can I merge', 'ready to ship', and 'PR status' appear only in the activation block, not the description itself, so coverage is partial rather than comprehensive.

2 / 3

Distinctiveness Conflict Risk

It carves a clear niche as a readiness-tracking / merge-gating meta-layer over the underlying review skills, so it is unlikely to be triggered in place of /security-review or /qa-review rather than above the overlapping-but-different level 2.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
nearai/ironclaw
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.