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 clearly defines its scope (AWS Secrets Manager with Java 2.x SDK), lists specific capabilities, and includes an explicit 'Use when' clause with natural trigger terms. It is well-differentiated from other potential skills due to its precise technology stack focus and concrete action descriptions.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: secret retrieval, caching, rotation-aware access, Spring Boot integration, replacing hardcoded credentials, and wiring secret-backed configuration.

3 / 3

Completeness

Clearly answers both 'what' (AWS Secrets Manager patterns for Java 2.x SDK including retrieval, caching, rotation, Spring Boot integration) and 'when' (explicit 'Use when' clause covering storing/reading secrets, replacing hardcoded credentials, wiring secret-backed config).

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'AWS Secrets Manager', 'Java', 'secret retrieval', 'hardcoded credentials', 'Spring Boot', 'caching', 'rotation', 'AWS SDK for Java 2.x'. These cover the domain well and match how developers naturally describe these tasks.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: AWS Secrets Manager + Java 2.x SDK. The combination of specific cloud service, specific SDK version, and specific use cases (rotation-aware, Spring Boot integration) makes it very unlikely to conflict with other skills.

3 / 3

Total

12

/

12

Passed

Implementation

57%

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

The skill has good structure and progressive disclosure, with clear references to supplementary materials. However, it leans too heavily on abstract guidance in the instruction steps without matching concrete code examples—only two examples are provided for six steps. Some content (trigger phrases, general design advice) is unnecessary padding that Claude doesn't need.

Suggestions

Add executable code examples for error handling (step 3), rotation-aware access (step 5), and validation (step 6) to match the abstract guidance with concrete implementations.

Remove the 'typical trigger phrases' list and trim the 'When to Use' section—these are routing concerns handled by the YAML frontmatter, not the skill body.

Define the DatabaseSecret record/class used in Example 1 so the example is fully copy-paste ready.

Add a concrete feedback loop for rotation scenarios: show code that detects stale credentials and retries with cache invalidation.

DimensionReasoningScore

Conciseness

The skill is mostly efficient but includes some unnecessary content. The 'When to Use' section with 'typical trigger phrases' is padding. Steps like 'Model the secret before writing access code' and 'Decide' bullet lists explain general software design thinking Claude already knows. The 'Best Practices' section partially overlaps with the Instructions.

2 / 3

Actionability

The two code examples are concrete and executable, which is good. However, the six instruction steps are largely abstract guidance ('Design for rotation,' 'Validate end-to-end behavior') without concrete code or commands. The DatabaseSecret class is never defined. Error handling is described but never shown. The gap between the instructional prose and the limited code examples reduces overall actionability.

2 / 3

Workflow Clarity

The six numbered steps provide a reasonable sequence, and step 6 mentions validation. However, the validation step is a checklist of things to verify without concrete commands or tools to run them. There are no explicit feedback loops (e.g., what to do if IAM permissions fail, how to retry). For operations involving secret rotation and cache invalidation, the lack of concrete validation checkpoints caps this at 2.

2 / 3

Progressive Disclosure

The skill is well-structured as an overview with clear one-level-deep references to api-reference.md, caching-guide.md, and spring-boot-integration.md. The main content stays concise and delegates detailed material appropriately. Related skills are also clearly listed.

3 / 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