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.
36
Quality
3%
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
7%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 severely underdeveloped, essentially just restating the skill name without explaining what it does or when to use it. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. The redundant trigger term and generic category reference provide minimal value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Generates AWS CDK stacks, creates infrastructure templates, configures cloud resources using TypeScript/Python CDK constructs'
Include a 'Use when...' clause with natural trigger scenarios like 'Use when the user wants to create AWS infrastructure, mentions CDK, CloudFormation, or infrastructure as code'
Add varied trigger terms users would naturally say: 'AWS CDK', 'infrastructure as code', 'IaC', 'CloudFormation alternative', 'cloud infrastructure', 'AWS resources'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Cdk Stack Generator' without describing any concrete actions. It doesn't explain what the skill actually does - no verbs describing capabilities like 'generates', 'creates', 'configures', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' guidance is just a repetition of the skill name rather than meaningful trigger scenarios. No 'Use when...' clause with actual use cases. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('cdk stack generator' listed twice) and overly specific. Missing natural variations users might say like 'create CDK stack', 'AWS CDK', 'infrastructure as code', 'CloudFormation', or 'IaC'. | 1 / 3 |
Distinctiveness Conflict Risk | The CDK/AWS focus provides some distinctiveness from general coding skills, but 'AWS Skills' category mention is vague and could overlap with other AWS-related skills. The lack of specific capabilities makes it hard to distinguish from other potential CDK or infrastructure skills. | 2 / 3 |
Total | 5 / 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 actionable content about CDK stack generation. It contains only generic boilerplate describing what a skill should do without any actual instructions, code examples, or CDK-specific guidance. The content provides zero value beyond what Claude already knows.
Suggestions
Add executable CDK code examples showing how to create common stack patterns (e.g., Lambda + API Gateway, S3 + CloudFront)
Include a concrete workflow: 1) Initialize CDK project, 2) Define constructs, 3) Synthesize, 4) Deploy with validation steps
Provide specific CDK best practices such as construct organization, environment handling, and stack naming conventions
Reference or link to detailed guides for advanced patterns like cross-stack references, custom constructs, or CI/CD integration
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about CDK stack generation. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude already understands. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The skill describes what it does abstractly ('generates production-ready code') but never shows how to actually generate a CDK stack. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content only describes trigger conditions and vague capabilities without any sequence of actions for CDK stack generation. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, examples, or related files. The content is a shallow placeholder with no depth or navigation. | 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
0c08951
- 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.