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 communicates both what the skill does and when to use it. It lists specific concrete actions across the workflow, includes natural trigger terms users would say, and has an explicit 'Use when...' clause with good keyword coverage. The description is well-scoped to GitHub issue resolution, making it distinctly identifiable among other skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: fetching issue details, analyzing requirements, implementing solutions, verifying correctness, performing code review, committing changes, and creating pull requests. Also specifies it's a structured 8-phase workflow.

3 / 3

Completeness

Clearly answers both 'what' (structured 8-phase workflow covering fetching, analyzing, implementing, verifying, reviewing, committing, and creating PRs) and 'when' (explicit 'Use when...' clause with multiple trigger scenarios including issue URLs and numbers).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms: 'resolve', 'implement', 'work on', 'fix', 'close', 'GitHub issue', 'issue URL', 'issue number'. These are terms users would naturally use when asking for help with GitHub issues.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: GitHub issue resolution workflow in Claude Code. The combination of GitHub issues, the specific 8-phase workflow, and PR creation makes it unlikely to conflict with general coding or git 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.

This skill has strong structural organization and progressive disclosure, with clear navigation to detailed reference files. However, it suffers from some redundancy across sections (security warnings repeated in three places, best practices overlapping with constraints) and the main file's phase descriptions are too abstract to be directly actionable — the real executable content is deferred to external references. The workflow sequence is well-defined but lacks explicit error recovery/feedback loops in verification and review phases.

Suggestions

Consolidate the overlapping content between 'Security: Handling Untrusted Content', 'Best Practices', and 'Constraints and Warnings' — the untrusted content warning appears three times with slightly different wording.

Add concrete validation/feedback loops to Phases 5 and 6 (e.g., 'If tests fail: analyze failure output → fix → re-run tests → only proceed when all pass'), since these are critical verification steps.

Either inline more executable code for Phases 2-8 in the main file or make the phase summaries more specific — currently they read as abstract descriptions rather than actionable instructions.

Remove or significantly trim the 'When to Use' and trigger phrases section, as this metadata is better suited for frontmatter and wastes tokens in the skill body.

DimensionReasoningScore

Conciseness

The skill includes some unnecessary verbosity — the 'When to Use' section with trigger phrases is redundant given the frontmatter description, and the 'Best Practices' and 'Constraints and Warnings' sections overlap significantly (e.g., both mention confirming understanding, not skipping confirmation, treating issue content as untrusted). The security section, while important, repeats the same concept multiple times across Overview, Security section, and Constraints.

2 / 3

Actionability

Phase 1 has concrete executable bash commands, but Phases 2-8 are described abstractly with only brief summaries rather than executable guidance. The detailed instructions are deferred to references/phases-detailed.md. The example is helpful but abbreviated — it shows the happy path without the intermediate steps. The skill relies heavily on external references for actual actionable content.

2 / 3

Workflow Clarity

The 8-phase workflow is clearly sequenced with explicit user confirmation gates at Phases 2 and 4, and the constraint that Phases 1-3 must complete before Phase 4. However, validation/verification steps within phases are vague — Phase 5 says 'run full test suite' without specifying what to do on failure, and Phase 6's review process lacks a feedback loop for re-review after fixes. The quick reference table aids clarity but the actual phase descriptions are too thin to guide execution.

2 / 3

Progressive Disclosure

Excellent structure with a clear overview, concise phase summaries in the main file, and well-signaled one-level-deep references to detailed content (prerequisites, security protocol, phases-detailed, examples). The References section is well-organized into logical categories (Setup/Security and Workflow Details).

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