CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

api-changes

Use when customer-facing API changes were made — i.e., API report .md files differ from the branch's resolved comparison base. Guides through release tag assignment, API Council review requirements, breaking change classification, deprecation process, and changeset guidance. Triggered automatically by ci-readiness-check when api-report diffs are detected.

Quality

91%

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

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.

A well-engineered procedural skill: every step is concrete, sequenced, and validated, and almost all content is non-inferable repo policy rather than padding. The only structural weakness is that everything lives inline in one file with no top-level overview or bundle split, which keeps progressive disclosure and conciseness just short of excellent.

DimensionReasoningScore

Conciseness

The body is dense with repo-specific policy Claude cannot infer (tag semantics, break-window versions, partner lead times, changeset summary rules), so nearly every token earns its place; only minor bits could be trimmed, e.g. the general definition 'A breaking change removes or modifies an existing API in a way that causes compile errors for consumers upgrading'.

4 / 5

Actionability

Guidance is fully executable with copy-paste commands ('git diff "$BASE_COMMIT" -- ':(glob)**/api-report/*.md'', 'pnpm flub changeset add --releaseGroup <releaseGroup> --empty'), concrete decision tables for tags and council approval, and a complete @deprecated TSDoc example covering the common cases.

5 / 5

Workflow Clarity

Seven clearly sequenced steps with explicit validation checkpoints ('If all changes are @internal-only... stop', 'flag any missing ones to the user', the deprecation checklist, 'show the content to the user and confirm it looks right') and a final go/no-go summary provide feedback loops and a checklist for a complex process.

5 / 5

Progressive Disclosure

Step-based sections are well organized and references to repo docs (API-Deprecation.md, Beta-Break-Process.md, .changeset/README.md) are clearly signaled and one level deep, but the skill is a single ~148-line file with no overview-first structure and reference material (tag tables, break-process details) kept fully inline rather than split into bundle files.

4 / 5

Total

18

/

20

Passed

Description

92%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 that concretely states both what the skill does and when it fires, with domain-specific trigger terms that make it highly distinguishable. The only improvement space is broader synonym coverage in the trigger phrasing.

DimensionReasoningScore

Specificity

'Guides through release tag assignment, API Council review requirements, breaking change classification, deprecation process, and changeset guidance' lists five specific concrete actions that comprehensively mirror the skill's steps; the voice is third person, so no penalty applies.

5 / 5

Completeness

It explicitly answers both questions: 'Use when customer-facing API changes were made — i.e., API report .md files differ from the branch's resolved comparison base' gives a concrete trigger, and the 'Guides through...' sentence states exactly what it does.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('API changes', 'api-report diffs', 'API report .md files', 'breaking change', 'deprecation', 'changeset') that a developer would actually say, but a few natural variations are missing (e.g. 'public API', 'API surface', 'release notes'), so it falls short of the comprehensive-with-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

Terms like 'API Council', 'ci-readiness-check', and 'api-report diffs' carve out a clear niche tied to this repository's API review process, making false triggers against other skills very unlikely.

5 / 5

Total

19

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository

microsoft/FluidFramework

Path

.github/skills/api-changes/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.