CtrlK
BlogDocsLog inGet started
Tessl Logo

run-maintenance-task

Use this skill to execute a task from the Android Agentic Maintenance Backlog. Invoke when the user provides an Asana task URL from that backlog and asks to run, start, execute, or work on it. Also invoke when the user says things like "run the next maintenance task", "work on this backlog item", or "pick up a maintenance task". Requires the Asana MCP to be configured.

74

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

An exceptionally actionable, lean, and well-sequenced workflow with strong validation feedback loops; its single weak spot is progressive disclosure, as all content is inline with no reference files to offload detail.

Suggestions

Extract the longer reusable blocks (e.g. the PR template fill-in mapping and the e2e trigger command list) into a reference file such as references/PR_GUIDE.md, then link to it from the body to add one-level-deep progressive disclosure.

Keep the core workflow steps inline in SKILL.md as the overview so navigation stays shallow and clearly signaled.

DimensionReasoningScore

Conciseness

Lean and directive throughout, packed with exact commands and assuming Claude's competence; it explains no concepts Claude already knows and nearly every line earns its place.

3 / 3

Actionability

Provides fully executable git worktree, gradle, and gh api commands with concrete REST-API fallbacks, PR title format, and template fill-in instructions — copy-paste ready.

3 / 3

Workflow Clarity

Clear sequenced sections (Before you start, Implement, Verify, Open draft PR, If stuck) with an explicit validate→fix→re-run feedback loop and a recovery branch for blockers; validation is prominent so no cap applies.

3 / 3

Progressive Disclosure

Well-organized into clearly headed sections but entirely single-file at ~90 lines with no file-level references; at over 50 lines the simple-skill carve-out does not apply and there is no progressive disclosure via bundle references.

2 / 3

Total

11

/

12

Passed

Description

90%

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

A strong description with explicit, natural trigger phrasing, a clear niche, and complete what/when coverage; its only weakness is relying on a single generic action verb rather than enumerating concrete capabilities.

Suggestions

Replace the single verb "execute a task" with a few concrete actions the skill performs (e.g. "fetch the Asana task, implement the change in a git worktree, run validation, and open a draft PR") to reach anchor 3 on specificity.

Consider naming the outcome explicitly (e.g. "...and open a draft PR for review") so the capability is concrete rather than implied.

DimensionReasoningScore

Specificity

Names the domain concretely ("Android Agentic Maintenance Backlog", "Asana task URL") but offers only a single generic action verb ("execute a task") rather than multiple specific concrete actions, so it sits at anchor 2 rather than 3.

2 / 3

Completeness

Explicitly states what it does ("execute a task from the Android Agentic Maintenance Backlog") and when to invoke with explicit triggers, satisfying the anchor 3 bar for both what and when.

3 / 3

Trigger Term Quality

Gives good coverage of natural user phrasings ("run the next maintenance task", "work on this backlog item", "pick up a maintenance task", and "run, start, execute, or work on it"), matching the anchor 3 example of common variations.

3 / 3

Distinctiveness Conflict Risk

Tied to a specific named Asana backlog and its task URLs, creating a clear niche with distinct triggers unlikely to conflict with other skills.

3 / 3

Total

11

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
duckduckgo/Android
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.