CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

next-batch

Use when deciding what to work on next or what is already in flight — reading the OSN Platform project board's In Review, In Progress and Up Next columns, choosing a batch of issues for orchestrate, or checking that no other session holds an issue before anyone builds it.

Quality

88%

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

88%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.

An exceptionally dense, operational skill: executable commands with exact filters and payloads, a clearly sequenced workflow with strong validation and error-recovery checkpoints, and almost zero token waste on concepts Claude already knows. The main structural weakness is that the long shared Claim procedure is inlined rather than split into a reference file shared with orchestrate and new-feat, and a few long sentences in Step 2 hurt readability.

DimensionReasoningScore

Conciseness

Nearly every sentence carries project-specific, non-inferable knowledge (the shared GraphQL point budget, `gh project item-list` silent truncation, REST-vs-GraphQL rate-limit reporting), with no generic-concept padding. A few passages could be tightened — Step 2's ~160-word single sentence about draft PRs and owner answers is genuinely convoluted — keeping it at anchor 4 rather than 5's every-token-earns-its-place.

4 / 5

Actionability

Fully executable throughout: complete `gh api` commands with `--jq` filters, the exact board-fetch and claim-check pipelines, the exact PATCH payload and GraphQL queries for claiming, and a concrete example of the required output block. Parameters like `<Status field id>` and `<sha>` are each derived by a preceding command, so the guidance is copy-paste ready and covers the common cases — anchor 5.

5 / 5

Workflow Clarity

Steps 1–6 and Claim 1–5 are clearly sequenced with explicit validation checkpoints and feedback loops: re-reading held state because "The snapshot is stale by now", "Nothing runs between the check and the write", "Any other failed call ... means the answer is unknown: do not claim and do not dispatch", the invariant that every Up Next item appears under Batch/Queue/Skipped/Questions, and "Touch the card only while it still says In Progress". This matches anchor 5's explicit validation, error recovery, and checklists for a complex batch process.

5 / 5

Progressive Disclosure

The single file is well-organized with clear section headers, a triage decision table, and a mistakes table, making navigation easy — better than anchor 3's 'could be better organized'. However, there are no bundle files at all, and the ~70-line §Claim section is explicitly duplicated with the orchestrate and new-feat skills ("§Claim below is also the check orchestrate and new-feat run"), so that shared procedure arguably belongs in a referenced file rather than inlined — a minor organization gap that keeps it below anchor 5.

4 / 5

Total

18

/

20

Passed

Description

83%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.

A strong description: it pairs an explicit 'Use when' trigger clause with three concrete, project-specific capabilities, and its trigger terms are natural user phrasing. The only weaknesses are minor — a few uncovered behaviors and slight trigger overlap with the orchestrate/new-feat claim check.

DimensionReasoningScore

Specificity

Lists several concrete actions — "reading the OSN Platform project board's In Review, In Progress and Up Next columns", "choosing a batch of issues for orchestrate", "checking that no other session holds an issue" — with minor gaps in coverage (writing the orchestrate block, owner questions, and capacity planning are not mentioned). It exceeds anchor 3's '1-2 concrete actions' but falls short of anchor 5's comprehensive coverage of the skill's behaviors.

4 / 5

Completeness

Explicitly opens with "Use when deciding what to work on next or what is already in flight" (concrete when-triggers) and states the what concretely (reading board columns, choosing a batch, checking held issues). Both what and when are clearly and explicitly answered with concrete trigger phrases, matching anchor 5; anchor 4's 'when could be more specific' does not apply.

5 / 5

Trigger Term Quality

Natural phrases like "deciding what to work on next", "what is already in flight", "project board", and "batch of issues" match what a user on this project would say, plus named columns and the orchestrate handoff. A few natural variations (e.g. "pick tasks", "triage the board", "check the board") are missing, placing it at anchor 4 rather than 5's synonym-complete coverage.

4 / 5

Distinctiveness Conflict Risk

The OSN board triage/batch-selection niche is distinct with specific triggers, but "checking that no other session holds an issue before anyone builds it" overlaps with the claim checks that orchestrate and new-feat themselves run, so it could fire in those skills' contexts. This is anchor 4's 'minor overlap risk with closely related skills' rather than anchor 5's minimal conflict risk.

4 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

englishstreetventures/osn

Path

.claude/skills/next-batch/SKILL.md

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.