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, well-crafted skill description that clearly defines its scope around memory file management (e.g., CLAUDE.md), lists concrete actions it performs, and provides explicit trigger guidance with natural user terms. It effectively distinguishes itself from general documentation or code editing skills through its specific focus on project memory files and quality assessment workflows.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: auditing, quality assessment, targeted improvements, scanning memory files, evaluating quality against standardized criteria, outputting detailed quality reports with scores and recommendations, and making targeted updates with user approval.

3 / 3

Completeness

Clearly answers both 'what' (auditing, quality assessment, scanning, evaluating, reporting, updating memory files) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios and terms.

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'check', 'audit', 'update', 'improve', 'fix', 'maintain', 'validate', 'CLAUDE.md quality check', 'project memory optimization', 'documentation review'. These are terms users would naturally use when needing this skill.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche — memory file management specifically for files like CLAUDE.md — with distinct triggers like 'project memory optimization' and 'CLAUDE.md quality check' that are unlikely to conflict with general documentation or code editing skills.

3 / 3

Total

12

/

12

Passed

Implementation

70%

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

The skill has excellent structure, actionability, and workflow design with clear phases, validation checkpoints, and well-organized references. However, it is significantly too verbose—the 'When to Use' section, overview paragraphs, best practices, and some examples contain substantial redundancy and information Claude doesn't need. Trimming the filler could easily cut 30-40% of tokens without losing any actionable content.

Suggestions

Remove the 'Overview' section entirely—it restates the description and adds no actionable information Claude needs.

Remove or drastically shorten the 'When to Use' section since trigger conditions belong in frontmatter, not the skill body.

Consolidate 'Best Practices' and 'Constraints and Warnings' into a single short list of only non-obvious rules (e.g., remove 'score consistently', 'be project-specific', 'verify file paths').

Reduce from 3 examples to 1-2, and shorten them—the 'Creating from Scratch' example includes generic React boilerplate that doesn't teach the workflow.

DimensionReasoningScore

Conciseness

The skill is excessively verbose at ~200+ lines. It explains concepts Claude already knows (what CLAUDE.md files are, what project memory means), includes a 'When to Use' section that largely duplicates the frontmatter description, provides lengthy examples that could be much shorter, and includes 'Best Practices' and 'Constraints' sections with obvious guidance like 'score consistently' and 'be project-specific'. The overview paragraph is pure filler.

1 / 3

Actionability

The skill provides concrete, executable guidance throughout: specific bash commands for discovery, detailed scoring rubrics with point values, exact report output formats, diff format for updates, and three complete worked examples showing input/output. Commands are copy-paste ready.

3 / 3

Workflow Clarity

The 5-phase workflow is clearly sequenced (Discovery → Assessment → Report → Updates → Apply) with explicit validation checkpoints. Phase 3 has a 'CRITICAL' note to always output the report before making changes, Phase 4 requires user confirmation before updating, and the workflow includes a clear feedback loop (propose → approve → apply).

3 / 3

Progressive Disclosure

The skill appropriately references external files for detailed content: `references/quality-criteria.md` for the full rubric and `references/update-guidelines.md` for detailed update principles. These are one-level-deep, clearly signaled references. The main file serves as an overview with enough inline detail to be useful standalone.

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