CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

release-readiness-review

Reviews build validation, linting/type-checking, target database checks, clinical governance preflight approvals, and environment variables. Use before staging or production releases.

Quality

86%

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

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

An exemplary lean, operational skill body: exact commands with precise approval and safety conditions, no concept padding, and clean delegation to canonical repo documents. The only notable gap is the absence of failure-handling guidance and an explicit cross-section execution order in the review workflow.

DimensionReasoningScore

Conciseness

The ~22-line body is dense and purely operational ("Run lint or typecheck only when the changed paths can plausibly fail that contract", "never edit the frozen `docs/branch-review-ledger.md` table") with zero concept explanation, delegating detail to canonical repo docs instead of restating it. Every token earns its place, matching the score-5 anchor; the only near-repetition (two links to verification-gates.md) serves distinct contexts and does not constitute padding.

5 / 5

Actionability

Five exact, copy-paste-ready commands are given (`npm run verify:pr-local`, `npm run verify:release`, `npm run check:supabase-project`, `npm run check:production-readiness:ci`, `npm run check:production-readiness`) with concrete execution conditions — approval requirements, no secrets printed, and the exact target ref `sjrfecxgysukkwxsowpy`. This matches the score-5 anchor of fully executable commands covering the common cases, well above the score-4 anchor's "minor gaps".

5 / 5

Workflow Clarity

The protocol-then-checklist structure is clearly organized into numbered sections with explicit gating checkpoints ("requires user approval because it includes provider-backed checks", "Pending release approvals block release or activation"), matching score 4. It falls short of score 5 because execution order across the sections is implicit and there is no error-recovery guidance (what to do when a check or approval fails); it stays above score 3 since checkpoints are explicit rather than missing.

4 / 5

Progressive Disclosure

No bundle files exist, and this sub-50-line skill needs none: it is well-organized into headed sections and delegates detail via clearly signaled, one-level-deep links to canonical repo docs (AGENTS.md, verification-gates.md, codex-review-protocol.md, pull_request_template.md) with no nested reference chains. Under the simple-skill guidance this matches the score-5 anchor of a clear overview with easy navigation.

5 / 5

Total

19

/

20

Passed

Description

75%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 solid third-person description that states concrete capabilities and an explicit use condition, well above the vague bad examples. It stops short of top marks on trigger coverage and completeness because it lacks user-mention synonyms (deploy, go-live) and phrased triggers.

Suggestions

Add natural trigger synonyms such as "deploy", "deployment", "go-live", or "ship" to the when-clause (e.g., "Use before staging or production releases, deployments, or go-live checks").

Make the "when" clause user-utterance oriented, e.g., "Use when the user asks to verify release readiness or approve a production release".

Clarify the action taken on each target, e.g., "validates required environment variables" instead of the bare "environment variables".

DimensionReasoningScore

Specificity

"Reviews build validation, linting/type-checking, target database checks, clinical governance preflight approvals, and environment variables" names several concrete review targets, but each item names an area rather than the action performed on it, leaving minor coverage gaps (e.g., what is done with environment variables). It lists more specific actions than the score-3 anchor yet is not the comprehensive coverage of the score-5 anchor.

4 / 5

Completeness

The "what" is explicit (reviews the five listed areas) and the "when" is present ("Use before staging or production releases"), matching the score-4 anchor where both exist but the when-clause could be more specific. It falls short of score 5 because the when-clause is a temporal condition rather than concrete user-utterance trigger phrases like "when the user mentions deployments or go-live".

4 / 5

Trigger Term Quality

"Use before staging or production releases" plus "linting", "type-checking", "preflight approvals" are natural terms users would say, but common synonyms like "deploy", "deployment", "go-live", or "ship" are missing. Good coverage per the score-4 anchor, short of the comprehensive synonym coverage of score 5.

4 / 5

Distinctiveness Conflict Risk

The clinical-governance and target-database framing carves a mostly distinct niche, and the release-scoped when-clause narrows triggering, but "reviews build validation, linting/type-checking" overlaps with generic code-review/CI skills. Mostly distinct with minor overlap risk, matching score 4 rather than the minimal-conflict score 5.

4 / 5

Total

16

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository

BigSimmo/PsychSift

Path

.cursor/skills/release-readiness-review/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.