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 hits all the marks. It clearly states what it does (creates AWS architecture diagrams in draw.io XML format), specifies the tooling details (aws4 library, .drawio files), and provides an explicit 'Use when...' clause with a rich set of natural trigger terms covering various AWS architecture scenarios and specific services. It serves as a strong example of a well-crafted skill description.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and details: creates diagrams in draw.io XML format, uses official AWS Architecture Icons (aws4 library), and specifies the output format (.drawio files). Very concrete and actionable.

3 / 3

Completeness

Clearly answers both 'what' (creates professional AWS architecture diagrams in draw.io XML format using official AWS icons) and 'when' (explicit 'Use when...' clause listing multiple trigger scenarios like AWS diagrams, VPC layouts, serverless designs, etc.).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'AWS diagrams', 'VPC layouts', 'multi-tier architectures', 'serverless designs', 'network topology', 'draw.io exports', and specific service names like 'Lambda', 'EC2', 'RDS'. These are terms users would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: the combination of AWS architecture + draw.io XML format + specific AWS icon library (aws4) makes this very unlikely to conflict with other skills. The trigger terms are specific to this domain.

3 / 3

Total

12

/

12

Passed

Implementation

85%

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

This is a strong, well-structured skill that provides highly actionable guidance for generating AWS architecture diagrams in draw.io XML format. The concrete XML examples, color code tables, and validation workflow make it immediately usable. Minor verbosity in repeated best practices and some sections that explain things Claude would already know (like security considerations and limitations) prevent a perfect conciseness score.

Suggestions

Remove or consolidate the 'Best Practices' section at the end, as most points are already covered in the body (e.g., nesting hierarchy, grid alignment, labeling).

Trim the 'When to Use' section and 'Security Considerations' — Claude can infer appropriate use cases, and generic security advice adds little value.

DimensionReasoningScore

Conciseness

The skill is mostly efficient with good use of tables and code blocks, but includes some unnecessary sections like 'When to Use' (Claude can infer this), 'Limitations' that are somewhat obvious, and 'Security Considerations' that are generic advice. The 'Best Practices' section at the end largely repeats guidance already given in the body.

2 / 3

Actionability

Excellent actionability with complete, copy-paste-ready XML examples, specific style strings, exact color codes, concrete coordinate values, and a full three-tier architecture example. The service color code table and connector style definitions are immediately usable.

3 / 3

Workflow Clarity

Clear validation workflow with numbered steps including ID uniqueness checks, parent reference verification, XML well-formedness validation, and a test step. The hierarchical nesting order is explicitly stated (AWS Cloud → Region → VPC → Subnet → Services), and critical constraints are clearly called out with consequences of failure.

3 / 3

Progressive Disclosure

Well-structured with a clear overview, inline essentials for immediate use, and references to external files (aws-shape-reference.md, aws-architecture-templates.md) for the complete shape catalog and additional templates. The serverless example appropriately defers to the reference file rather than duplicating content.

3 / 3

Total

11

/

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