CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-blocker-summarizer

Summarizes open pull requests into a blockers-first standup digest. Activates when the user asks to summarize open PRs, find blocked pull requests, generate a PR standup, or triage review backlog from a PR export.

69

Quality

85%

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

87%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 body is concise, executable, and well-structured with a real referenced script. Its main weakness is workflow clarity: it processes a batch export without an in-flow validation checkpoint, instead documenting validation gaps in Gotchas and offloading filtering to the user.

Suggestions

Add an explicit pre-run validation step (e.g., a check that all PRs have state==open and numeric age_days, or a --strict flag that errors on missing fields) so the workflow has a real checkpoint rather than offloading validation to the user.

Surface a digest-level signal when a guard silently skipped (e.g., include a "warnings" or "skipped_checks" array noting non-numeric age_days) so the output reveals that a check did not run.

Reconcile the summary line with the documented vanishing-PR gotcha by either adding an "uncategorized" count or explicitly stating the remainder, turning the current caveat into a verified output property.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and never explains concepts Claude already knows; every section (Input, Run, Gotchas, Anti-goals) earns its place.

5 / 5

Actionability

Provides a copy-paste-ready command (verified the referenced scripts/run_pipeline.py exists), a concrete input schema with field values, and an explicit output JSON shape covering the common case.

5 / 5

Workflow Clarity

Although the single action is unambiguous, this batch operation over a PR export lacks an in-workflow validation checkpoint and the Gotchas explicitly delegate validation to the user (e.g., "Filter the export before running"); per the batch-operation cap, workflow clarity cannot exceed 3.

3 / 5

Progressive Disclosure

Under 50 lines with well-organized sections and a single one-level-deep reference to a real bundled script (scripts/run_pipeline.py), matching the well-organized simple-skill anchor.

5 / 5

Total

18

/

20

Passed

Description

82%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 well-formed: it concisely states the skill's purpose and gives multiple explicit natural-language triggers. It is distinctive and low conflict-risk; the only gap is that it names a single consolidated action rather than enumerating several specific capabilities.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ("Summarizes open pull requests into a blockers-first standup digest") but does not enumerate multiple specific actions, matching the '1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

Explicitly states both what it does (blockers-first standup digest) and when to use it ("Activates when the user asks to..." with concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

Provides several natural phrases users would say ("summarize open PRs", "find blocked pull requests", "generate a PR standup", "triage review backlog") with good synonym coverage, though a few additional natural variations are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (PR triage from an exported list) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository
FrancyJGLisboa/agent-skills-platform
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.