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.

66

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/positron-intake-rotation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

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

The content is well-structured and highly actionable, with a clear daily workflow and good progressive disclosure to real reference files. It could be tightened by removing generic tone/collaboration advice Claude already knows.

Suggestions

Trim the 'Tone and Style' and 'Team Collaboration' sections to a few specific Positron-specific pointers, removing generic guidance Claude already knows.

Fill in the elided graphql query in the discussions example or point to the exact script line that contains it, so commands are fully copy-paste ready.

Consider adding a brief verification checkpoint in the daily workflow (e.g., confirm every queued item was either triaged, drafted, or handed off) to close the loop on batch intake processing.

DimensionReasoningScore

Conciseness

The body is mostly efficient procedural guidance, but sections like 'Tone and Style' ('Be welcoming: Thank contributors...') and 'Team Collaboration' offer generic soft advice Claude already knows and could be trimmed.

3 / 5

Actionability

Concrete named scripts with usage, executable gh command examples, specific URLs, and named team members to learn from; minor gaps such as the elided graphql query ('...') keep it just short of fully copy-paste ready.

4 / 5

Workflow Clarity

The 'Daily Intake Process' is a clear six-step numbered sequence with a 'Present draft to user for review before posting' checkpoint; the skill is explicitly non-destructive so the missing-validation cap does not apply, though error-recovery feedback loops are absent.

4 / 5

Progressive Disclosure

The body is an overview that clearly signals one-level-deep references to real files (references/intake_workflow.md, references/response_examples.md) and four scripts, with a Quick Start section organizing them for easy navigation.

5 / 5

Total

16

/

20

Passed

Description

87%Weight 40%Scale 1-5

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 clear, specific, and answers both what the skill does and when to use it with concrete trigger phrases. It is narrowly scoped to a distinct niche, giving it low conflict risk.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'reviewing and organizing new issues, responding to discussions, handling support tickets, and searching for related content' — but omits explicit mention of labeling/categorization, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly states what the skill does ('provides workflows for...') and when to use it ('Use this skill when on intake rotation duty, when helping someone with intake tasks, or when learning the intake rotation process') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural audience-specific triggers like 'on intake rotation duty', 'intake tasks', and 'learning the intake rotation process' are present, though a few synonymous phrasings a user might say are missing.

4 / 5

Distinctiveness Conflict Risk

Scoped to 'issue intake rotation duties for the Positron repository', a clear internal niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

18

/

20

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.