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.

1.00x

Quality

Does it follow best practices?

Impact

100%

1.00x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./planned-skills/generated/13-aws-skills/cdk-stack-generator/SKILL.md

Quality

Discovery

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 essentially a placeholder that repeats the skill name and category without providing any substantive information about capabilities, use cases, or trigger conditions. It fails on all dimensions: no concrete actions, no natural trigger terms, no explicit 'when to use' guidance, and no distinguishing details to separate it from other AWS-related skills.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Generates AWS CDK stack definitions, scaffolds infrastructure-as-code projects, creates TypeScript/Python CDK constructs 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, scaffold AWS infrastructure, generate IaC templates, or set up cloud resources using AWS CDK.'

Diversify trigger terms to include natural variations users would say: 'CDK', 'AWS CDK', 'infrastructure as code', 'IaC', 'CloudFormation', 'cloud stack', 'deploy infrastructure', '.ts stack', 'cdk init'.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions. It only names itself ('Cdk Stack Generator') and mentions it's 'auto-activating' for 'AWS Skills' but never describes what it actually does — e.g., generating CDK stacks, scaffolding infrastructure, creating CloudFormation templates, etc.	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause and no description of capabilities beyond the skill's name.	1 / 3
Trigger Term Quality	The trigger terms are just the skill name repeated twice ('cdk stack generator, cdk stack generator'). There are no natural user keywords like 'AWS CDK', 'infrastructure as code', 'CloudFormation', 'deploy stack', 'IaC', or 'cloud infrastructure'.	1 / 3
Distinctiveness Conflict Risk	The description says it's part of 'AWS Skills' which is extremely broad. Without specifying what distinguishes CDK stack generation from other AWS-related skills (e.g., Lambda deployment, S3 management), it would easily conflict with any other AWS skill.	1 / 3
	Total	4 / 12 Passed

Implementation

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 placeholder with no substantive content. It repeatedly names 'cdk stack generator' without providing any actual guidance, code, commands, or workflows for generating AWS CDK stacks. It fails on every dimension because it contains zero actionable information.

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).

Provide a clear step-by-step workflow: initialize a CDK project (`cdk init`), define constructs, synthesize (`cdk synth`), validate the CloudFormation output, and deploy (`cdk deploy`) with explicit validation checkpoints.

Remove all boilerplate meta-descriptions ('This skill provides automated assistance...') and replace with lean, actionable content that assumes Claude already knows what CDK is.

Add references to supporting files for advanced patterns (e.g., PATTERNS.md for common stack architectures, CONSTRUCTS.md for custom construct examples) to enable progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'cdk stack generator' excessively, and provides zero substantive information about actually generating CDK stacks.	1 / 3
Actionability	There are no concrete code examples, no CDK constructs, no commands, no executable guidance whatsoever. The skill describes what it does in abstract terms without ever showing how to do anything.	1 / 3
Workflow Clarity	There is no workflow, no steps, no sequence, and no validation checkpoints. The bullet 'Provides step-by-step guidance' is a claim with no actual steps provided.	1 / 3
Progressive Disclosure	The content is a monolithic block of vague descriptions with no references to supporting files, no bundle files exist, and there is no structured navigation to deeper content.	1 / 3
	Total	4 / 12 Passed

Validation

81%

Warnings & errors only

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

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3a2d27d

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.