Name: localstack
Rating: 60 (1 reviews)
Author: membranedev

localstack

LocalStack integration. Manage data, records, and automate workflows. Use when the user wants to interact with LocalStack data.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/localstack/SKILL.md

Quality

Content

82%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.

The content is highly actionable with copy-paste commands and a strong, checkpointed connection workflow, held back only by minor over-explanation and the absence of validation guidance for destructive proxy/action operations.

Suggestions

Add a pre-flight validation step (e.g. listing or dry-running an action) before executing destructive operations such as DELETE proxy requests or destructive action runs.

Trim the explanatory filler such as 'so you can focus on the integration logic rather than auth plumbing' to improve token efficiency.

Consider moving the service list and proxy-flag table into a reference file and linking to it, which would tighten the overview and lift progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands plus a flag table, with only minor over-explanation ('so you can focus on the integration logic rather than auth plumbing' and the opening LocalStack definition) that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands for every stage (install, login, connection ensure, action list/run, request) plus a complete table of proxy flags, covering the common cases with executable guidance.	5 / 5
Workflow Clarity	The connection workflow has explicit state checkpoints and a feedback loop (poll until READY, branch on CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the action-run and proxy paths include destructive capability (DELETE) without pre-flight validation, leaving a minor validation gap.	4 / 5
Progressive Disclosure	The ~160-line body is well organized into clear sections (Overview, Working with LocalStack, Popular actions, Best practices) with no bundle files to reference; minor organization gaps like the inlined service list and flag table keep it just below a 5.	4 / 5
	Total	17 / 20 Passed

Description

57%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.

The description clearly identifies the LocalStack niche and includes an explicit 'Use when' trigger, but its action list is generic rather than concrete LocalStack operations and it lacks trigger-term synonyms beyond the product name.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete LocalStack actions such as 'create S3 buckets, invoke Lambda functions, send SQS messages, and query DynamoDB tables'.

Add natural trigger synonyms so users who say 'test AWS locally', 'emulate AWS', or 'run AWS services locally' also match the skill.

Tighten the 'Use when' clause to name specific LocalStack workflows rather than the vague 'interact with LocalStack data'.

Dimension	Reasoning	Score
Specificity	Names the LocalStack domain and lists three action areas ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete LocalStack operations (e.g. create S3 buckets, invoke Lambda), matching the anchor where actions are minimal or generic.	2 / 5
Completeness	It states both what ('LocalStack integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with LocalStack data.'), matching the anchor with both present though the 'when' could be more specific.	4 / 5
Trigger Term Quality	The only genuinely natural trigger term is 'LocalStack' (repeated once); common variations a user might say such as 'AWS local', 'cloud emulator', or 'test AWS locally' are missing, so coverage has relevant keywords but lacks synonyms.	3 / 5
Distinctiveness Conflict Risk	'LocalStack integration' is a clear, specific niche with minimal conflict risk, though the generic 'manage data, records' phrasing introduces minor overlap with broad data-management skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/localstack/SKILL.md
Commit: f484c82

Reviewed: 6 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.