Sam Template Builder - Auto-activating skill for AWS Skills. Triggers on: sam template builder, sam template builder Part of the AWS Skills skill category.
35
3%
Does it follow best practices?
Impact
94%
1.01xAverage 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/sam-template-builder/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 extremely minimal and essentially just restates the skill name without explaining what the skill does or when it should be used. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance, making it nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates AWS SAM template.yaml files, configures Lambda functions, API Gateway endpoints, DynamoDB tables, and other serverless resources.'
Add a 'Use when...' clause with natural trigger terms like 'SAM template', 'serverless application model', 'template.yaml', 'AWS Lambda deployment', 'serverless infrastructure as code'.
Remove the duplicate trigger term ('sam template builder' is listed twice) and expand with varied natural language phrases users would actually say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. 'Sam Template Builder' names a domain but does not describe what it actually does—no mention of creating, editing, validating, or deploying SAM templates or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is just a repetition of the skill name rather than meaningful trigger guidance. Both dimensions are very weak. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'sam template builder' repeated twice. It misses natural user phrases like 'SAM template', 'serverless application model', 'AWS SAM', 'template.yaml', 'Lambda deployment', 'CloudFormation', or 'serverless infrastructure'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'SAM Template Builder' and 'AWS Skills' provides some specificity to a niche domain, but the lack of concrete actions or detailed triggers means it could overlap with other AWS-related skills or CloudFormation 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 placeholder with no actual content about SAM template building. It contains only generic boilerplate text that could describe any skill, with zero actionable information about AWS SAM templates, template syntax, resource definitions, or deployment workflows. It provides no value beyond what Claude already knows.
Suggestions
Add concrete SAM template examples showing common patterns (e.g., API Gateway + Lambda, S3 event triggers) with complete, copy-paste-ready YAML templates.
Include a clear workflow: `sam init` → edit template.yaml → `sam validate` → `sam build` → `sam local invoke` (test) → `sam deploy`, with validation checkpoints at each step.
Add specific guidance on SAM-specific resource types (AWS::Serverless::Function, AWS::Serverless::Api, etc.) with property references and common configurations.
Remove all generic boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable content like template structure, globals configuration, and common gotchas.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains nothing Claude doesn't already know and provides zero actual guidance on SAM template building. Every section is generic boilerplate that could apply to any skill. | 1 / 3 |
Actionability | There are no concrete code examples, no SAM template snippets, no CLI commands, no specific configuration patterns. The content is entirely abstract and descriptive, offering no executable guidance whatsoever. | 1 / 3 |
Workflow Clarity | There is no workflow defined at all. SAM template building involves multi-step processes (init, build, validate, deploy) but none are mentioned. No validation steps, no sequencing, no checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic text with no references to detailed materials, no links to examples, and no structured navigation to deeper content about SAM templates, resource types, or deployment patterns. | 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 | |
4dee593
Table of Contents
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.