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. USE FOR: reviewing or authoring routes.tsp files under specification/ai-foundry/data-plane/Foundry/src/. DO NOT USE FOR: files outside the Foundry data-plane area, model-only .tsp files, or SDK client customization files (client.tsp).

80

Quality

100%

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%

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

A well-structured, token-efficient skill body with concrete commands, a sequenced workflow containing explicit validation checkpoints, and a single clearly-signaled one-level reference. It assumes Claude's intelligence and avoids concept exposition.

DimensionReasoningScore

Conciseness

Lean body using tables, terse rule IDs (FDOC-001..005), and copy-paste commands; assumes Claude's competence and avoids explaining TypeSpec or OpenAPI basics, with only minor redundancy between the Rules table and the referenced detail file.

3 / 3

Actionability

Provides executable commands ('npx tsp format ...', 'npx tsp compile .'), a concrete rule table with remediation criteria, and a copy-paste output-format table — fully actionable guidance rather than abstract direction.

3 / 3

Workflow Clarity

A numbered 7-step workflow with explicit post-edit verification checkpoints (format → compile → 'Verify that the files under openapi3/{version}/ are updated'), plus a Conservative Change Policy feedback gate before fixing.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview that signals a single one-level-deep reference — [route-documentation-rules.md](references/route-documentation-rules.md), a real bundle file — keeping detail out of the main file with clear navigation.

3 / 3

Total

12

/

12

Passed

Description

100%

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 highly specific, third-person description with explicit use/non-use triggers and concrete capability statements tightly scoped to the Foundry data-plane routes.tsp niche. It does not pad or over-claim.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Validates that all TypeSpec route operations ... have documentation comments and @summary decorators with correct voice' — naming exact checks rather than vague capability claims.

3 / 3

Completeness

Explicitly answers both what (validates doc comments and @summary with correct voice) and when ('USE FOR: reviewing or authoring routes.tsp files ...'), with a clear exclusion clause, satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

Covers the natural terms a Foundry contributor would say — 'routes.tsp files', 'documentation comments', '@summary decorators', 'TypeSpec route operations' — plus explicit USE FOR / DO NOT USE FOR triggers.

3 / 3

Distinctiveness Conflict Risk

Narrow niche scoped to a single path glob and a DO NOT USE FOR list (client.tsp, models.tsp, openapi3/), making conflict with other skills very unlikely.

3 / 3

Total

12

/

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