scope-maintenance-task
Use this skill to interactively scope a maintenance idea into a properly formatted task for the Android Agentic Maintenance Backlog. Invoke when the user wants to add a task to the maintenance backlog, scope a new maintenance idea, or says things like "I want to add something to the backlog", "help me scope a maintenance task", or "can we add this as a maintenance item".
96
95%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%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-constructed description with excellent trigger terms and completeness, clearly stating both what the skill does and when to invoke it. The main weakness is that it uses second-person voice ('Use this skill') and the specificity of concrete actions could be improved by listing more of what the scoping process entails. The trigger phrases are natural and varied, and the niche is clearly defined.
Suggestions
Add more specific concrete actions beyond 'scope' — e.g., 'gathers context, estimates effort, assigns priority, and formats the task entry' to improve specificity.
Rephrase to third person voice (e.g., 'Interactively scopes a maintenance idea...' instead of 'Use this skill to interactively scope...') to follow the style guidelines.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Android Agentic Maintenance Backlog) and describes the action (interactively scope a maintenance idea into a properly formatted task), but doesn't list multiple concrete actions beyond scoping/formatting. | 2 / 3 |
Completeness | Clearly answers both 'what' (interactively scope a maintenance idea into a properly formatted task for the Android Agentic Maintenance Backlog) and 'when' (explicit 'Invoke when...' clause with multiple trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger phrases users would actually say: 'add a task to the maintenance backlog', 'scope a new maintenance idea', 'help me scope a maintenance task', 'add this as a maintenance item', and 'add something to the backlog'. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting the 'Android Agentic Maintenance Backlog' with distinct trigger terms around backlog scoping and maintenance tasks, making it unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%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-crafted interactive scoping skill that is concise, actionable, and clearly structured. It provides specific output requirements with concrete examples, includes validation checkpoints (the pre-creation checklist), and handles edge cases (unclear requirements, cross-module scope, unavailable tooling). The only minor note is that the Asana integration details (project GID, skill reference) are tightly coupled but appropriate for the use case.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and purposeful. Every section earns its place — it defines the interactive workflow, required output sections, and a pre-flight checklist without explaining concepts Claude already knows (like what Asana is or how Gradle works). | 3 / 3 |
Actionability | The skill provides concrete, specific guidance: exact required sections with clear acceptance criteria, a real example of validation commands, explicit fallback behavior (ddg-asana skill → Asana API), and a specific project GID. The checklist is directly actionable. | 3 / 3 |
Workflow Clarity | The 5-step interactive workflow is clearly sequenced, the required sections provide a structured output template, and the checklist serves as an explicit validation checkpoint before the final action (creating the Asana task). The [NEEDS INPUT] fallback provides error recovery for ambiguous cases. | 3 / 3 |
Progressive Disclosure | For a skill of this size and scope (~50 lines, single purpose), the content is well-organized with clear sections (workflow steps, required sections template, checklist). No bundle files are needed, and the structure is easy to navigate without external references. | 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
- duckduckgo/Android
- Commit
adccd8d
- 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.