cdk-stack-generator
Cdk Stack Generator - Auto-activating skill for AWS Skills. Triggers on: cdk stack generator, cdk stack generator Part of the AWS Skills skill category.
34
0%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/13-aws-skills/cdk-stack-generator/SKILL.mdQuality
Discovery
0%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 description is extremely weak across all dimensions. It is essentially a repeated skill name with a category label, providing no information about what the skill actually does, what concrete actions it performs, or when it should be selected. It would be nearly impossible for Claude to reliably choose this skill from a pool of available skills.
Suggestions
Add concrete capability descriptions such as 'Generates AWS CDK stack definitions in TypeScript/Python, creates infrastructure-as-code templates for common AWS services like Lambda, S3, DynamoDB, and API Gateway.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a CDK stack, generate infrastructure as code, set up AWS resources programmatically, or mentions CDK, CloudFormation, or IaC.'
Remove the duplicate trigger term and expand with natural variations users would say, such as 'CDK', 'AWS stack', 'infrastructure as code', 'IaC template', 'cloud infrastructure setup'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Cdk Stack Generator') and its category ('AWS Skills') but does not describe any concrete actions like 'generates CDK stacks', 'creates infrastructure-as-code templates', or 'defines AWS resources'. It is essentially a title repeated, not a capability description. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just the skill name repeated twice ('cdk stack generator, cdk stack generator'). It lacks natural user keywords like 'CDK', 'CloudFormation', 'infrastructure as code', 'AWS stack', 'IaC', 'cloud infrastructure', or 'TypeScript stack'. | 1 / 3 |
Distinctiveness Conflict Risk | Being labeled only as part of 'AWS Skills' with no specific scope makes it highly likely to conflict with other AWS-related skills. There is nothing distinguishing this from other potential AWS infrastructure, CloudFormation, or CDK-related skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no actual content about CDK stack generation. It contains no executable code, no AWS CDK constructs, no specific patterns, and no actionable guidance whatsoever. Every section is generic boilerplate that could be auto-generated for any topic by replacing the skill name.
Suggestions
Add concrete, executable CDK code examples (e.g., a TypeScript/Python CDK stack definition with common constructs like S3 buckets, Lambda functions, or VPCs)
Define a clear workflow for generating CDK stacks: initialize project → define constructs → synthesize → validate → deploy, with specific commands like `cdk init`, `cdk synth`, `cdk diff`, `cdk deploy`
Include specific CDK best practices such as construct organization, environment configuration, tagging strategies, and common anti-patterns to avoid
Remove all generic filler sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actionable content like code templates, configuration patterns, and validation steps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains nothing Claude doesn't already know and consists of generic template text that could apply to any skill. Every section restates the title without adding value. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no CDK constructs, no commands, no specific patterns. The skill describes what it could do in abstract terms ('provides step-by-step guidance') without actually providing any guidance. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains no steps whatsoever. There are no validation checkpoints or sequenced operations. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic placeholder text with no references to detailed materials, no links to examples or API references, and no meaningful structural organization beyond boilerplate headings. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
c8a915c
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.