drivers-ticket-assistant
Help the user understand and complete their assigned DOCSP tickets for drivers. Provides a prioritized overview of all assigned tickets and suggests next steps. Use only when the user explicitly uses the slash command.
59
68%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/drivers-ticket-assistant/SKILL.mdQuality
Discovery
59%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 adequately communicates what the skill does and when to use it, with a clear and distinctive scope around DOCSP driver tickets. However, the actions described are somewhat vague ('understand and complete', 'suggests next steps'), and the reliance on a slash command means there are no natural language trigger terms for discoverability. The specificity of capabilities could be improved by listing concrete actions like triaging, summarizing ticket requirements, or generating documentation drafts.
Suggestions
Add more specific concrete actions, e.g., 'triages assigned DOCSP tickets by priority, summarizes ticket requirements, and drafts documentation changes for driver pages'.
Include natural trigger terms even if slash-command-activated, e.g., mention 'DOCSP', 'driver documentation tickets', 'Jira tickets', 'assigned tickets' so Claude can better match context.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (DOCSP tickets for drivers) and some actions ('prioritized overview', 'suggests next steps'), but the actions are somewhat vague—'understand and complete' is generic, and 'suggests next steps' lacks concrete detail about what those steps entail. | 2 / 3 |
Completeness | It answers both 'what' (understand and complete DOCSP tickets, provides prioritized overview, suggests next steps) and 'when' (only when the user explicitly uses the slash command). The trigger condition is explicit, even though it's a slash command rather than natural language. | 3 / 3 |
Trigger Term Quality | The description says 'Use only when the user explicitly uses the slash command' which means it relies on a slash command rather than natural language triggers. There are no natural keywords a user would say—'DOCSP tickets' is internal jargon, and no common variations or natural phrases are provided. | 1 / 3 |
Distinctiveness Conflict Risk | The skill is clearly scoped to DOCSP tickets for drivers and is triggered only by an explicit slash command, making it very unlikely to conflict with other skills or trigger incorrectly. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
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 strong, highly actionable skill that provides specific CLI commands, clear decision trees, and well-structured workflows for managing Jira tickets. Its main weakness is that the content is somewhat long for a single SKILL.md and could benefit from splitting detailed per-status logic into referenced files. The priority ordering and status-based branching logic are excellent and provide Claude with clear, unambiguous guidance.
Suggestions
Consider splitting the detailed per-status action logic (Reviews, Backlog, In Progress, Blocked) into a separate reference file to keep SKILL.md as a concise overview with pointers.
Remove the opening 'You are a Jira ticket assistant...' paragraph — this is role framing that Claude doesn't need repeated in the body when the skill description already covers it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary framing ('You are a Jira ticket assistant...') and could be tightened in places. The priority order section and detailed review logic are appropriately detailed for the complexity of the task, but some phrasing is slightly verbose. | 2 / 3 |
Actionability | The skill provides specific, executable commands (gh search prs, gh pr view with JSON flags, gh api calls with exact endpoints), concrete classification heuristics (20 commits = internal), and detailed decision trees for each ticket status. The guidance is highly specific and actionable. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced (Step 1: Overview → Step 2: Category/Ticket Actions) with well-defined branching logic for each status category. Each branch includes specific conditions and corresponding actions, forming implicit validation loops (e.g., check review status → determine action → suggest follow-up). The priority ordering is explicit and well-structured. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and subsections, but it's a fairly long monolithic document that could benefit from splitting detailed per-status logic into separate files. References to external resources (Confluence wiki pages) are present and well-signaled, but there are no bundle files to offload complexity to. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- mongodb/docs
- Commit
5985af5
- 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.