CtrlK
BlogDocsLog inGet started
Tessl Logo

triage-reviews

Fetch PR review comments, verify each against real code/docs, fix valid issues, commit and push

66

Quality

80%

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 ./.agents/skills/triage-reviews/SKILL.md
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.

The content is highly actionable and workflow-clear, with strong validation checkpoints and feedback loops for a batch/destructive operation. Progressive disclosure and conciseness are good but have minor room to trim prose or offload long scripts.

DimensionReasoningScore

Conciseness

The body is action-oriented with executable commands and mostly justified prose (GraphQL-only thread resolution, page-size cap), but the redundant opening sentence and meta-commentary like 'The skill must close that loop' could be trimmed, sitting just below the lean level-5 anchor.

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands — `gh pr view --json number --jq .number`, `gh api --paginate`, a complete GraphQL query, and bash reply/resolve scripts — with clearly templated variables, matching the level-5 anchor.

5 / 5

Workflow Clarity

Clear phased sequence (Gather → Verify → Fix/Ship → Reply/Resolve → Report) with explicit validation (read actual code, lint/test gate before commit) and feedback loops (fix failures, or skip-and-report as 'Valid (unfixed)'), matching the level-5 anchor.

5 / 5

Progressive Disclosure

Well-organized single-file skill with clear phase headers and no external references needed; the long GraphQL/bash blocks are inlined but justified as core workflow steps, leaving a minor organization gap versus the cleanly-split level-5 anchor.

4 / 5

Total

18

/

20

Passed

Description

71%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 concrete and action-rich with a distinct niche, but lacks an explicit 'Use when...' trigger clause, which caps completeness at 3. Trigger term coverage is good but could add synonyms like 'feedback'.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when triaging PR review feedback, responding to reviewer comments, or addressing Copilot/Greptile findings on a pull request.'

Include the synonym 'feedback' (e.g. 'PR review comments/feedback') to broaden natural trigger terms.

Optionally name the reviewer sources (Copilot, Greptile, human) in the description to sharpen distinctiveness.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Fetch PR review comments, verify each against real code/docs, fix valid issues, commit and push' — covering the full triage workflow comprehensively, matching the level-5 anchor.

5 / 5

Completeness

The 'what' is clearly stated (fetch/verify/fix/commit/push) but there is no 'Use when...' clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

'PR review comments' is the natural phrase users would say, giving good keyword coverage, but synonyms like 'feedback' or 'review feedback' are missing, so it sits just below the comprehensive level-5 anchor.

4 / 5

Distinctiveness Conflict Risk

PR review triage is a clear, specific niche with minimal conflict risk, though minor overlap could occur with generic commit/push or code-review skills, keeping it just below the level-5 anchor.

4 / 5

Total

16

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
stickerdaniel/linkedin-mcp-server
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.