simple-typescript

Apply direct, functional TypeScript and JavaScript coding style preferences. Use when writing, editing, reviewing, or refactoring TS/JS code; deciding whether to introduce classes, factories, helpers, wrappers, utilities, shared modules, types vs interfaces, validation boundaries, or recoverable error handling; or when the user asks for code that matches these personal style preferences.

1.20x

Quality

—

Does it follow best practices?

Impact

100%

1.20x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

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 actionable and well-organized with concrete TS/JS examples and a useful review checklist, suited to a simple style-preference skill. The main weakness is mild verbosity where prose and bullet points overlap.

Suggestions

Tighten sections where the lead sentence and the bullets say the same thing (e.g. 'Avoid abstractions that only rename obvious operations' is restated by its bullets) so each line earns its place.

Consider trimming wordy bullets such as the inlining and module-boundary guidance to shorter imperative forms to improve token efficiency.

If the skill grows, move the extended avoid/prefer examples into a reference file and link from SKILL.md to keep the overview lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining basic concepts, but several sections restate their guidance twice (a prose sentence followed by overlapping bullet points restating it) and some bullets are wordy, so it could be tightened further rather than every token earning its place.	2 / 3
Actionability	Provides concrete, executable TypeScript examples with clear 'avoid' vs 'prefer' pairs (e.g. the createUserService factory vs concrete named exports, and the resolveSubscriptionStatus helper), giving copy-paste-ready, specific guidance.	3 / 3
Workflow Clarity	Although not a multi-step operational workflow, this is a simple style-overlay skill with a clearly sequenced Review Checklist that serves as the validation checkpoint before finishing a change; per the simple-skill note, this satisfies workflow clarity.	3 / 3
Progressive Disclosure	With no bundle files present, the content is appropriately self-contained in well-organized sections under 50 lines of substance; per the simple-skill note, well-organized sections without external references warrant a 3.	3 / 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 specific, third-person, and clearly answers both what the skill does and when to use it, with natural trigger terms and a distinct niche. It is a strong example of a well-formed skill description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('writing, editing, reviewing, or refactoring TS/JS code', 'deciding whether to introduce classes, factories, helpers, wrappers, utilities, shared modules, types vs interfaces, validation boundaries, or recoverable error handling'), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly states what the skill does ('Apply direct, functional TypeScript and JavaScript coding style preferences') and when to use it ('Use when writing, editing, reviewing, or refactoring TS/JS code; ... or when the user asks for code that matches these personal style preferences'), satisfying both 'what' and 'when'.	3 / 3
Trigger Term Quality	Covers natural terms a user would actually say ('writing, editing, reviewing, or refactoring TS/JS code', 'the user asks for code that matches these personal style preferences'), with good coverage of natural phrasings; not merely technical jargon.	3 / 3
Distinctiveness Conflict Risk	Has a clear, specific niche (TS/JS functional style preferences) with distinct triggers unlikely to conflict with unrelated skills, matching the 'clear niche with distinct triggers' anchor.	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: idrevnii/perks
Commit: 1674a50

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.