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 articulates specific capabilities across multiple AWS services, provides concrete actions (bulk scripts, cross-service workflows, security validation, JMESPath queries), and includes an explicit and comprehensive list of trigger terms. The description is well-structured, uses third person voice correctly, and would be easily distinguishable from other skills in a large skill library.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: managing EC2/Lambda/S3/DynamoDB/RDS/VPC/IAM/CloudWatch, generating bulk operation scripts, automating cross-service workflows, validating security configurations, and executing JMESPath queries for complex filtering.

3 / 3

Completeness

Clearly answers both 'what' (advanced AWS CLI patterns for specific services, bulk operations, cross-service workflows, security validation, JMESPath queries) and 'when' (explicit trigger terms listed with 'Triggers on' clause serving as the equivalent of a 'Use when' clause).

3 / 3

Trigger Term Quality

Includes a comprehensive list of natural trigger terms users would say: 'aws cli help', 'aws command line', 'aws scripting', 'aws automation', 'aws batch operations', 'aws bulk operations', 'aws cli pagination', 'aws multi-region', 'aws profiles', 'aws cli troubleshooting'. These cover many common variations of how users would phrase AWS CLI requests.

3 / 3

Distinctiveness Conflict Risk

Clearly scoped to AWS CLI specifically, with distinct triggers like 'aws cli', 'aws command line', 'JMESPath queries', and specific service names. This is unlikely to conflict with general cloud skills or non-CLI AWS skills due to the explicit CLI focus and detailed service enumeration.

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 with excellent actionability and workflow clarity. The destructive operation safety patterns with mandatory dry-runs and validation gates are particularly well done. The main weakness is moderate verbosity — some sections explain things Claude already knows (service categorization, basic best practices like tagging resources), and the 'Beast Mode' branding adds no instructional value.

Suggestions

Remove the Step 1 categorization table — Claude already knows which AWS services map to which categories. Replace with a brief note to identify the service and check the relevant detailed guide.

Trim the Best Practices list to only non-obvious items (e.g., keep #8 simulate-principal-policy and #9 dry-run, but drop #5 tagging and #7 CloudTrail which Claude already knows).

DimensionReasoningScore

Conciseness

Generally efficient but includes some unnecessary framing (e.g., 'Beast Mode' branding, 'When to Use' section listing obvious use cases, the categorization table in Step 1 that Claude already knows). The best practices list has items Claude would already know (like 'tag all resources' and 'enable CloudTrail'). Could be tightened by ~20-30%.

2 / 3

Actionability

Excellent executable examples throughout — all bash commands are copy-paste ready with real flags, JMESPath queries, and piping patterns. Examples cover bulk EC2 stop, S3 migration, IAM audit, multi-region Lambda deployment, and advanced JMESPath filtering, all with concrete, runnable commands.

3 / 3

Workflow Clarity

Multi-step processes are clearly sequenced with explicit validation checkpoints. Destructive operations have mandatory dry-run steps, review gates before execution, and the examples consistently follow a pattern of identify → confirm → execute. The feedback loop of 'dry-run first, review, then remove --dryrun' is well-established.

3 / 3

Progressive Disclosure

Clear overview with well-organized sections, and references to four detailed guide files (compute-mastery.md, data-ops-beast.md, networking-security-hardened.md, automation-patterns.md) that are one level deep and clearly signaled. The main content stays at the right level of detail for an overview skill.

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