CtrlK
BlogDocsLog inGet started
Tessl Logo

create-invoke-task

Create a new Python invoke task for the dda CLI

49

Quality

55%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/create-invoke-task/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured skill with a clear workflow for creating invoke tasks. Its main strength is the concise, well-sequenced steps that guide Claude through information gathering, reference reading, implementation, and verification. The primary weakness is the lack of a concrete, executable code example showing a complete task definition, which would make the skill more immediately actionable.

Suggestions

Add a complete, copy-paste-ready code example of a task definition with parameters (e.g., a minimal @task function with ctx, a string param, and ctx.run()) to improve actionability.

Consider including a small inline template showing the exact import block and function signature pattern rather than just describing the conventions in prose.

DimensionReasoningScore

Conciseness

The content is lean and efficient. It doesn't explain what invoke is, what decorators are, or how Python imports work. Every section serves a clear purpose and assumes Claude's competence with Python tooling.

3 / 3

Actionability

The skill provides clear steps and references specific files to read, but lacks executable code examples for the task definition itself. It describes patterns ('use @task decorator', 'first param is ctx') rather than showing a complete, copy-paste-ready task template with parameters.

2 / 3

Workflow Clarity

The 5-step workflow is clearly sequenced with logical progression: gather info → read reference → create task → register if needed → verify. The verification step with a concrete bash command serves as a validation checkpoint, and the conditional registration step (Step 4) handles branching cleanly.

3 / 3

Progressive Disclosure

The skill references specific files to read (tasks/auth.py, tasks/agent.py, tasks/__init__.py) which is good progressive disclosure to the codebase. However, with no bundle files provided, there are no supporting reference documents, and the skill inlines all content in a single file which works for this length but could benefit from a template file reference.

2 / 3

Total

10

/

12

Passed

Description

32%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is terse and narrowly scoped, identifying a specific tool (dda CLI) and framework (Python invoke) but failing to provide explicit trigger guidance or elaborate on the concrete actions involved. It lacks a 'Use when...' clause, which is critical for skill selection, and does not cover enough natural trigger terms to reliably match user requests.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to add a new command, task, or subcommand to the dda CLI using Python invoke.'

Include additional trigger terms and variations such as 'pyinvoke', 'tasks.py', 'dda command', 'CLI task', 'new subcommand'.

Expand the capability description with more concrete actions, e.g., 'Scaffolds a new invoke task file, registers it in the task namespace, and adds argument parsing for the dda CLI.'

DimensionReasoningScore

Specificity

Names a specific domain (Python invoke task for dda CLI) and one action (create), but does not list multiple concrete actions or elaborate on what creating such a task entails.

2 / 3

Completeness

Describes what it does (create a new Python invoke task) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also minimal, warranting a 1.

1 / 3

Trigger Term Quality

Includes relevant keywords like 'Python', 'invoke task', and 'dda CLI' that a user familiar with the project might use, but misses common variations or synonyms (e.g., 'pyinvoke', 'tasks.py', 'command', 'new task').

2 / 3

Distinctiveness Conflict Risk

The mention of 'dda CLI' and 'invoke task' provides some specificity, but 'create a new Python' could overlap with general Python scaffolding or CLI-related skills. It's somewhat distinctive but not clearly delineated.

2 / 3

Total

7

/

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.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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

Repository
DataDog/datadog-agent
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.