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.

57

Quality

66%

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-readiness/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 an efficient, well-structured, single-purpose instruction skill with a concrete template, explicit verdict logic, and copy-paste-ready output phrasings. It is strong across all dimensions with only minor gaps in error-recovery detail and a couple of derivable fields (slug, pr_number).

DimensionReasoningScore

Conciseness

Lean and well-sectioned with no over-explanation of concepts Claude already knows; the inline readiness-file template earns its tokens as a concrete reference, with only minor editorial padding ('This reframes the cost — completeness is cheap with AI assistance.') that could be trimmed.

4 / 5

Actionability

Provides concrete guidance: an exact file path, a complete copy-paste-ready template, explicit verdict criteria, and exact output phrasings ('Ready to merge.', 'Not ready. Missing: <list>...'); minor gaps remain around branch-slug generation and pr_number retrieval.

4 / 5

Workflow Clarity

The 'Checking readiness' section gives a clear 5-step sequence with if/else checkpoints, the verdict logic acts as a checklist, and 'After running a review skill' forms a feedback loop; not a destructive/batch operation so the 3-cap does not apply, but error-recovery for malformed/missing files is only implicit.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections (How it works, When to use, Automated updates, Verdict logic, Effort estimates) with all content appropriately inline since no external references are needed; at ~70 lines it exceeds the simple-skill 50-line threshold so the auto-5 does not fully apply, leaving minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

58%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 clearly conveys what the skill does with concrete, specific actions and a well-defined niche, but it lacks an explicit 'Use when...' trigger clause and the natural conversational phrases that would drive user-initiated activation. Adding a trigger clause with phrasings like 'Use when asked if a PR is ready to merge or ship' would raise both completeness and trigger-term quality.

Suggestions

Append an explicit 'Use when...' clause with natural user phrasings, e.g. 'Use when the user asks if a PR is ready to merge, can be shipped, or what reviews are still missing.'

Surface a few conversational trigger terms in the description itself ('can I merge', 'ready to ship') rather than only in the activation keywords.

Clarify the single most distinctive verb-phrase up front to separate it from plain code-review or CI-status skills.

DimensionReasoningScore

Specificity

Lists several concrete actions ('tracks which reviews have been completed per branch', 'gates merge decisions', 'Shows code review, tests, security, QA, and linting status') with a comprehensive 5-type status list; falls just short of 5 because the actions are display/track/gate rather than transformative operations.

4 / 5

Completeness

Clearly answers 'what' (tracks reviews per branch, gates merges, shows 5 status types) but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant domain keywords ('PR readiness', 'merge decisions', 'reviews') but omits the natural conversational phrases users actually say ('can I merge', 'is this PR ready', 'ready to ship'), which live in the activation block rather than the description.

3 / 5

Distinctiveness Conflict Risk

'PR readiness dashboard' that 'gates merge decisions' is a distinct niche with minimal conflict risk; only minor overlap with generic code-review or CI-status skills keeps it below 5.

4 / 5

Total

14

/

20

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.