CtrlK
BlogDocsLog inGet started
Tessl Logo

foundry-route-doc-check

Validates that all TypeSpec route operations in the AI Foundry data-plane (Foundry) domain have documentation comments and @summary decorators with correct voice, replaces documentation-required suppressions with generated documentation, and uses description override extensions when TypeSpec would concatenate noisy descriptions. USE FOR: reviewing or authoring routes.tsp and routes.generated.tsp files under specification/ai-foundry/data-plane/Foundry/src/, including nested OpenAI routes under src/openai/. DO NOT USE FOR: files outside the Foundry data-plane area, model-only .tsp files, or SDK client customization files (client.tsp).

69

Quality

83%

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

67%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 is well-structured, actionable, and uses progressive disclosure with a single clearly-linked reference. Its main weakness is conciseness: the Conservative Change Policy and Rules table overlap, and suppression/override guidance is repeated across sections.

Suggestions

Consolidate the 'Conservative Change Policy' bullets into the Rules table (or vice versa) to remove duplication between what triggers a fix and the rule definitions.

Move the detailed suppression-removal and override-extension walkthroughs into route-documentation-rules.md, keeping the body to the rule table and a short pointer, to reduce repetition.

Add an explicit error-recovery loop to Post-Edit Steps ('if tsp compile fails, fix the reported errors and re-run') to turn the verification step into a full feedback loop.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes TypeSpec competence, but the 'Conservative Change Policy' bullet list substantially duplicates the Rules table, and the suppression/override-extension guidance is repeated across the Rules table and dedicated sections; it could be tightened.

3 / 5

Actionability

Provides copy-paste-ready extension snippets ('@extension("x-ms-description-override", ...)') and concrete commands ('npx tsp format ...', 'npx tsp compile .') with specific file globs, with only minor gaps left to the referenced rules file.

4 / 5

Workflow Clarity

A clear 7-step Workflow plus ordered Post-Edit Steps (format, then compile, then verify openapi3 outputs) is present, with a verification checkpoint; the error-recovery feedback loop on compile failure is only implicit rather than spelled out.

4 / 5

Progressive Disclosure

Body offers a rules overview table and points to a single one-level-deep reference (route-documentation-rules.md) that is clearly signaled, though some detail (full suppression/override sections) is inlined that could live in the reference.

4 / 5

Total

15

/

20

Passed

Description

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

The description is exemplary: it states concrete capabilities, includes natural trigger terms and file names, and explicitly covers both when-to-use and when-not-to-use. It is written in third person and has minimal conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Validates that all TypeSpec route operations ... have documentation comments and @summary decorators', 'replaces documentation-required suppressions with generated documentation', 'uses description override extensions when TypeSpec would concatenate noisy descriptions'), giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both 'what' (validates/replaces/uses override extensions) and 'when' via a 'USE FOR:' clause with concrete triggers plus a 'DO NOT USE FOR:' anti-trigger clause.

5 / 5

Trigger Term Quality

Includes natural domain terms and file names users would mention: 'routes.tsp', 'routes.generated.tsp', '@summary decorators', 'documentation-required suppressions', 'description override extensions', 'OpenAI routes', and 'client.tsp'.

5 / 5

Distinctiveness Conflict Risk

Scoped to a clear niche (Foundry data-plane routes.tsp files) with an explicit exclusion list, making conflict with other skills minimal.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Azure/azure-rest-api-specs
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.