step-functions

AWS Step Functions workflow orchestration with state machines. Use when designing workflows, implementing error handling, configuring parallel execution, integrating with AWS services, or debugging executions.

1.02x

Quality

84%

Does it follow best practices?

Impact

94%

1.02x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

76%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 solid reference-style skill body with executable, comprehensive code examples and clean organization. Its main weakness is workflow clarity: the create/start-execution flows lack embedded validation checkpoints, and the validation command is relegated to troubleshooting.

Suggestions

Add an explicit validation checkpoint in the create-state-machine flow, e.g. run `aws stepfunctions validate-state-machine-definition` before create/update and only proceed when valid.

Tighten the intro and the ASL one-liner to remove concepts Claude already knows, pushing conciseness toward level 5.

Consider moving the full CLI reference tables and the pattern catalog into a references/ bundle file so SKILL.md stays a lean overview, improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean tables and complete code examples that assume Claude's competence, with only minor over-explanation such as the intro ("AWS Step Functions is a serverless orchestration service...") and "Amazon States Language (ASL): JSON-based language for defining state machines", fitting the level-4 anchor rather than the fully lean level-5.	4 / 5
Actionability	It provides fully executable, copy-paste-ready ASL JSON, AWS CLI, and boto3 examples covering the common cases (Lambda workflow, Choice, Parallel, Map, error handling), matching the level-5 anchor.	5 / 5
Workflow Clarity	Patterns like create-state-machine → start-execution and the troubleshooting cause/fix structure give a rough sequence, but there are no explicit validate-then-proceed checkpoints in the main flows (the validate-state-machine-definition command appears only under troubleshooting), fitting the level-3 anchor of sequence present but checkpoints missing or implicit.	3 / 5
Progressive Disclosure	Content is well-organized with a table of contents, clear section headers, and a clearly signaled References section pointing to external AWS docs, fitting the level-4 anchor of good structure with minor organization gaps; no bundle files exist so structure is judged on the inline organization.	4 / 5
	Total	16 / 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, well-structured description that concretely states capabilities, includes a clear "Use when" trigger clause, and occupies a distinct niche. The only minor gap is missing synonyms such as "ASL"/"Amazon States Language" among the trigger terms.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — "designing workflows, implementing error handling, configuring parallel execution, integrating with AWS services, or debugging executions" — giving comprehensive coverage of the skill's capabilities, matching the level-5 anchor rather than the level-4 anchor which expects minor gaps.	5 / 5
Completeness	It explicitly answers both "what" ("AWS Step Functions workflow orchestration with state machines") and "when" ("Use when designing workflows, implementing error handling..."), matching the level-5 anchor for clearly and explicitly answering both with concrete trigger phrases.	5 / 5
Trigger Term Quality	It includes strong natural terms a user would say ("Step Functions", "state machines", "workflows", "error handling", "debugging executions"), but omits common synonyms like "ASL" or "Amazon States Language", fitting the level-4 anchor of good coverage with a few natural terms missing rather than the comprehensive level-5.	4 / 5
Distinctiveness Conflict Risk	The leading "AWS Step Functions workflow orchestration with state machines" carves a clear niche with distinct triggers and minimal conflict risk, matching the level-5 anchor; the broad "integrating with AWS services" phrase is scoped to Step Functions workflow integration.	5 / 5
	Total	19 / 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: itsmostafa/aws-agent-skills
Path: skills/step-functions/SKILL.md
Commit: e786d25

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