CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-typespec-author

Authors and modifies Azure TypeSpec (.tsp) API specifications. MUST BE USED FOR ALL TypeSpec changes regardless of complexity — even adding a single property or enum value requires this skill's validation workflow. USE FOR: any TypeSpec/tsp change — api versions (add, bump, preview, stable, promote), resources, operations, models, properties, decorators, visibility, constraints, breaking changes, LRO, suppressions, operationId, spread model. Covers both ARM resource-manager (Azure.ResourceManager) and data-plane (Azure.Core) services. DO NOT USE FOR: SDK generation, releasing SDK packages, or single MCP tool calls. INVOKES: azure-sdk-mcp:azsdk_typespec_generate_authoring_plan, azure-sdk-mcp:azsdk_run_typespec_validation.

64

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/azure-typespec-author/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 with a clear sequenced workflow and validation feedback loop, but it leans on a reference bundle that is absent, leaving most actionable detail dangling. The 'no simple edits' message is also over-repeated.

Suggestions

Ship the referenced files under ./references/ (analyze-project.md, intake.md, authoring-plan.md, agentic-search.md, reference-document-links.md, validation.md) so the one-level-deep navigation actually resolves.

Collapse the four restatements of 'there are no simple TypeSpec edits' (Triggers intro + Rules bullets 1–3) into a single rule to cut repetition.

Add at least one concrete, copy-pasteable command or minimal .tsp snippet in Step 4 so the apply step is actionable without the missing reference file.

DimensionReasoningScore

Conciseness

Mostly efficient with short step stubs and a reference table, but the 'no simple TypeSpec edits' point is restated four times (Triggers intro, Rules bullets 1–3) and the USE-FOR list duplicates the frontmatter, which could be tightened.

3 / 5

Actionability

Some concrete guidance is present (named MCP tools, an explicit ✅/❌ validation checklist with Case 3 checks), but the actual executable steps are delegated to reference files and Step 4 ('Make minimal .tsp edits following the plan') is only a high-level hint.

3 / 5

Workflow Clarity

A clear six-step sequence is given with a one-line summary and checkboxes, plus an explicit validate→fix→re-run feedback loop and a Case 3 checklist; minor gaps remain because the underlying validation commands live in a referenced file.

4 / 5

Progressive Disclosure

Structure is well-signaled on paper (Reference Files table, one-level-deep links), but the referenced bundle (analyze-project.md, intake.md, authoring-plan.md, agentic-search.md, reference-document-links.md, validation.md) does not exist in ./references/, so the navigation is broken rather than deliverable.

3 / 5

Total

13

/

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.

A strong, third-person description that clearly states capabilities, trigger conditions, and exclusions with comprehensive natural keywords. It is dense but every clause earns its place; no vague fluff or over-claims.

DimensionReasoningScore

Specificity

Names the domain ('Authors and modifies Azure TypeSpec (.tsp) API specifications') and lists many concrete change types — api versions, resources, operations, models, properties, decorators, visibility, constraints, LRO, suppressions, operationId, spread model — giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what ('Authors and modifies Azure TypeSpec (.tsp) API specifications... Covers both ARM resource-manager and data-plane services') and when ('USE FOR: any TypeSpec/tsp change...', 'DO NOT USE FOR: SDK generation...'), with concrete trigger phrases and an explicit exclusion clause.

5 / 5

Trigger Term Quality

Covers natural terms and synonyms a user would say ('TypeSpec', 'tsp change', '.tsp', 'api versions', 'add/bump/preview/stable/promote', 'ARM resource-manager', 'data-plane') including the file extension, matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

A clear niche (Azure TypeSpec authoring) with distinct triggers and an explicit 'DO NOT USE FOR' boundary (SDK generation, releasing packages, single MCP tool calls), minimizing overlap with related skills.

5 / 5

Total

20

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 12 missing

Warning

referenced_paths_exist

Referenced path issues: 12 missing

Warning

Total

14

/

16

Passed

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.