CtrlK
BlogDocsLog inGet started
Tessl Logo

iikit-08-taskstoissues

Convert tasks from tasks.md into GitHub Issues with labels and dependencies. Use when exporting work items to GitHub, setting up project boards, or assigning tasks to team members.

83

1.74x
Quality

92%

Does it follow best practices?

Impact

82%

1.74x

Average score across 14 eval scenarios

SecuritybySnyk

—

The risk profile of this skill

The canonical home for this skill is tessl-labs/intent-integrity-kit

SKILL.md
Quality
Evals
Security

Quality

Content

85%Scale 1-3

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 strong actionability and workflow clarity. It provides concrete commands, clear sequencing with validation gates, and appropriate error handling for a multi-step process involving external API calls. Minor verbosity in the prerequisites section and some boilerplate directives slightly reduce token efficiency, but overall the content is effective and well-organized.

Suggestions

Remove the 'You MUST consider the user input before proceeding (if not empty)' directive — Claude can infer this from the $ARGUMENTS block, saving tokens.

DimensionReasoningScore

Conciseness

Generally efficient but includes some unnecessary scaffolding like the 'You MUST consider the user input' directive and the verbose prerequisites/selection flow. The Windows alternatives add bulk but are arguably necessary for cross-platform support.

2 / 3

Actionability

Provides concrete, executable bash commands throughout (gh issue create, git config, script paths). The title format, label specifications, and issue body template reference are specific and actionable. Parallel dispatch instructions are clear.

3 / 3

Workflow Clarity

Clear sequential flow with explicit validation checkpoints: prerequisites check, GitHub remote validation before proceeding, verification that all subagents returned successfully, and graceful partial failure handling. The error handling table provides explicit feedback loops for each failure mode.

3 / 3

Progressive Disclosure

Appropriately references external files (issue-body-template.md, conversation-guide.md) for detailed content while keeping the main skill as an overview. References are one level deep and clearly signaled with relative links.

3 / 3

Total

11

/

12

Passed

Description

100%Scale 1-3

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 is a well-crafted skill description that clearly communicates what the skill does and when to use it. It uses third person voice, includes specific concrete actions, and provides natural trigger terms that users would actually say. The description is concise yet comprehensive, with a distinct niche that minimizes conflict risk.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: converting tasks from tasks.md, creating GitHub Issues, adding labels, handling dependencies. These are clear, actionable capabilities.

3 / 3

Completeness

Clearly answers both what ('Convert tasks from tasks.md into GitHub Issues with labels and dependencies') and when ('Use when exporting work items to GitHub, setting up project boards, or assigning tasks to team members') with explicit trigger guidance.

3 / 3

Trigger Term Quality

Includes strong natural trigger terms users would say: 'tasks.md', 'GitHub Issues', 'labels', 'dependencies', 'project boards', 'assigning tasks', 'exporting work items'. Good coverage of how users would phrase these requests.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: the combination of tasks.md as a source format and GitHub Issues as the target, along with specific actions like labels and dependencies, makes this unlikely to conflict with other skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
JaviMontano/jm-adk
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.