CtrlK
BlogDocsLog inGet started
Tessl Logo

giuseppe-trisciuoglio/developer-kit

Comprehensive developer toolkit providing reusable skills for Java/Spring Boot, TypeScript/NestJS/React/Next.js, Python, PHP, AWS CloudFormation, AI/RAG, DevOps, and more.

89

Quality

89%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Risky

Do not use without reviewing

Overview
Quality
Evals
Security
Files

Quality

Discovery

100%

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 an excellent skill description that clearly defines its scope at the intersection of AWS ECS and GitHub Actions CI/CD. It provides comprehensive trigger terms covering the full deployment pipeline, has an explicit 'Use when' clause with detailed scenarios, and occupies a distinct niche that minimizes conflict risk. The description is thorough without being padded, and uses proper third-person voice throughout.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: building Docker images, pushing to ECR, updating ECS task definitions, deploying ECS services, integrating with CloudFormation stacks, configuring AWS OIDC authentication, blue/green deployments, ECR image scanning, and more.

3 / 3

Completeness

Clearly answers both 'what' (provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD) and 'when' (explicit 'Use when...' clause listing specific trigger scenarios like building Docker images, pushing to ECR, updating task definitions, etc.).

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'ECS', 'GitHub Actions', 'CI/CD', 'Docker images', 'ECR', 'task definitions', 'CloudFormation', 'OIDC', 'blue/green deployments', 'container deployment pipelines'. These are all terms a user working in this domain would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche combining ECS + GitHub Actions + CI/CD deployment patterns. The specificity of AWS services (ECS, ECR, CloudFormation) combined with GitHub Actions makes it very unlikely to conflict with other skills.

3 / 3

Total

12

/

12

Passed

Implementation

42%

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

The skill has good structural organization with well-signaled references to detailed materials, and the Quick Start workflow includes useful validation steps. However, it is significantly too verbose—padding with best practices lists, troubleshooting checklists, constraints, and cost considerations that Claude already knows or that belong in reference files. Several code examples are incomplete or contain errors, undermining actionability.

Suggestions

Cut the Best Practices, Common Troubleshooting, Constraints and Warnings, and Cost Considerations sections entirely—move them to the referenced best-practices.md file where they're already pointed to, keeping the SKILL.md as a lean overview.

Remove the 'Overview' and 'When to Use' sections which restate information already conveyed by the title and description.

Fix the multi-environment example to include complete matrix definitions (env_account, region values) and fix the blue/green deployment config name syntax error ('CodeDeployDefault ECSAllAtOnce' should be 'CodeDeployDefault.ECSAllAtOnce').

Replace the abstract 8-step Instructions list with either concrete commands/code for each step or remove it in favor of the Quick Start workflow which already demonstrates the process.

DimensionReasoningScore

Conciseness

Extremely verbose with extensive sections that explain concepts Claude already knows (what OIDC is, what ECR does, basic Docker concepts). The 'When to Use' section restates the description. Best practices, troubleshooting, constraints, and cost considerations are largely common knowledge padding. The 'Overview' paragraph is redundant with the title and instructions.

1 / 3

Actionability

The Quick Start workflow is mostly executable YAML, which is good. However, the multi-environment example is incomplete (matrix.env_account and matrix.region are undefined), the blue/green example has a syntax error in the deployment config name (missing dot), and the 8-step instructions in the Instructions section are abstract descriptions without concrete commands or code for steps 1-6.

2 / 3

Workflow Clarity

The Quick Start workflow includes good validation steps (image verification, task definition validation), but the high-level 8-step Instructions section lacks validation checkpoints and concrete commands. The multi-environment and blue/green examples lack error handling and verification steps. No rollback procedure is defined despite mentioning CloudFormation rollbacks in troubleshooting.

2 / 3

Progressive Disclosure

Well-structured with clear one-level-deep references to specific reference files (workflow-examples.md, authentication.md, ecr-and-task-definitions.md, deployment-strategies.md, best-practices.md). Each reference is clearly labeled with its content scope. The main file serves as an overview with appropriate detail level.

3 / 3

Total

8

/

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