CtrlK
BlogDocsLog inGet started
Tessl Logo

analyzing-release-readiness

Trigger a pre-merge release readiness review on a GitHub PR, GitLab MR, or local branch. Use when the user wants to analyze code changes for risk, correctness, and potential rollback issues before merging. Trigger words include release readiness, analyze PR, analyze MR, review PR, risk analysis, pre-merge, safe to ship, ready to merge, ready to commit, any risks, before merging, validate changes, release management.

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

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable and clearly sequenced with strong validation checkpoints for its destructive git operations. The main weaknesses are verbosity from repeated emphasis and a monolithic structure that would benefit from splitting the fallback and local-git details into reference files.

Suggestions

Reduce repeated emphasis directives ('MANDATORY', 'Do NOT proceed until the user approves', 'NEVER use gh CLI') by stating each rule once in a prominent callout rather than restating per step.

Extract the fallback (aws-mcp) CLI section and the detailed local-repo git procedure into separate reference files (e.g., references/fallback.md, references/local-repo-flow.md) and link to them one level deep to improve progressive disclosure.

Condense the verbatim user-facing prompt strings into shorter templates or a shared phrasing table to trim token usage without losing the approval-gate intent.

DimensionReasoningScore

Conciseness

Mostly efficient actionable instructions, but padded with repeated emphasis ('MANDATORY', 'Do NOT proceed until the user approves', 'NEVER use gh CLI') and long verbatim user-facing prompt strings that could be tightened.

3 / 5

Actionability

Fully executable guidance with exact bash commands, concrete JSON payloads, precise tool-call signatures, and specific polling intervals (30s/15s) covering GitHub PR, GitLab MR, local repo, and fallback paths.

5 / 5

Workflow Clarity

Clear strictly-numbered sequence with explicit validation checkpoints (sensitive-file scan, branch verification before push, tool-availability check, user approval gates) and error-handling feedback loops for recovery.

5 / 5

Progressive Disclosure

Well-sectioned with headers and a decision tree, but the ~400-line document is monolithic with no bundle files; the fallback aws-mcp path and detailed local-git procedures are inlined rather than split into one-level-deep reference files.

3 / 5

Total

16

/

20

Passed

Description

91%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 clearly states both purpose and trigger conditions with comprehensive natural keywords in third-person voice. The only weakness is slight overlap risk from a few generic review-related trigger terms.

DimensionReasoningScore

Specificity

Names the domain (GitHub PR, GitLab MR, local branch) and several concrete actions ('trigger a pre-merge release readiness review', 'analyze code changes for risk, correctness, and potential rollback issues'), with only minor gaps in coverage.

4 / 5

Completeness

Explicitly answers both 'what' (trigger a release readiness review analyzing risk/correctness/rollback) and 'when' ('Use when the user wants to analyze code changes... before merging') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Provides comprehensive natural trigger phrases users would actually say ('release readiness', 'analyze PR', 'safe to ship', 'ready to merge', 'before merging', 'validate changes') including synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (pre-merge release readiness) with distinct triggers, though generic phrases like 'review PR' and 'analyze PR' carry minor overlap risk with general code-review skills.

4 / 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
aws/agent-toolkit-for-aws
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.