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 a strong skill description that thoroughly covers specific capabilities, includes abundant natural trigger terms, explicitly addresses both what and when, and occupies a clearly distinct niche. The only minor weakness is that the description is quite long and could potentially be more concise, but the verbosity serves the purpose of comprehensive trigger term coverage without being padded with fluff.

DimensionReasoningScore

Specificity

The description lists numerous specific concrete actions and capabilities: ECS clusters, task definitions, services, container definitions, auto scaling, blue/green deployments, CodeDeploy integration, ALB integration, service discovery, monitoring, logging, template structure, parameters, outputs, and cross-stack references.

3 / 3

Completeness

Clearly answers both 'what' (provides AWS CloudFormation patterns for ECS clusters, task definitions, etc.) and 'when' (explicit 'Use when' clause covering creating ECS clusters with CloudFormation, configuring Fargate, implementing blue/green deployments, etc.).

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'CloudFormation', 'ECS', 'Fargate', 'EC2 launch types', 'blue/green deployments', 'auto scaling', 'ALB', 'NLB', 'task definitions', 'service discovery'. These are all terms a user would naturally use when seeking help with AWS ECS infrastructure.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche combining AWS CloudFormation specifically with ECS. The combination of CloudFormation + ECS + specific features like blue/green deployments and CodeDeploy integration makes it very unlikely to conflict with other skills.

3 / 3

Total

12

/

12

Passed

Implementation

64%

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

This is a solid, actionable skill with executable CloudFormation YAML patterns covering the core ECS use cases. Its main weaknesses are verbosity (the inline content is extensive when some could be offloaded to reference files) and incomplete workflow feedback loops for error recovery during deployment. The best practices and constraints sections add genuine value but contribute to the overall length.

Suggestions

Move the Best Practices, Constraints/Warnings, and additional examples into separate reference files (e.g., references/best-practices.md, references/examples.md) to keep the main skill leaner and improve progressive disclosure.

Add an explicit error recovery workflow: check stack events on failure (`aws cloudformation describe-stack-events`), rollback procedures, and how to diagnose common ECS deployment failures.

Trim the Parameters block to show only 2-3 representative values with a comment indicating the full range, and remove the Related Resources section of external AWS docs which Claude already knows about.

DimensionReasoningScore

Conciseness

The skill is quite long (~300+ lines) with some redundancy between the step-by-step instructions and the examples section. The Parameters block listing all allowed memory values is verbose, and the 'Related Resources' section with 8 external AWS doc links adds little value for Claude. However, the YAML snippets themselves are lean and the best practices section is efficiently written.

2 / 3

Actionability

All code examples are fully executable CloudFormation YAML with correct resource types, properties, and intrinsic functions. The examples are copy-paste ready, including a complete minimal Fargate service template and ALB integration pattern. CLI commands for validation and change sets are also concrete.

3 / 3

Workflow Clarity

The 8-step sequence is clearly ordered and includes two validation checkpoints (template validation after step 3 and change set preview before deployment). However, there's no explicit error recovery loop (e.g., what to do if deployment fails, how to check stack events, rollback procedures). For CloudFormation operations which are destructive/batch in nature, the missing feedback loops cap this at 2.

2 / 3

Progressive Disclosure

There is a reference to constraints.md for detailed limits, which is good progressive disclosure. However, the main body contains substantial inline content (best practices, constraints/warnings, multiple examples) that could be split into separate reference files. The skill tries to be both a quick-start guide and a comprehensive reference, making it harder to navigate.

2 / 3

Total

9

/

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