CtrlK
BlogDocsLog inGet started
Tessl Logo

deployment-patterns

Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.

63

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.kiro/skills/deployment-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

Highly actionable with excellent copy-paste code, but the skill is a long monolithic document that bundles language variants and full pipeline definitions inline, and it lacks a single explicit deploy-validate-rollback feedback loop. Splitting detail into reference files and tightening would raise the score.

Suggestions

Move the per-language Dockerfiles and the full CI/CD pipeline YAML into reference files, keeping a concise overview plus one canonical example in SKILL.md.

Add one explicit sequenced deployment workflow with validation checkpoints: deploy → check /health and probes → on failure run rollback → verify recovery.

Trim inline volume by retaining a single representative Dockerfile and pointing to language-specific variants rather than embedding all three.

DimensionReasoningScore

Conciseness

The body is almost entirely executable code with little prose padding, but at ~440 lines it is voluminous — three full language-specific Dockerfiles and a complete CI/CD YAML all inline could be tightened.

2 / 3

Actionability

Copy-paste-ready Dockerfiles, GitHub Actions YAML, Kubernetes probes, TypeScript health checks, and bash rollback commands provide fully executable, specific guidance.

3 / 3

Workflow Clarity

Pipeline stages and checklists exist, but for a risky operation the core deploy→verify-health→rollback feedback loop is scattered across sections rather than presented as one explicit sequenced workflow with validation checkpoints.

2 / 3

Progressive Disclosure

The file is well-sectioned but monolithic — everything is inline with no reference files, and at ~440 lines it far exceeds the simple-skill exemption that would allow a 3 without external references.

2 / 3

Total

9

/

12

Passed

Description

85%

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: specific, complete with an explicit Use-when trigger, and clearly niched to deployment. The only weakness is a somewhat narrow trigger clause that omits common phrasings users would actually say.

Suggestions

Broaden the "Use when" clause to include natural variations such as dockerizing an app, deploying to production, rolling back a release, or setting up a CI/CD pipeline.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — "CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists" — matching the anchor for multiple specific actions.

3 / 3

Completeness

Clearly answers what it does (the capability list) and when to use it via an explicit "Use when..." clause, satisfying both halves.

3 / 3

Trigger Term Quality

Relevant domain keywords appear, but the explicit trigger ("Use when setting up deployment infrastructure or planning releases") is narrow and misses common natural variations like "dockerize", "deploy to production", or "rollback a deploy".

2 / 3

Distinctiveness Conflict Risk

A clear deployment-infrastructure niche with distinct sub-domain triggers, written in third person, unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.