CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

74

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

90%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 high-quality, executable patterns guide that is lean, code-driven, and well-structured. Its main weakness is that a large single-file reference could benefit from splitting detailed material into referenced bundle files.

Suggestions

Consider extracting the binding-syntax reference and full testing harness details into referenced files (e.g. BINDINGS.md, TESTING.md) to reduce inline bulk and improve progressive disclosure.

Add a brief "Quick start" section at the top so the most common pattern (defining an element) is reachable before the topic-by-topic reference.

DimensionReasoningScore

Conciseness

Lean and code-heavy; assumes TypeScript competence and avoids explaining basic concepts, with prose limited to non-obvious policy rationale (e.g. the browser-API avoidance stance).

5 / 5

Actionability

Provides fully executable, copy-paste-ready examples across imports, templates, styles, decorators, and tests, plus a concrete binding-syntax table covering the common cases.

5 / 5

Workflow Clarity

Clearly organized into logical sections with the define() and testing patterns sequenced well, but as a reference/patterns guide it lacks explicit validation checkpoints; no cap applies since operations are non-destructive.

4 / 5

Progressive Disclosure

Well-organized with clear section headers in a single self-contained file, but at ~285 lines with no bundle files or one-level-deep references, it sits below the split-and-referenced 5 anchor.

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, specific description that clearly states both what the skill covers and when to use it, scoped tightly to the FAST monorepo. Its only gap is the absence of synonym/extension trigger terms.

Suggestions

Add natural trigger synonyms and file extensions, e.g. ".ts files", "FASTElement", or "Web Components in FAST" to broaden trigger matching.

Consider naming the observable/reactive system with the user-facing term ("reactivity") alongside the technical one.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "authoring Web Components, writing templates and styles, working with the observable/reactive system, and testing" — giving comprehensive coverage of FAST TypeScript tasks.

5 / 5

Completeness

Explicitly answers both what (authoring components, templates, styles, reactivity, testing) and when ("Use this guide when working on TypeScript changes in the FAST monorepo") with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Good keyword coverage ("TypeScript changes", "FAST monorepo", "Web Components", "observable/reactive system") but lacks synonyms or file extensions like .ts, so it sits just below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The "FAST monorepo" niche is specific and unlikely to trigger for unrelated skills, giving minimal conflict risk.

5 / 5

Total

19

/

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
microsoft/fast
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.