typescript

Use this guide when working on TypeScript changes in the FAST monorepo — authoring Web Components, writing templates and styles, working with the observable/reactive system, and testing.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

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

The content is a lean, code-first reference with executable examples and direct rules across modules, templates, styles, reactivity, and testing. Its main weakness is progressive disclosure: everything sits in one file with no references, so API-reference-like material is inline rather than split out.

Suggestions

Extract the binding syntax table and the 'TypeScript idioms' section into a dedicated reference file (e.g. references/binding-syntax.md, references/ts-idioms.md) and link to it one level deep from the body.

Add a short overview/quick-start at the top that stitches element definition, template, styles, and the relevant test pattern into a single end-to-end sequence.

Trim policy prose such as 'Our stance as a framework library is that certain browser APIs are best avoided by the framework' down to the rule and the API list.

Dimension	Reasoning	Score
Conciseness	The body is code-first and lean ('Templates use the html tagged template literal typed to the element class:' followed immediately by executable code), assuming Claude's competence without explaining what TypeScript or Web Components are; only minor phrases such as 'Our stance as a framework library is...' could be trimmed.	3 / 3
Actionability	Pervasive copy-paste-ready executable code (imports, define(), when/repeat templates, the binding syntax table, css styles, attr/observable/volatile, Observable.notify, reactive, test patterns) paired with direct rules like 'Do not use the @customElement decorator'.	3 / 3
Workflow Clarity	Each described action is unambiguous and the browser-evaluated test section sequences goto -> evaluate -> return serializable value -> expect outside the boundary; no destructive or batch operation requires a validation loop here.	3 / 3
Progressive Disclosure	The file is well-organized into clear header sections but is a single ~280-line monolith with no bundle files or external references, and reference-like content (the binding syntax table and the TypeScript idioms deep-dive) lives inline rather than split into one-level-deep reference files.	2 / 3
	Total	11 / 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.

The description is concise, specific, and uses third person with an explicit 'Use this guide when...' trigger that names both the domain (FAST monorepo, TypeScript) and the concrete capabilities covered. It is distinguishable from generic TypeScript skills and carries no fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'authoring Web Components, writing templates and styles, working with the observable/reactive system, and testing' — matching the anchor for several specific concrete actions rather than just naming a domain.	3 / 3
Completeness	Explicitly answers both what and when via 'Use this guide when working on TypeScript changes in the FAST monorepo — authoring Web Components...', combining an explicit trigger clause with a list of capabilities.	3 / 3
Trigger Term Quality	Natural terms a user would say are present ('TypeScript changes', 'FAST monorepo', 'Web Components', 'templates', 'styles', 'testing'), giving good coverage rather than jargon-only or generic phrasing.	3 / 3
Distinctiveness Conflict Risk	Tied to the specific FAST monorepo plus Web Components and the observable/reactive system, a clear niche unlikely to trigger for unrelated TypeScript skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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/fast
Path: .github/skills/typescript/SKILL.md
Commit: 27a4304

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.