CtrlK
BlogDocsLog inGet started
Tessl Logo

devops-deployer

DevOps Deployer Agent. 배포, 롤백, 릴리즈 관리를 담당합니다. 배포(deploy), 롤백(rollback), 릴리즈, Blue-Green 관련 요청 시 사용됩니다.

Install with Tessl CLI

npx tessl i github:shaul1991/shaul-agents-plugin --skill devops-deployer
What are skills?

83

Quality

81%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/devops-deployer/SKILL.md
SKILL.md
Review
Evals

Discovery

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid skill description that effectively communicates its deployment-focused purpose with good trigger terms in both Korean and English. The explicit 'Use when' clause with specific keywords makes it easy for Claude to select appropriately. The main weakness is that the capability description could be more specific about concrete actions beyond general deployment/rollback/release management.

Suggestions

Add more specific concrete actions such as 'execute deployment pipelines', 'manage Kubernetes deployments', 'configure environment variables', or 'monitor deployment health' to improve specificity.

DimensionReasoningScore

Specificity

Names the domain (DevOps/deployment) and lists some actions (배포/deploy, 롤백/rollback, 릴리즈 관리/release management), but lacks specific concrete actions like 'execute deployment scripts', 'manage container orchestration', or 'configure CI/CD pipelines'.

2 / 3

Completeness

Clearly answers both what ('배포, 롤백, 릴리즈 관리를 담당합니다') and when ('배포(deploy), 롤백(rollback), 릴리즈, Blue-Green 관련 요청 시 사용됩니다') with explicit trigger guidance using '사용됩니다' (Use when) clause.

3 / 3

Trigger Term Quality

Includes good coverage of natural terms users would say: 배포(deploy), 롤백(rollback), 릴리즈, Blue-Green. Provides both Korean and English terms which helps with bilingual trigger matching.

3 / 3

Distinctiveness Conflict Risk

Clear niche focused on deployment operations with distinct triggers (deploy, rollback, release, Blue-Green). Unlikely to conflict with other skills as it targets a specific DevOps domain with specialized terminology.

3 / 3

Total

11

/

12

Passed

Implementation

72%

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

This is a well-structured deployment skill with good conciseness and organization. The main weaknesses are incomplete actionability for rollback operations (described but not executable) and missing error recovery workflows for when deployments or health checks fail.

Suggestions

Add executable rollback commands (e.g., specific docker/caddy commands to switch traffic back to previous slot)

Add error recovery steps: what to do if health check fails after 30 attempts, how to manually intervene

Include specific command for rollback to a particular image version, not just description

DimensionReasoningScore

Conciseness

Content is lean and efficient with no unnecessary explanations. Every section serves a purpose - tables, commands, and checklists are all actionable without padding.

3 / 3

Actionability

Provides concrete commands for deployment and slot checking, but rollback section is vague ('이전 슬롯으로 트래픽 전환') without actual executable commands. Missing specific rollback commands.

2 / 3

Workflow Clarity

Deployment process has clear 5-step sequence, but lacks explicit validation/error recovery steps. Checklists are present but no feedback loops for what to do if health checks fail or how to actually perform rollback.

2 / 3

Progressive Disclosure

For a skill of this size (~60 lines), content is well-organized with clear sections. No need for external references given the scope. Tables and code blocks are appropriately used for different content types.

3 / 3

Total

10

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

10

/

11

Passed

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.