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

92%

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 description that clearly identifies its niche at the intersection of AWS CloudFormation and CloudWatch monitoring. It provides extensive specific trigger terms and an explicit 'Use when' clause. The main weakness is that including generic CloudFormation template structure elements (Parameters, Outputs, Mappings, Conditions) could cause overlap with other CloudFormation skills, and the description is somewhat long, which slightly dilutes focus.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and resources: CloudWatch metrics, alarms, dashboards, log groups, log subscriptions, anomaly detection, synthesized canaries, Application Signals, plus CloudFormation template structure elements like Parameters, Outputs, Mappings, Conditions, and cross-stack references.

3 / 3

Completeness

Clearly answers both 'what' (provides AWS CloudFormation patterns for CloudWatch monitoring resources) and 'when' (explicit 'Use when' clause listing specific trigger scenarios like creating alarms, dashboards, log groups, etc.).

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'CloudWatch', 'alarms', 'dashboards', 'log groups', 'metrics', 'monitoring', 'CloudFormation', 'canaries', 'anomaly detection', 'observability'. These are terms AWS users would naturally use when requesting help.

3 / 3

Distinctiveness Conflict Risk

While the CloudWatch + CloudFormation combination is fairly specific, the inclusion of generic CloudFormation template structure elements (Parameters, Outputs, Mappings, Conditions) could cause overlap with other CloudFormation-focused skills. The monitoring/observability niche is clear, but the template structure terms broaden the scope and increase conflict risk.

2 / 3

Total

11

/

12

Passed

Implementation

62%

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

The skill provides excellent actionable CloudFormation templates and a well-structured workflow with proper validation steps. However, it is significantly too verbose—the bottom half of the document contains extensive best-practice bullet lists that are highly redundant with each other and with content likely in the referenced files. Trimming the duplicated advisory sections would dramatically improve token efficiency without losing any practical value.

Suggestions

Remove or drastically condense the 'Monitoring Strategy', 'Log Management', 'Alarm Configuration', 'Template Structure', and 'Dashboard Design' subsections—they heavily overlap with 'Best Practices' and with the referenced detail files (alarms.md, dashboards.md, logs.md, constraints.md).

Consolidate 'Best Practices' into 5-6 key bullets maximum, deferring detailed guidance to the reference files where it belongs.

Remove the 'Related Resources' section with external AWS documentation links—Claude already knows these exist and can find them; they waste tokens.

The 'Constraints and Warnings' section duplicates content from the referenced constraints.md—keep only the most critical 3-4 warnings inline and point to constraints.md for the rest.

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~350+ lines. The 'Best Practices', 'Constraints and Warnings', 'Monitoring Strategy', 'Log Management', 'Alarm Configuration', 'Template Structure', and 'Dashboard Design' sections contain massive overlap and redundancy. Many bullet points repeat the same advice (e.g., composite alarms, anomaly detection, encryption mentioned multiple times). Claude already knows CloudFormation syntax and AWS concepts—this over-explains.

1 / 3

Actionability

The skill provides fully executable YAML CloudFormation templates and CLI commands throughout. Code examples are copy-paste ready with proper !Sub references, parameter types, and resource configurations. The deploy/verify section includes concrete CLI commands.

3 / 3

Workflow Clarity

The 10-step workflow is clearly sequenced from parameter definition through deployment and verification. Step 9 includes template validation, step 10 includes waiting for completion and verifying alarm states, and there's explicit guidance to test alarm actions before production—a proper feedback loop for this domain.

3 / 3

Progressive Disclosure

The skill does reference four detailed files (alarms.md, dashboards.md, logs.md, constraints.md) with clear descriptions, which is good. However, the main file itself is bloated with inline content that duplicates what those reference files likely cover—the Best Practices, Monitoring Strategy, Log Management, Alarm Configuration, Template Structure, and Dashboard Design sections should largely live in the reference files rather than being repeated here.

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