CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

prp-worklist

Render the open work of a repository as something worth looking at, so the maintainer can see what to take next. Deliberate invocation only — /prp-worklist.

Quality

71%

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 ./plugins/prp-core/skills/prp-worklist/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 exemplary in token efficiency and structure — a deliberately loose skill that trusts the model and wastes nothing. Its weakness is the executable middle: the reading step (which gh commands), the analysis mechanics, and the output shape are all left unspecified, leaving genuine ambiguity about how to perform the core of the task even accounting for the stated intent to stay loose.

Suggestions

Add the concrete reading step, e.g. `gh issue list` and `gh pr list` with the relevant --state/--limit flags, so the input-gathering is executable rather than implied.

Include one small example of an output grouping (e.g. a two-line sample of "Takeable now" vs "Blocked on a decision") as a starting point that still leaves shape open.

Spell out the execution order as a short numbered sequence (read → weigh → render → write to ~/.prp/<key>/ → report choices) so the workflow doesn't have to be reconstructed from prose.

DimensionReasoningScore

Conciseness

"Incubating. Deliberately underspecified." and "Read the tracker with `gh`. Then decide what is worth showing and how to show it." are maximally lean — no padded explanations, no concepts Claude already knows, every section earns its tokens. This matches the lean-and-efficient anchor exactly.

5 / 5

Actionability

Concrete anchors exist ("Read the tracker with `gh`", "write the file to this project's `~/.prp/<key>/` store and print a link", five specific considerations like "Blocked on a decision, or takeable now"), but the executable middle is missing: no gh commands, no example output, no grouping scheme. Some concrete guidance but incomplete matches anchor 3 rather than 4.

3 / 5

Workflow Clarity

A sequence is discernible (read tracker → weigh considerations → decide shape → write to store and offer link → report choices) but it is implicit across sections rather than stated as steps, with no checkpoints. Anchor 3 (sequence present but implicit/checkpoints missing) fits; not 4 because the order must be inferred, and the read-and-offer operation is not destructive so no cap applies.

3 / 5

Progressive Disclosure

The body is under 50 lines, needs no external references, and is well organized into clear sections (The job / What this maintainer cares about / Shape / Report your choices), meeting the simple-skill exception for a 5. The conditional "If a `helm-canvas` skill is available, follow it" is a clearly signaled pointer, not a buried reference.

5 / 5

Total

16

/

20

Passed

Description

58%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 has a clear niche and explicit invocation guidance, giving it strong distinctiveness and solid completeness. Its main weaknesses are vague capability language ("something worth looking at") and a near-total absence of the natural trigger terms (issues, PRs, backlog) a user would actually say.

Suggestions

Replace vague phrasing with concrete actions, e.g. "Lists and prioritizes a repository's open issues and pull requests into a what-to-take-next view for the maintainer."

Add natural trigger vocabulary — issues, pull requests, backlog, triage, what to work on next — even though invocation is deliberate-only, so the description still communicates scope.

State the concrete deliverable (a rendered artifact written to ~/.prp/<key>/ with a link) instead of "something worth looking at".

DimensionReasoningScore

Specificity

"Render the open work of a repository as something worth looking at" names the domain and a single action/outcome (a what-to-take-next view for the maintainer), but "something worth looking at" is soft and no specific actions are enumerated. It sits at the domain-plus-1-2-actions anchor rather than the several-specific-actions anchors.

3 / 5

Completeness

The what is stated (render open work as a maintainer's what-to-take-next view) and the when is explicit via "Deliberate invocation only — /prp-worklist", which is equivalent explicit trigger guidance, so the missing-use-when cap of 3 does not apply. Not a 5 because the what lacks concrete trigger phrasing and could be crisper.

4 / 5

Trigger Term Quality

Only generic keywords like "open work", "repository", and "maintainer" appear; the natural phrases a user would say ("issues", "pull requests", "backlog", "triage", "what should I work on next") are entirely absent. This matches the one-or-two-generic-keywords anchor, not the missing-synonyms anchor of 3.

2 / 5

Distinctiveness Conflict Risk

"Deliberate invocation only — /prp-worklist" removes auto-trigger conflict risk entirely, and the niche (a maintainer's prioritized view of open repo work) is clearly distinct. This matches the clear-niche-with-minimal-conflict anchor.

5 / 5

Total

14

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

Wirasm/prp

Path

plugins/prp-core/skills/prp-worklist/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.