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 articulates specific capabilities across multiple AWS security domains, provides an explicit 'Use when' clause with natural trigger terms, and occupies a distinct niche. The description is comprehensive without being verbose, covering both the what and when effectively with domain-specific terminology users would naturally employ.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and domains: KMS encryption, Secrets Manager, IAM security, VPC security, ACM certificates, parameter security, outputs, and secure cross-stack references. These are concrete, identifiable capabilities.

3 / 3

Completeness

Clearly answers both 'what' (provides CloudFormation patterns for security infrastructure including specific services) and 'when' (explicit 'Use when' clause covering implementing security best practices, encrypting data, managing secrets, IAM policies, VPC configurations, certificates, and defense in depth).

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'CloudFormation', 'KMS encryption', 'Secrets Manager', 'IAM', 'VPC security', 'ACM certificates', 'TLS/SSL certificates', 'least privilege', 'defense in depth', 'encrypting data', 'managing secrets'. Good coverage of terms a user working on AWS security infrastructure would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche: AWS CloudFormation + security infrastructure is a very specific combination. The enumeration of specific AWS services (KMS, Secrets Manager, ACM, VPC) makes it clearly distinguishable from general CloudFormation skills or general security skills.

3 / 3

Total

12

/

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 solid, comprehensive security infrastructure skill with excellent actionability—every section includes executable CloudFormation YAML and CLI validation commands. The main weaknesses are moderate redundancy between the instructional steps and the examples section, and a lack of explicit workflow sequencing and error recovery guidance. The progressive disclosure structure is well done with clear references to supporting files.

Suggestions

Remove or significantly condense the 'Examples' section since it largely duplicates patterns already shown in the step-by-step instructions, or differentiate it by showing a single integrated stack that combines multiple security components.

Add explicit error recovery guidance after validation commands (e.g., 'If key policy validation fails, check that the Principal ARN matches your account ID') to create proper feedback loops for these security-critical operations.

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some redundancy—the 'Examples' section at the bottom largely repeats patterns already shown in the step-by-step instructions (KMS key, IAM role). The 'When to Use' section restates the overview. Some trimming would improve token efficiency.

2 / 3

Actionability

Every step includes complete, copy-paste-ready CloudFormation YAML snippets with specific resource types, properties, and realistic configurations. Validation commands are provided for each step with concrete AWS CLI commands.

3 / 3

Workflow Clarity

Each step has a validation command which is good, but the steps are presented as independent patterns rather than a sequenced workflow with dependencies. There's no feedback loop for what to do if validation fails, and no explicit ordering rationale (e.g., KMS must be created before Secrets Manager references it). For infrastructure involving destructive/security-critical operations, the lack of error recovery guidance caps this at 2.

2 / 3

Progressive Disclosure

The skill provides a clear overview with inline essentials and appropriately delegates detailed examples and constraints to one-level-deep reference files (references/examples.md, references/constraints.md). Navigation is well-signaled with descriptive links.

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