ecs-task-definition-creator
Ecs Task Definition Creator - Auto-activating skill for AWS Skills. Triggers on: ecs task definition creator, ecs task definition creator Part of the AWS Skills skill category.
39
Quality
11%
Does it follow best practices?
Impact
88%
0.93xAverage 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/ecs-task-definition-creator/SKILL.mdQuality
Discovery
22%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 severely underdeveloped, essentially just restating the skill name without explaining what actions it performs or when it should be used. It lacks concrete capabilities, natural trigger terms, and explicit usage guidance, making it difficult for Claude to reliably select this skill from a pool of AWS-related options.
Suggestions
Add specific actions the skill performs, e.g., 'Creates ECS task definitions including container configurations, resource limits, networking settings, and IAM role assignments'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user needs to create or configure ECS task definitions, Fargate tasks, container definitions, or asks about ECS container settings'
Include common variations users might say: 'ECS task', 'task def', 'container definition', 'Fargate configuration', 'AWS container setup'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Ecs Task Definition Creator' which names a domain but provides no concrete actions. It doesn't explain what creating a task definition involves (e.g., configuring containers, setting memory/CPU limits, defining environment variables). | 1 / 3 |
Completeness | The description only vaguely addresses 'what' (creates ECS task definitions) and completely lacks a 'Use when...' clause or any explicit guidance on when Claude should select this skill. The 'Triggers on' field just repeats the skill name. | 1 / 3 |
Trigger Term Quality | Includes 'ecs task definition creator' as a trigger term (duplicated), which is somewhat relevant but misses natural variations users might say like 'ECS task', 'container definition', 'Fargate task', 'task def', or 'AWS container configuration'. | 2 / 3 |
Distinctiveness Conflict Risk | Being part of 'AWS Skills' category and mentioning 'ECS task definition' provides some specificity, but without detailed triggers it could conflict with other AWS-related skills or general infrastructure/container skills. | 2 / 3 |
Total | 6 / 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 essentially a placeholder with no actionable content. It describes what it claims to do in abstract terms but provides zero concrete guidance on creating ECS task definitions—no JSON examples, no required fields, no AWS CLI commands, no validation steps. The content would be useless for actually helping someone create an ECS task definition.
Suggestions
Add a concrete, executable ECS task definition JSON example with common fields (containerDefinitions, cpu, memory, executionRoleArn)
Include AWS CLI commands for registering and validating task definitions (e.g., `aws ecs register-task-definition --cli-input-json file://task-def.json`)
Define a clear workflow: 1) Create JSON, 2) Validate required fields, 3) Register with ECS, 4) Verify registration
Remove all generic boilerplate ('provides automated assistance', 'follows industry best practices') and replace with specific ECS task definition requirements and constraints
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about ECS task definitions. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any guidance, examples, or executable content for creating ECS task definitions. | 1 / 3 |
Workflow Clarity | No workflow is defined. Creating ECS task definitions involves specific steps (defining container specs, resource limits, IAM roles, etc.) but none are mentioned. No validation checkpoints or sequences are provided. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed materials. No references to examples, templates, or advanced configuration guides are provided. | 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
0c08951
- 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.