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.
34
3%
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
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 essentially a placeholder that repeats the skill name without providing any meaningful information about capabilities, use cases, or trigger scenarios. It lacks concrete actions, natural trigger terms, and explicit guidance on when Claude should select this skill. It would be nearly indistinguishable in a large skill library and provides no value for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates AWS ECS task definitions with container configurations, resource limits, networking settings, and IAM role assignments.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create or configure an ECS task definition, define containers for Fargate or EC2 launch types, set up Docker container specs for AWS, or generate task definition JSON.'
Include common keyword variations users might say: 'ECS', 'task def', 'container definition', 'Fargate task', 'Docker on AWS', '.json task definition', 'containerDefinitions'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('ECS task definition') but does not describe any concrete actions. It merely states the skill name twice and its category without explaining what it actually does (e.g., generates JSON task definitions, configures container settings, sets resource limits). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the skill name and barely addresses 'when should Claude use it' — the triggers section just repeats the skill name. There is no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the exact skill name repeated twice ('ecs task definition creator'). It lacks natural user keywords like 'ECS', 'task definition', 'container definition', 'Fargate', 'Docker', 'AWS ECS', or phrases users might say like 'create a task def' or 'define ECS containers'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'ECS task definition' provides some specificity within the AWS domain, making it somewhat distinguishable from other AWS skills. However, the lack of detail about what it does versus other ECS-related skills (e.g., ECS service creation, ECS cluster management) creates potential overlap risk. | 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 an empty placeholder with no actual content. It contains only generic boilerplate text that repeats the skill name without providing any ECS task definition JSON examples, AWS CLI commands, IAM role configurations, container definitions, or any other actionable guidance. It fails on every dimension of the rubric.
Suggestions
Add a concrete, copy-paste-ready ECS task definition JSON example with common fields (containerDefinitions, cpu, memory, networkMode, executionRoleArn) and an equivalent AWS CLI command to register it.
Include a clear multi-step workflow: 1) Define container requirements, 2) Create IAM execution/task roles, 3) Write the task definition JSON, 4) Register with `aws ecs register-task-definition`, 5) Validate with `aws ecs describe-task-definition`.
Remove all generic filler text ('This skill provides automated assistance...', 'Provides step-by-step guidance...') and replace with actual patterns for Fargate vs EC2 launch types, logging configuration, and secrets management.
Add references to related resources like IAM role templates, CloudWatch log group setup, and common pitfalls (e.g., missing execution role permissions, incorrect network mode for Fargate).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It repeats 'ecs task definition creator' numerous times without providing any actual guidance, code, or configuration examples. Every line is generic boilerplate that could apply to any skill. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No ECS task definition JSON, no AWS CLI commands, no Terraform/CloudFormation snippets, no container definitions—nothing actionable whatsoever. It only describes what it claims to do without actually doing it. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. The skill claims to provide 'step-by-step guidance' but contains no steps, no sequence, and no validation checkpoints for creating an ECS task definition. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic placeholder text with no meaningful structure, no references to detailed resources, and no navigation to related documentation or examples. | 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
4dee593
- 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.