CtrlK
BlogDocsLog inGet started
Tessl Logo

docs-impact-localizer

Use this skill to translate a classifier's in-place verdict into a precise, page-by-page work plan for the docs-sync panel. Activate after docs-impact-classifier returns verdict in_place; reads the candidate page list, fetches the actual page contents, narrows scope to specific sections within each page, and emits the per-page task brief the panel fans out against.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary content body: lean, fully actionable, with a clearly sequenced workflow, built-in verification hooks, and a well-organized single-file structure that needs no external references.

DimensionReasoningScore

Conciseness

Lean and purposeful throughout: concrete YAML/JSON schemas, specific line-range and command examples, and role framing ('You are NOT the verdict-maker... You are the work planner') that prevents scope creep without explaining concepts Claude already knows. Every section earns its tokens with no generic padding.

3 / 3

Actionability

Fully executable guidance — specific commands ('gh pr diff $PR', 'apm install --help', 'grep -n no-cache src/apm_cli/commands/install.py'), concrete line ranges ('lines 120-145'), and complete JSON/YAML output schemas that are copy-paste ready, matching the top anchor.

3 / 3

Workflow Clarity

A clear 4-step sequence (load page contents -> narrow scope -> detect cross-page conflicts -> emit brief) with an explicit output contract and built-in verification via verify_claims[] consumed by the verifier panel.

3 / 3

Progressive Disclosure

Single self-contained file with well-organized sections (When to invoke, Inputs, Steps 1-4, Output contract, Anti-patterns); no bundle files exist and no external references are needed, so the well-organized inline structure satisfies the top anchor.

3 / 3

Total

12

/

12

Passed

Description

85%Weight 40%Scale 1-3

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, specific description with clear what-and-when framing and good distinctiveness from sibling skills. Its only weakness is that triggers are phrased as internal system states rather than natural user language.

Suggestions

Add natural-language trigger terms a user might say (e.g. 'when the user asks to update docs for an in-place change' or 'docs sync work plan') alongside the system-state trigger so it surfaces on user phrasing.

Consider mirroring the canonical 'Use when...' construction to reinforce the trigger clause.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'translate a classifier's in-place verdict into a precise, page-by-page work plan', 'reads the candidate page list, fetches the actual page contents, narrows scope to specific sections within each page, and emits the per-page task brief' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what ('translate a classifier's in-place verdict into a precise, page-by-page work plan') and when ('Activate after docs-impact-classifier returns verdict in_place') with an explicit trigger clause, matching the top anchor.

3 / 3

Trigger Term Quality

Domain terms (docs-sync panel, classifier, page contents, sections) are relevant but the triggers are internal orchestration jargon ('Activate after docs-impact-classifier returns verdict in_place') rather than natural language a user would say, missing common user-facing variations.

2 / 3

Distinctiveness Conflict Risk

A clear niche scoped to the in_place verdict and explicitly distinguished from sibling skills (classifier owns verdicts, doc-writer owns writing), making it unlikely to trigger for the wrong skill.

3 / 3

Total

11

/

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
microsoft/apm
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.