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 provides specific concrete actions, comprehensive trigger terms covering multiple diagram types, explicit 'Use when' guidance with enumerated scenarios, and a clear boundary distinguishing it from related skills. The cross-reference to the AWS-specific skill is a particularly strong touch for reducing selection conflicts.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and diagram types: logical flow diagrams, logical architecture diagrams, BPMN process diagrams, UML diagrams (with subtypes), data flow diagrams, decision flowcharts, and system interaction diagrams. Also specifies the output format (.drawio XML).

3 / 3

Completeness

Clearly answers both 'what' (creates professional logical flow and architecture diagrams in draw.io XML format) and 'when' (explicit 'Use when creating:' clause with seven numbered trigger scenarios). Also includes a negative boundary distinguishing it from cloud-specific architecture skills.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'flow diagrams', 'architecture diagrams', 'BPMN', 'UML', 'class diagram', 'sequence diagram', 'activity diagram', 'data flow', 'DFD', 'flowcharts', 'draw.io', '.drawio'. These are terms users would naturally use when requesting these artifacts.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche (generic/abstract diagrams in draw.io format) and explicitly differentiates itself from cloud-specific architecture diagram skills by name ('use aws-drawio-architecture-diagrams for cloud diagrams'). This cross-reference significantly reduces conflict risk.

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 well-structured skill that provides highly actionable, executable draw.io XML guidance with complete working examples. The workflow includes proper validation checkpoints, and content is appropriately split between the main file and references. Minor verbosity in the 'When to Use' section and some tables explaining concepts Claude likely knows prevent a perfect conciseness score.

Suggestions

Remove or significantly trim the 'When to Use' section since this information is already in the skill's description/metadata and the 'Do NOT use for' line could be a single note at the top.

Remove the 'Key XML Components' table as Claude already understands XML structure and the template example immediately below makes these self-evident.

DimensionReasoningScore

Conciseness

The skill is fairly comprehensive but includes some unnecessary content like the 'When to Use' section which largely duplicates the description, and the key XML components table which explains basic XML structure Claude already knows. The shape/color tables are useful reference material but could be more compact.

2 / 3

Actionability

The skill provides fully executable XML examples that are copy-paste ready, complete with proper draw.io XML structure, specific style strings, color codes, and two complete working diagram examples. The connector styles and shape types are concrete and immediately usable.

3 / 3

Workflow Clarity

The 8-step creation process is clearly sequenced, and critically includes an explicit XML validation checklist with specific items to verify before output. This serves as a proper feedback loop for catching errors in the XML generation process, which is important since malformed XML will fail to open.

3 / 3

Progressive Disclosure

The skill provides a clear overview with essential information inline (shapes, styles, examples) while appropriately referencing detailed content in one-level-deep files: shape-styles.md and diagram-templates.md. The references are well-signaled and the inline content is appropriately scoped.

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