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 clearly defines its scope at the intersection of AWS CloudFormation and Lambda. It lists comprehensive specific capabilities and includes an explicit 'Use when' clause with natural trigger terms that AWS developers would use. The only minor weakness is some redundancy between the 'what' and 'when' portions, but this doesn't detract from its effectiveness.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: CloudFormation patterns for Lambda functions, layers, API Gateway integration, event sources, cold start optimization, monitoring, logging, template validation, and deployment workflows.

3 / 3

Completeness

Clearly answers both 'what' (provides AWS CloudFormation patterns for Lambda functions, layers, API Gateway integration, etc.) and 'when' (explicit 'Use when' clause listing specific trigger scenarios like creating Lambda functions with CloudFormation, configuring event sources, etc.).

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'Lambda functions', 'CloudFormation', 'API Gateway', 'cold start', 'layers', 'event sources', 'deployment', 'monitoring', 'logging', 'template validation'. These cover the terms AWS developers naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly specific niche combining AWS CloudFormation with Lambda-specific concerns. The intersection of CloudFormation + Lambda + specific sub-topics like cold start optimization and layers makes it clearly distinguishable from generic AWS, IaC, or serverless skills.

3 / 3

Total

12

/

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 excels at actionability with executable CloudFormation templates and a well-structured deployment workflow with validation steps. However, it is significantly bloated with generic best practices and constraints that Claude already knows, consuming excessive tokens. The content would benefit greatly from moving the Best Practices and Constraints sections to reference files and trimming redundant advice.

Suggestions

Move the Best Practices and Constraints sections to separate reference files (e.g., references/best-practices.md, references/constraints.md) and link to them from the main skill, keeping only the most critical 2-3 warnings inline.

Remove generic advice Claude already knows (e.g., 'test Lambda functions thoroughly before deployment', 'apply least privilege IAM policies') and keep only Lambda-specific, non-obvious guidance.

Consolidate the step-by-step Instructions and the Complete Lambda Stack Template example — the individual snippets in steps 1-8 largely duplicate what's in the complete template, so consider showing only the complete template with inline comments.

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~300+ lines. The Best Practices section is largely generic advice Claude already knows (e.g., 'apply least privilege IAM policies', 'test Lambda functions thoroughly before deployment'). The Constraints section repeats information from Best Practices. Much of this could be cut by 50%+ without losing actionable value.

1 / 3

Actionability

The skill provides fully executable CloudFormation YAML templates and CLI commands throughout. The deployment workflow has copy-paste ready bash commands, and the complete stack template example is directly usable.

3 / 3

Workflow Clarity

The deployment workflow is clearly sequenced with 5 explicit steps: validate → deploy → monitor events → verify resources → rollback on failure. This includes validation checkpoints (template validation, stack status checks) and error recovery (monitoring failed events, rollback instructions).

3 / 3

Progressive Disclosure

There is a reference to constraints.md for detailed limits, and external AWS docs are linked. However, the massive Best Practices and Constraints sections are inlined when they could be split into reference files, and the main body is a monolithic wall of content that would benefit from better separation.

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