ecs-task-definition-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill ecs-task-definition-creatorEcs 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.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely lacking in detail and usefulness. It essentially just restates the skill name without explaining what creating an ECS task definition involves, what specific capabilities are offered, or when Claude should select this skill. The duplicate trigger term and lack of natural language variations make it unlikely to be selected appropriately.
Suggestions
Add specific actions the skill performs, e.g., 'Creates AWS ECS task definitions with container configurations, resource limits, networking settings, and IAM role assignments'
Add a 'Use when...' clause with natural trigger terms like 'create ECS task', 'Fargate container', 'Docker on AWS', 'container definition', 'task def JSON'
Include common use cases or scenarios, e.g., 'Use when deploying containerized applications to AWS ECS/Fargate or when the user needs help configuring container resources, port mappings, or environment variables'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Ecs Task Definition Creator') without describing any concrete actions. It doesn't explain what creating a task definition involves or what specific capabilities it offers. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. There's no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('ecs task definition creator'). Missing natural variations users might say like 'create ECS task', 'task def', 'container definition', 'Fargate task', or 'Docker container config'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'ECS task definition' is somewhat specific to AWS ECS, but without describing what actions it performs, it could overlap with other AWS-related skills. The 'AWS Skills' category mention provides some context. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content about ECS task definitions. It contains only generic placeholder text that could apply to any skill topic. There is no actionable guidance, no code examples, no AWS-specific information, and no value added beyond what the skill's title already conveys.
Suggestions
Add a concrete, executable example of a minimal ECS task definition JSON with required fields (family, containerDefinitions, cpu, memory)
Include a step-by-step workflow: 1) Define container specs, 2) Set resource limits, 3) Configure IAM task role, 4) Validate with `aws ecs register-task-definition --cli-input-json`
Provide specific guidance on common patterns: Fargate vs EC2 launch types, sidecar containers, secrets management with AWS Secrets Manager
Add references to detailed documentation for advanced topics like service discovery, logging configuration, and health checks
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual ECS task definition information. | 1 / 3 |
Actionability | Contains zero concrete guidance - no code, no commands, no actual task definition examples, no JSON schemas, no container definitions. It describes what the skill supposedly does without providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Creating ECS task definitions involves multiple steps (container definitions, resource allocation, IAM roles, networking) but none are mentioned or sequenced. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no links to examples, no separation of quick-start from advanced topics. The content is both monolithic and empty. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.