step-functions-workflow
Step Functions Workflow - Auto-activating skill for AWS Skills. Triggers on: step functions workflow, step functions workflow Part of the AWS Skills skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage 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/step-functions-workflow/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 weak across all dimensions. It functions as little more than a label, providing no concrete actions, no meaningful trigger terms, and no guidance on when Claude should select this skill. It would be nearly indistinguishable from any generic AWS-related skill in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates, validates, and debugs AWS Step Functions state machine definitions in Amazon States Language (ASL), including configuring task states, parallel execution, error handling, and retry logic.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Step Functions, state machines, workflow orchestration, ASL definitions, or designing multi-step AWS service integrations.'
Remove the duplicate trigger term ('step functions workflow' is listed twice) and expand with natural variations users would actually say, such as 'state machine', 'orchestrate Lambda functions', 'workflow steps', 'parallel execution'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. It merely names 'Step Functions Workflow' without describing what it does—no mention of creating, editing, debugging, deploying, or any specific capabilities. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. The description only states it's an auto-activating skill for AWS Skills without explaining capabilities or explicit usage triggers. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'step functions workflow' repeated twice. Missing natural variations users would say like 'state machine', 'orchestration', 'ASL', 'Amazon States Language', 'workflow definition', or 'step function'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Step Functions Workflow' does narrow it to a specific AWS service, which provides some distinctiveness. However, the lack of specific actions means it could overlap with a general AWS skill or other workflow-related 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 a hollow placeholder with no substantive content about AWS Step Functions. It contains only generic meta-descriptions and trigger phrases without any actionable guidance, code examples, ASL definitions, or workflow steps. It provides no value beyond what Claude already knows about Step Functions.
Suggestions
Add concrete, executable examples such as an ASL (Amazon States Language) state machine definition, AWS CLI commands for creating/deploying step functions, and a CloudFormation or SAM template snippet.
Define a clear multi-step workflow: e.g., 1) Define state machine in ASL JSON, 2) Create IAM execution role, 3) Deploy via CLI/CloudFormation, 4) Test execution, 5) Validate output—with explicit validation checkpoints.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers') that merely restate the skill name, and replace them with actual technical content covering common patterns (e.g., sequential steps, parallel execution, error handling with Catch/Retry).
If the topic is broad, create referenced bundle files for specific patterns (e.g., PATTERNS.md for common workflow patterns, ERROR_HANDLING.md for retry/catch strategies) and link to them from a concise overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content about Step Functions workflows. Every section restates the same vague idea. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific AWS Step Functions syntax, no ASL (Amazon States Language) examples, no CLI commands, no CloudFormation templates. It only describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow steps are defined at all. Step Functions involve multi-step state machine definitions, IAM roles, deployment, and testing, yet none of this is addressed. There are no sequences, validation checkpoints, or error handling guidance. | 1 / 3 |
Progressive Disclosure | No bundle files exist and no references to external resources are provided. The content is a monolithic block of generic placeholder text with no structured navigation to deeper material. | 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 | |
- Commit
3a2d27d
- Reviewed
Table of Contents
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.