CtrlK
BlogDocsLog inGet started
Tessl Logo

canary-deployment

Skill para rollout gradual de release com observacao continua de metricas e rollback automatico. Cobre estrategias canary (traffic-based, feature flag, blue-green), thresholds de seguranca e gatilhos de abort. Use quando precisar promover uma release ja aprovada em producao reduzindo blast radius. Trigger em: "canary", "canary deployment", "rollout gradual", "blue-green", "feature flag rollout", "progressive deployment", "gradual release", "rollback automatico", "deploy seguro".

70

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

81%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 thorough, action-oriented canary deployment runbook with explicit step sequencing, validation checkpoints, and rollback feedback loops. Its main weakness is mild verbosity and a few stack-agnostic pseudocode blocks that are not directly executable.

Suggestions

Tighten the communication template and surrounding prose in the Comunicacao section to trim tokens without losing the operational signal.

Where stack-agnostic pseudocode appears (e.g. the flag SDK block), add at least one fully executable example for a common stack so the common case is copy-paste ready.

Consider extracting the metric threshold table and rollback runbook into a references/ file to keep SKILL.md a leaner overview, signalling one-level-deep navigation.

DimensionReasoningScore

Conciseness

The body is dense and operational rather than padded with concepts Claude already knows, but the communication template and some prose around strategies could be tightened, leaving minor over-explanation.

4 / 5

Actionability

It provides concrete executable commands (kubectl apply, aws elbv2 modify-listener, flag SDK API) and a precise metric-threshold table; the pseudocode blocks are explicitly justified as stack-agnostic, so only minor gaps remain versus copy-paste-ready.

4 / 5

Workflow Clarity

The step ladder (0% -> 1% -> 10% -> 50% -> 100%) with soak times, the metric threshold table, the four rollback triggers, and the numbered rollback procedure with a dashboard-confirmation checkpoint form an explicit, validated sequence with feedback loops.

5 / 5

Progressive Disclosure

No bundle files exist, but the single-file runbook is well-organized with clear section headers and no nested references; the referenced GLOBAL.md/policies/*.md are external governance docs rather than progressive-disclosure splits of this skill, so structure is good with only minor organization gaps.

4 / 5

Total

17

/

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, well-structured description that explicitly separates what it does from when to use it and supplies a rich natural-language trigger list. The only weak spot is a slightly broad "deploy seguro" trigger and one or two mildly abstract action verbs.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete actions — "observacao continua de metricas", "rollback automatico", strategies "traffic-based, feature flag, blue-green", "thresholds de seguranca e gatilhos de abort" — but "promover uma release" stays somewhat abstract, leaving minor coverage gaps versus the comprehensive anchor.

4 / 5

Completeness

It clearly answers both what (gradual rollout with metric observation and automatic rollback, covering canary strategies and abort triggers) and when ("Use quando precisar promover uma release ja aprovada em producao reduzindo blast radius" plus a dedicated trigger phrase list).

5 / 5

Trigger Term Quality

The explicit "Trigger em:" list gives comprehensive natural-term coverage with synonyms ("canary", "canary deployment", "rollout gradual", "gradual release", "progressive deployment", "blue-green", "rollback automatico") a user would actually say.

5 / 5

Distinctiveness Conflict Risk

The canary-deployment niche is distinct with dedicated triggers, but the broad term "deploy seguro" could plausibly fire for a general deploy skill, leaving minor overlap risk with closely related 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
felvieira/claude-skills-fv
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.