CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

implement-suggestion

Applies human and AI-bot review comments on one or more PRs — each gated by /critical + /confidence, committed separately, pushed, and its thread resolved — or one pasted suggestion in place. --watch repeats on one PR until reviewers go quiet; --resolve-all also closes every non-fix thread it honestly can; triggers on "implement suggestion", "apply review comments", "/implement-suggestion".

Quality

87%

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

85%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 itself is a high-quality orchestrator skill document: lean, dense with executable guidance, and with an unusually well-specified multi-phase workflow including validation and error paths. Its one real defect is bundle integrity — nearly all of the rules and template files the body defers to are missing from the bundle, so the progressive-disclosure promise is unfulfilled.

Suggestions

Ship the referenced bundle files: all ten rules/*.md files and templates/suggestion-pack.md are cited with load timing but absent from the bundle, so every phase's 'Apply <rules/...>' instruction dead-ends. Either include them or inline the minimal content each phase needs.

Inline the worker prompt template (or at least the commit-message format it mandates) in SKILL.md Phase 6 — the 'one commit per applied comment' contract is central, but its concrete shape only exists in the missing rules/handoff.md.

The reference '../../../agents/shared/rules/reviewer-report-ingest.md' escapes the skill directory entirely; move that grammar in-bundle (e.g. under rules/) so the skill is self-contained and the path resolves.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence throughout — no concept is explained (what a PR is, how git works), and every section is operational: a mode-detection table, a gate-score matrix, an eight-phase architecture block, and terse hard rules. There is no padded or over-explained passage left to trim, matching the anchor-5 'every token earns its place' rather than anchor 4's 'minor instances of over-explanation'.

5 / 5

Actionability

Mostly executable guidance: concrete commands ('gh api repos/<owner>/<repo>/pulls/<n>/reviews', 'gw checkout <pr-url-or-number>', 'git status --porcelain', 'gh pr view --json number,url,state,...') and a numeric /confidence decision matrix. It falls short of anchor 5 because the worker prompt template and the commit-message format ('message cites @author + URL') are only pointed at via rules/handoff.md rather than given inline, leaving minor gaps for the most delicate step.

4 / 5

Workflow Clarity

Phases 0–7 are clearly sequenced with explicit parallel/sequential boundaries ('Phases 1–6 run in parallel across PRs; Phase 4 runs sequentially within a PR'), validation checkpoints are present for this batch operation (two-gate validation, 'verify git status --porcelain is empty and HEAD == headRefOid', full check before push), and error-recovery paths are explicit (refuse MERGED/CLOSED PRs, contradicting comments move to surface, auto-rebase is surface-and-stop). This matches anchor 5's 'explicit validation steps; feedback loops; checklists' — the batch-operation cap does not apply since validation is thorough.

5 / 5

Progressive Disclosure

The in-body structure is excellent — a 'Rule | When it loads' table, per-phase read triggers, and one-level-deep references — but scored against the actual bundle, 11 of the 12 referenced files (all ten rules/*.md and templates/suggestion-pack.md) are absent; only references/apply-context.md exists. The navigation design would merit 4–5, but the dangling referenced paths are a major organization gap, not a minor one, placing it at anchor 3 rather than anchor 4.

3 / 5

Total

17

/

20

Passed

Description

88%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.

A strong description: concrete, third-person, and fully explicit about both capabilities and triggers, with the flag behaviors (watch, resolve-all) described rather than just named. The only weaknesses are modest — a few missing natural trigger synonyms and undischarged overlap risk against closely related PR-review skills.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — 'Applies human and AI-bot review comments on one or more PRs — each gated by /critical + /confidence, committed separately, pushed, and its thread resolved' — plus both flag behaviors ('--watch repeats on one PR until reviewers go quiet; --resolve-all also closes every non-fix thread it honestly can'). Coverage of the skill's modes and actions is comprehensive with no gaps, which matches the anchor-5 example rather than anchor 4's 'minor gaps in coverage'.

5 / 5

Completeness

Both halves are explicit: the 'what' is the full apply/gate/commit/push/resolve pipeline, and the 'when' is stated via concrete trigger phrases ('triggers on ...'), matching the anchor-5 example pattern. It is not anchor 4 because the when-clause is explicit and concrete rather than 'could be more explicit or specific'.

5 / 5

Trigger Term Quality

It explicitly names natural trigger phrases users would say: 'triggers on "implement suggestion", "apply review comments", "/implement-suggestion"'. This is good keyword coverage but not comprehensive — common variations like 'address review feedback', 'fix review comments', or 'implement PR feedback' are missing — so it sits at anchor 4 rather than the synonym-complete anchor 5 or the sparser anchor 3.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — implementing review feedback rather than generating it — with distinct triggers including the unique '/implement-suggestion'. However, closely related sibling skills in the same ecosystem (pr-reviewer, review-loop) overlap on phrases like 'apply review comments', and the description does not disambiguate against them, so it fits anchor 4's 'minor overlap risk with closely related skills' better than anchor 5's 'minimal conflict risk'.

4 / 5

Total

18

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 25 missing, 1 suspicious

Warning

Total

12

/

16

Passed

Repository

mthines/agent-skills

Path

skills/workflow/implement-suggestion/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.