aws-blocks

Guides building full-stack applications with AWS Blocks — an Infrastructure-from-Code framework. Applies when creating APIs, selecting Building Blocks (KVStore, DistributedTable, Database, AuthBasic, AuthCognito, Realtime, AsyncJob, FileBucket, etc.), running local development, or deploying AWS Blocks applications. Also covers AWS Blocks topics with validated, version-specific patterns that prevent common mistakes. Triggers when user mentions AWS Blocks; project has aws-blocks/ directory; code imports @aws-blocks packages.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/aws-core/skills/aws-blocks/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, mostly concise skill with concrete scaffolding and security guidance, weakened by delegating the core development workflow to external docs and lacking validation checkpoints for deployment.

Suggestions

Inline a concise development-workflow sequence (scaffold → define blocks → run locally → sandbox → deploy) with at least one validation step instead of only pointing to node_modules READMEs.

Add a post-deploy verification checkpoint (e.g., confirm sandbox URL responds, check CloudWatch/logs) to satisfy the validation requirement for deployment operations.

Merge the 'existing project' and 'Amplify Gen 2' subsections that share the identical `create-blocks-app .` command into one block with a note about Amplify auto-detection to remove redundancy.

Dimension	Reasoning	Score
Conciseness	Mostly lean with dense, useful sections (templates table, security bullets), but the 'To add to an existing project' and 'To add to an Amplify Gen 2 project' subsections repeat the identical `npx @aws-blocks/create-blocks-app .` command, a minor redundancy.	4 / 5
Actionability	Scaffolding commands and security patterns are concrete and executable, but the central 'Development Workflow' section defers entirely to node_modules READMEs rather than providing the actual steps inline, leaving a key gap.	3 / 5
Workflow Clarity	Scaffolding has a clear sequence, but the development/deployment workflow has no validation checkpoints and deployment is mentioned without verification steps, capping this dimension at 3 per the destructive/batch-operation guidance.	3 / 5
Progressive Disclosure	Well-organized sections with one-level-deep, clearly signaled referrals to authoritative READMEs and no nested references; slightly above the midpoint but the core workflow lives entirely outside the skill.	4 / 5
	Total	14 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that concretely states capabilities and gives explicit, multi-signal trigger conditions. Minor room to broaden natural-term synonyms beyond 'AWS Blocks'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'creating APIs, selecting Building Blocks (KVStore, DistributedTable, Database, AuthBasic, AuthCognito, Realtime, AsyncJob, FileBucket, etc.), running local development, or deploying' — giving comprehensive coverage of the framework's capabilities.	5 / 5
Completeness	Explicitly answers 'what' ('Guides building full-stack applications with AWS Blocks...') and 'when' ('Applies when...', 'Triggers when...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good keyword coverage with 'user mentions AWS Blocks; project has aws-blocks/ directory; code imports @aws-blocks packages', but the natural-language trigger phrases are narrow variations on a single term rather than a broad synonym set.	4 / 5
Distinctiveness Conflict Risk	A clear niche anchored to the AWS Blocks framework with specific package scopes and directory names, making conflict with other skills minimal.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: aws/agent-toolkit-for-aws
Path: plugins/aws-core/skills/aws-blocks/SKILL.md
Commit: 88a5fb3

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.