CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

docs-impact-architect

Use this skill when the docs-impact-classifier returns a structural verdict, signalling that the documentation TOC must change to accommodate the PR. Proposes TOC deltas (new pages, moves, merges) and emits new-page outline stubs that the doc-sync panel later fleshes out. Holds the 3-promise narrative (consume / produce / govern) and the persona ramps as hard constraints.

72

Quality

90%

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

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

An excellent instruction-style skill body: dense, concrete, and self-validating, with a clear step sequence and an explicit output contract. The only structural improvement available is splitting the reference templates into a separate file for leaner top-level loading.

DimensionReasoningScore

Conciseness

Lean and operational throughout — the shape table, YAML stubs, five hard rules, and anti-patterns list contain no concept explanations Claude already knows and no padding; every section drives the task.

5 / 5

Actionability

Fully actionable: a concrete command (`gh pr diff $PR`), a worked example per structural shape ('`apm pack --format wheel` adds a new package format'), fill-in YAML templates with per-field constraints ('redirect_to: <slug> # MUST exist'), and a complete JSON output contract.

5 / 5

Workflow Clarity

Steps 1-5 are explicitly sequenced and Step 4 is a genuine validation checkpoint with a feedback loop ('Apply these hard rules. If any fails, redesign'), reinforced by self-check anti-patterns.

5 / 5

Progressive Disclosure

Well-organized single-file skill with no external references (none exist in the bundle), but at ~130 lines the shape-classification table and the YAML/JSON templates are candidates for a one-level-deep references/ file, which keeps it at 'good structure, minor organization gaps'.

4 / 5

Total

19

/

20

Passed

Description

80%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 with explicit what-and-when structure and a distinctive, well-gated trigger. Its only weakness is trigger-term naturalness — it leans on internal pipeline vocabulary rather than phrases a user would naturally say.

Suggestions

Add one or two natural user-facing synonyms for the trigger, e.g. 'reorganize the documentation structure' or 'table of contents changes', alongside the classifier-verdict condition.

Mention the retirement/redirect and persona-ramp-impact actions in the description so the capability list matches what the skill actually emits.

DimensionReasoningScore

Specificity

Names several concrete actions with specific artifacts — 'Proposes TOC deltas (new pages, moves, merges)', 'emits new-page outline stubs' — but omits actions detailed only in the body (retired pages, redirects, ramp impact), leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both: what ('Proposes TOC deltas... emits new-page outline stubs... Holds the 3-promise narrative... as hard constraints') and when ('Use this skill when the docs-impact-classifier returns a structural verdict') with a concrete trigger condition.

5 / 5

Trigger Term Quality

Contains relevant domain keywords ('structural verdict', 'documentation TOC', 'PR', 'new pages, moves, merges') but relies on pipeline jargon ('TOC delta', 'doc-sync panel') and misses natural synonyms like 'reorganize docs' or 'table of contents change'.

3 / 5

Distinctiveness Conflict Risk

Trigger is gated on a specific upstream signal (classifier's structural verdict) and a named pipeline role, giving it a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

17

/

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

microsoft/apm

Path

.agents/skills/docs-impact-architect/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.