CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

phoenix-typescript

TypeScript conventions and patterns for any TypeScript code in the Phoenix monorepo — including js/packages/, js/app/, and any other TS directories. Use this skill whenever writing, reviewing, or modifying TypeScript code — new functions, types, exports, tests, or refactors. Also trigger when the user asks about TS patterns, naming conventions, or best practices for this project.

Quality

82%

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

75%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 solid conventions skill: rules are concrete, backed by executable bad/good code pairs, and grounded in repo-specific facts (no noUncheckedIndexedAccess, tree-shaking rationale for path imports). The main gaps are the truncated fetchSpans example, the vague 'check sibling packages' reuse direction, and the absence of any verify step such as running the type checker or linter.

DimensionReasoningScore

Conciseness

The body is almost entirely rules plus bad/good code pairs with only minor trimmable rationale ('TypeScript's type system is most valuable when it catches bugs at compile time', 'Self-documenting names eliminate mental parsing for the next reader'). The extended zoomOut example is executable and justified by the repo-specific purity rule, so this fits 'efficient; minor instances of over-explanation' rather than the noticeably padded level 3.

4 / 5

Actionability

Concrete, executable TypeScript examples cover naming, destructured object params with JSDoc, Record<K, V | undefined> lookups, and lodash path imports ('import debounce from "lodash/debounce"'). Not 5 because the fetchSpans snippet is truncated at the signature and the Reuse section gives direction ('check sibling packages') without a concrete method; not 3 because guidance is mostly executable with only minor gaps.

4 / 5

Workflow Clarity

A single-purpose conventions skill with an unambiguous entry sequence ('Before writing new code, explore the directory you're working in to understand existing patterns — then follow these rules') and sections organized by concern. Not 5 because there is no validation checkpoint (e.g., run tsc/lint to confirm conventions hold); no destructive or batch operations, so no cap applies.

4 / 5

Progressive Disclosure

No bundle files exist, and all guidance sits in one well-sectioned ~110-line file with clear headers (Naming, Functions, Type Safety, Comments, Imports, Reuse). Structure and navigation are good; not 5 because the single file is at the upper bound of inline length (the 28-line zoomOut example could be tightened) and exceeds the under-50-line simple-skill exception; not 3 because organization is clean with no content that clearly belongs in a separate file.

4 / 5

Total

16

/

20

Passed

Description

83%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 description: it states what the skill covers, scopes it precisely to the Phoenix monorepo's TS directories, and gives explicit 'Use this skill whenever...' triggers with natural terms including the TS synonym. The only gaps are missing file-extension triggers and slight genericity in the action list.

DimensionReasoningScore

Specificity

Names the domain ('TypeScript conventions and patterns for any TypeScript code in the Phoenix monorepo') and lists several concrete activities ('writing, reviewing, or modifying TypeScript code — new functions, types, exports, tests, or refactors'). Not 5 because the actions are variants of one activity (writing/reviewing code) rather than multiple distinct capabilities; not 3 because coverage clearly exceeds 1-2 actions.

4 / 5

Completeness

Explicitly answers both: what ('TypeScript conventions and patterns... including js/packages/, js/app/') and when ('Use this skill whenever writing, reviewing, or modifying TypeScript code... Also trigger when the user asks about TS patterns, naming conventions, or best practices'). Concrete trigger phrases match the 5 anchor.

5 / 5

Trigger Term Quality

Good natural-term coverage: 'TypeScript code', 'TS patterns', 'naming conventions', 'best practices', 'refactors', including the TS synonym. Not 5 because file extensions (.ts, .tsx) and other common variants are missing; not 3 because the phrase set is richer than 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Scoped to a specific project ('the Phoenix monorepo') with named directories, giving it a clear niche. Not 5 because it overlaps the generic 'TypeScript conventions/best practices' skill category; not 3 because the project scoping makes it mostly distinct.

4 / 5

Total

17

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

Arize-ai/phoenix

Path

.agents/skills/phoenix-typescript/SKILL.md

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.