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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

80%

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

The body is a lean, highly actionable operational playbook with concrete commands and clear status-based branches. Its main gaps are the absence of explicit validation/error-recovery checkpoints in the workflow and no progressive disclosure into separate reference files.

Suggestions

Add explicit validation/fallback checkpoints, e.g. 'If gh search prs returns no PR, also search docs-shared and docs-node; if still none, ask the user for the PR link' and a retry loop for failed API calls.

Split the detailed per-status review logic (reviewer classification heuristic, wiki tech-review process) into a references/ file (e.g. REVIEW_WORKFLOW.md) and link to it from SKILL.md to improve progressive disclosure and keep the overview lean.

Dimension	Reasoning	Score
Conciseness	The body is dense, domain-specific operational instruction (priority ordering, review-classification heuristic, exact gh/Jira API commands) that assumes Claude's competence without explaining what Jira, PRs, or commits are; the opening sentences mildly restate the description but overall every token earns its place.	3 / 3
Actionability	It supplies copy-paste-ready commands with concrete parameters ('gh search prs "<ticket key>"', 'gh pr view <number> --json reviewRequests,reviews', 'gh api "repos/10gen/docs-mongodb-internal/commits?author=<login>&per_page=20"', '?expand=changelog') plus numeric thresholds and drafted message templates, matching the fully-executable anchor.	3 / 3
Workflow Clarity	Steps are clearly sequenced (Step 1 overview, Step 2 per-status branches) with conditional decision logic, but there are no explicit validation checkpoints or error-recovery feedback loops (e.g., what to do when 'gh search prs' returns no PR), fitting 'steps listed but validation gaps; checkpoints missing or implicit'.	2 / 3
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent) and the body is a single monolithic document; sectioning is good but detailed per-status logic that could live in a reference file is inline, matching 'some structure but content that should be separate is inline'.	2 / 3
	Total	10 / 12 Passed

Description

75%

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 answers both what it does and when to invoke it, with a distinct, slash-command-gated niche. It is held back from a perfect score by somewhat generic action verbs and a lack of natural-language trigger variations beyond the slash command.

Suggestions

Replace generic verbs ('understand and complete', 'suggests next steps') with more specific concrete actions (e.g., 'ranks assigned tickets by review-readiness, drafts reviewer follow-up messages, and identifies blocked tickets').

Add natural-language trigger terms a user might say (e.g., 'Use when the user asks what driver docs ticket to work on next or wants to triage their DOCSP backlog'), not only the slash-command trigger.

Dimension	Reasoning	Score
Specificity	Names the domain ('DOCSP tickets for drivers') and several actions ('understand and complete', 'Provides a prioritized overview', 'suggests next steps'), but these are broad rather than a list of multiple distinct concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It states what the skill does ('understand and complete their assigned DOCSP tickets', 'prioritized overview', 'suggests next steps') and gives an explicit when clause ('Use only when the user explicitly uses the slash command'), satisfying both what and when; it is not a 2 because the trigger is explicit rather than implied.	3 / 3
Trigger Term Quality	It includes relevant domain keywords ('DOCSP tickets', 'assigned tickets', 'drivers') but the only trigger guidance is 'Use only when the user explicitly uses the slash command', offering no natural-language variations a user would say, fitting 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The narrow 'DOCSP tickets for drivers' niche plus a slash-command-only invocation trigger make it clearly distinguishable and unlikely to fire for the wrong skill, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: mongodb/docs
Commit: e765459

Reviewed: about 23 hours 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.