CtrlK
BlogDocsLog inGet started
Tessl Logo

squash-bugbot

Triage unresolved bot review comments on a GitHub PR. Use when asked to run /squash-bugbot <PR_NUMBER> or to assess, fix, dismiss, reply to, or resolve bot review feedback.

94

1.17x
Quality

Does it follow best practices?

Impact

94%

1.17x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 with a clearly sequenced, well-validated multi-step workflow, but it is a long monolithic file with light redundancy between its safety sections and inline content that could be factored into references.

Suggestions

Consolidate the overlapping untrusted-input guidance between 'Trust Boundaries and Command Safety' and 'Safety Rules' into a single section to remove redundancy and save tokens.

Move the multi-line GraphQL query blocks and the bot-login allowlist into reference files (e.g. references/graphql-queries.md, references/bot-logins.md) with one-level-deep links from the body to improve progressive disclosure.

Tighten Step 5's filtering narrative into a compact checklist so the retention rules read as concisely as the rest of the workflow.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive with no concept-explanation fluff, but it repeats the untrusted-input guidance in both 'Trust Boundaries and Command Safety' and the closing 'Safety Rules', introducing minor redundancy that keeps it just below the leanest anchor.

2.5 / 3

Actionability

Concrete, executable `gh api`, `git`, and GraphQL commands with quoted variables and `--` pathspecs appear throughout, making the guidance copy-paste ready.

3 / 3

Workflow Clarity

Twelve sequenced steps include explicit validation checkpoints (git-state checks in Step 2.5, remote merge-base verification in Step 10, re-checking staged files before commit) with feedback loops for the destructive push/resolve operations.

3 / 3

Progressive Disclosure

It is a single ~375-line SKILL.md with well-organized sections but no bundle files; sizable inline blocks such as the GraphQL queries and the bot-login list could be split into references, so it sits at the 'some structure but inline-heavy' anchor.

2 / 3

Total

10.5

/

12

Passed

Description

100%

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, uses an explicit 'Use when' trigger, covers both what and when, and occupies a clear distinct niche. It is a strong, well-scoped skill description.

DimensionReasoningScore

Specificity

The description enumerates concrete actions — 'assess, fix, dismiss, reply to, or resolve bot review feedback' — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It explicitly answers both what ('Triage unresolved bot review comments on a GitHub PR') and when (an explicit 'Use when...' clause), satisfying the top anchor.

3 / 3

Trigger Term Quality

'Use when asked to run /squash-bugbot <PR_NUMBER> or to assess, fix, dismiss, reply to, or resolve bot review feedback' gives natural phrasing a user would actually say, with good coverage of relevant terms.

3 / 3

Distinctiveness Conflict Risk

The niche — bot review comments on GitHub PRs — is narrow with distinct triggers, making it unlikely to fire for an unrelated skill.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Consensys/linea-monorepo
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.