cdk-stack-generator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cdk-stack-generatorCdk Stack Generator - Auto-activating skill for AWS Skills. Triggers on: cdk stack generator, cdk stack generator Part of the AWS Skills skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining what it actually does or when to use it. It lacks concrete actions, natural trigger terms, and explicit usage guidance, making it nearly impossible for Claude to correctly select this skill from a pool of alternatives.
Suggestions
Add specific capabilities like 'Generates AWS CDK stacks, scaffolds infrastructure code, creates TypeScript/Python CDK constructs for common AWS services'
Include a 'Use when...' clause with natural triggers: 'Use when the user asks to create AWS infrastructure, generate CDK code, scaffold a new stack, or mentions CDK, CloudFormation, or infrastructure as code'
Add common user terms and file extensions: 'CDK', 'AWS infrastructure', 'CloudFormation', 'IaC', 'cdk.json', 'stack template'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Cdk Stack Generator') without describing any concrete actions. There are no specific capabilities listed like 'generates infrastructure code', 'creates CloudFormation templates', or 'scaffolds AWS resources'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and 'when should Claude use it' is not addressed at all. There is no 'Use when...' clause or equivalent guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated ('cdk stack generator, cdk stack generator'). Missing natural user terms like 'AWS infrastructure', 'CloudFormation', 'IaC', 'infrastructure as code', 'deploy stack', or 'CDK app'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'CDK' and 'stack generator' provide some specificity to AWS CDK context, the lack of detail means it could conflict with other AWS-related skills. The category mention helps slightly but doesn't fully distinguish it. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual CDK stack generation guidance. It contains only generic boilerplate describing what the skill claims to do without any concrete instructions, code examples, or workflows. The content provides zero value beyond trigger word matching.
Suggestions
Add executable CDK code examples showing how to create common stack patterns (e.g., Lambda + API Gateway, S3 + CloudFront)
Include a clear workflow: 1) Initialize CDK project, 2) Define constructs, 3) Synthesize, 4) Deploy with validation steps
Provide specific CDK CLI commands (cdk init, cdk synth, cdk deploy) with expected outputs
Remove all generic capability descriptions and replace with concrete, actionable guidance specific to CDK stack generation
| 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 doesn't need. | 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
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.