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.

Quality

62%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/drivers-ticket-assistant/SKILL.md

Quality

Content

64%

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

This is a solid, highly actionable skill with concrete commands, specific heuristics, and useful draft messages. Its main weaknesses are moderate verbosity (the detailed per-status instructions make the file long) and the absence of validation/error-handling checkpoints in a workflow that chains multiple API calls. Splitting detailed status-specific guidance into referenced files would improve both conciseness and progressive disclosure.

Suggestions

Add explicit validation checkpoints after key API calls (e.g., verify gh search found the correct PR before proceeding, handle cases where the Jira changelog is empty or the API returns an error).

Extract the detailed per-status action guides (Reviews, Backlog, In Progress, Blocked) into separate referenced files to keep SKILL.md as a concise overview with clear navigation links.

Tighten the reviewer classification section — the heuristic (20 commits = internal, <10 = external) can be stated in one line rather than a full paragraph.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient and avoids explaining concepts Claude already knows, but some sections are verbose — e.g., the detailed reviewer classification heuristic and the repeated Confluence wiki references could be tightened. The priority order list is clear but lengthy.	2 / 3
Actionability	The skill provides specific, executable commands (gh search prs, gh pr view with JSON flags, gh api calls, Jira REST API with expand=changelog), concrete classification heuristics (20 commits = internal), and even draft message templates. Guidance is highly concrete and copy-paste ready.	3 / 3
Workflow Clarity	The two-step workflow (Overview → Category/Ticket Actions) is clear, and each status category has well-defined decision trees. However, there are no explicit validation checkpoints — e.g., no verification that the gh search actually found the right PR, no fallback if the Jira API call fails, and no feedback loops for error recovery in what are multi-step API-dependent operations.	2 / 3
Progressive Disclosure	The content is well-structured with clear headers and subsections, but it's a monolithic file with no references to supporting files. The detailed per-status logic (Reviews, Backlog, In Progress, Blocked) could be split into separate reference files to keep the main skill lean, especially given the length.	2 / 3
	Total	9 / 12 Passed

Description

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 clearly defines when to use the skill (slash command only) and occupies a distinct niche around DOCSP driver tickets, which minimizes conflict risk. However, the actual capabilities described are somewhat vague ('understand and complete', 'suggests next steps'), and the reliance on a slash command rather than natural language means trigger term quality is poor for keyword-based skill selection.

Suggestions

Add more specific concrete actions, e.g., 'Summarizes ticket requirements, identifies blocking dependencies, drafts documentation changes, and tracks completion status for DOCSP driver tickets.'

Even though it's slash-command triggered, include natural language trigger terms like 'ticket triage', 'driver documentation', 'DOCSP backlog' so Claude can better match if users describe the task in conversation.

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	The description 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 if unconventional.	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. Terms like 'DOCSP tickets' and 'drivers' are domain-specific jargon, and there are no natural keywords a user would say in conversation to trigger this skill.	1 / 3
Distinctiveness Conflict Risk	The combination of 'DOCSP tickets for drivers' and the slash-command-only trigger makes this highly distinctive and unlikely to conflict with other skills. It occupies a very specific niche.	3 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

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: be9d4af

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.