CtrlK
BlogDocsLog inGet started
Tessl Logo

positron-intake-rotation

This skill should be used when handling issue intake rotation duties for the Positron repository. It provides workflows for reviewing and organizing new issues, responding to discussions, handling support tickets, and searching for related content. Use this skill when on intake rotation duty, when helping someone with intake tasks, or when learning the intake rotation process.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The body is highly actionable and well-structured with real, one-level-deep bundle references, but it leans verbose through generic tone coaching and repeated safety warnings, and lacks an explicit outcome-verification feedback loop for the batch/destructive GitHub modifications.

Suggestions

Tighten conciseness by replacing the generic "Tone and Style" section (Be welcoming/clear/helpful/realistic/professional) with a pointer to response_examples.md, and consolidate the repeated NEVER-execute warnings into the single CRITICAL protocol so the others just reference it.

Add an explicit verification step to the Core Workflow after user execution, e.g. a checkpoint where the assistant re-checks that the applied label/status change took effect before marking the item triaged, to close the feedback loop for the batch/destructive operations.

Collapse the Workflow Summary block, which restates the same 8 steps already detailed in "Daily Intake Process", into a one-line pointer or remove it to reduce token overhead.

DimensionReasoningScore

Conciseness

Mostly efficient and domain-specific, but the generic "Tone and Style" coaching ("Be welcoming", "Be clear", "Be helpful", "Be realistic", "Be professional") restates guidance Claude already knows, and the NEVER-execute warning is repeated across the CRITICAL section, CLI section, and Workflow Summary.

2 / 3

Actionability

Provides concrete named scripts with usage, executable `gh` commands (e.g. `gh issue view <number> --repo posit-dev/positron --comments`), ready-to-draft modification commands, and specific URLs/team handles — copy-paste ready.

3 / 3

Workflow Clarity

The daily intake process is a clearly numbered 1–6 sequence with a draft-for-review checkpoint, but there is no explicit post-action verification loop (e.g. confirm a label was applied or an issue closed), so the batch/destructive GitHub operations trigger the rubric's cap at 2.

2 / 3

Progressive Disclosure

Clear overview with well-signaled one-level-deep references to `references/intake_workflow.md` and `references/response_examples.md` (both verified present), plus four named scripts; detailed workflows are appropriately offloaded rather than nested.

3 / 3

Total

10

/

12

Passed

Description

100%

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 is specific, trigger-rich, and complete, clearly stating both what the skill does and when to invoke it within a well-scoped niche. It uses third person and mirrors the structure of the rubric's good examples.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: "reviewing and organizing new issues, responding to discussions, handling support tickets, and searching for related content" — beyond a single domain/action, matching the level-3 anchor.

3 / 3

Completeness

Explicitly answers both what (the listed workflows) and when via the "Use this skill when on intake rotation duty, when helping someone with intake tasks, or when learning the intake rotation process" trigger clause.

3 / 3

Trigger Term Quality

Natural phrases a team member would say are well covered: "intake rotation duty", "helping someone with intake tasks", and "learning the intake rotation process"; not jargon-only.

3 / 3

Distinctiveness Conflict Risk

Scoped to "issue intake rotation duties for the Positron repository" with distinct intake-rotation triggers, giving it a clear niche unlikely to fire for unrelated skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
posit-dev/positron
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.