CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

github-pr-query

Query GitHub pull requests with jq filtering and reusable selectors.

Quality

69%

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 ./.github/skills/github-pr-query/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 highly actionable, with concrete executable jq examples and an unambiguous single-step workflow. Weaknesses are the missing query-prs.sh script in the bundle, repeated statements of the --jq-optional behavior, and filler sections that could be trimmed.

Suggestions

Ship the referenced script (e.g. scripts/query-prs.sh) in the bundle or replace './query-prs.sh' invocations with the actual 'gh' commands so examples are executable as delivered.

State the '--jq is optional / schema-first' behavior once (the dedicated section) and remove the duplicate comment and options-list repetition.

Merge the thin 'Output Format' section into Usage and trim the Requirements line about jq being preinstalled.

DimensionReasoningScore

Conciseness

Mostly efficient — the bulk is executable examples — but the '--jq is optional' point is repeated three times (its own section, the basic-query comment, and the options list), the 'Output Format' section is thin filler, and 'jq (installed by default on most systems)' pads the Requirements. Fits 'mostly efficient but could be tightened'; not 4 because the repetition goes beyond minor trimmable instances.

3 / 5

Actionability

Every example is a copy-paste-ready command with concrete jq filters covering common cases (state, author, counts, review decision, labels). Not 5 because the target of every example, './query-prs.sh', is absent from the bundle, so the commands are not executable as shipped; not 3 because everything written is specific and complete.

4 / 5

Workflow Clarity

A simple single-purpose skill where the single action (run query-prs.sh with options) is unambiguous, satisfying the simple-skill exception. The schema-first pattern (run without --jq to inspect structure, then a targeted query) acts as an implicit checkpoint, and the operation is read-only so no validation cap applies.

5 / 5

Progressive Disclosure

The body is well-organized with clear sections, but the only bundle reference it makes — './query-prs.sh', invoked throughout — does not exist in the bundle (no scripts/ directory), so navigation to the actual tool is broken. Scored 3 rather than 4 because a broken primary reference is more than a minor organization gap; not 2 because the in-file structure itself is good.

3 / 5

Total

15

/

20

Passed

Description

53%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 states a clear, concrete 'what' in third person, but omits any 'Use when...' trigger guidance and misses the common 'PRs'/'PR' synonym. It is reasonably distinct from other skills thanks to the jq-filtering angle.

Suggestions

Add an explicit trigger clause, e.g. 'Use when querying or listing pull requests/PRs, analyzing PR metadata, or filtering PR data with jq.'

Include natural synonyms users actually say — 'PRs', 'PR', 'pull request list' — alongside 'pull requests' for better trigger coverage.

Make 'reusable selectors' concrete or drop it (e.g. 'filter by state, author, review decision, and labels').

DimensionReasoningScore

Specificity

Names the domain ('GitHub pull requests') and one concrete action ('query... with jq filtering'), but 'reusable selectors' is vague and no further specific actions are listed. Not 4 because it doesn't enumerate several concrete actions; not 2 because the 'what' is concrete rather than generic.

3 / 5

Completeness

A clear 'what' is present ('Query GitHub pull requests with jq filtering and reusable selectors'), but there is no 'when' / 'Use when...' clause, which caps completeness at 3 per the rubric guideline. Not 4 because the 'when' is entirely absent rather than merely weak.

3 / 5

Trigger Term Quality

Relevant keywords are present ('GitHub', 'pull requests', 'jq', 'filtering'), but the natural synonym users most commonly say — 'PRs' / 'PR' — is missing. Fits anchor 3: some relevant keywords but missing common variations.

3 / 5

Distinctiveness Conflict Risk

'GitHub pull requests with jq filtering' carves a fairly distinct niche with low overlap risk against non-PR skills, though it could collide with general GitHub or code-review skills. Fits 'mostly distinct; minor overlap risk with closely related skills'; not 5 because the trigger set isn't fully distinctive.

4 / 5

Total

13

/

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

github/gh-aw

Path

.github/skills/github-pr-query/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.