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.
92
88%
Does it follow best practices?
Impact
100%
1.20xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
92%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly communicates both what it does and when to use it, with rich trigger terms covering many specific coding decisions. Its main weakness is the broad activation surface—nearly any TS/JS coding task could trigger it, which creates potential conflict with other TS/JS-related skills. The description is well-structured, uses third person voice, and avoids vague language.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and decisions: writing/editing/reviewing/refactoring code, choosing between classes/factories/helpers/wrappers/utilities, types vs interfaces, validation boundaries, and error handling patterns. | 3 / 3 |
Completeness | Clearly answers both 'what' (apply direct, functional TS/JS coding style preferences across multiple decision areas) and 'when' (explicit 'Use when...' clause covering writing, editing, reviewing, refactoring, and specific architectural decisions). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a user would say: 'TypeScript', 'JavaScript', 'TS/JS', 'classes', 'factories', 'helpers', 'wrappers', 'utilities', 'types vs interfaces', 'refactoring', 'code style', 'error handling'. These are terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | While it specifies TS/JS and 'personal style preferences', the broad scope of 'writing, editing, reviewing, or refactoring TS/JS code' could overlap with any general TypeScript/JavaScript coding skill. The 'style preferences' angle helps distinguish it, but the trigger surface is very wide. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong style preference skill with excellent actionability through concrete avoid/prefer code examples and clear organization. The review checklist provides a useful validation mechanism. Minor verbosity in some sections and slight redundancy between related topics (e.g., factories mentioned in both Abstractions and Module Boundaries) prevent a perfect conciseness score, but overall the content is well-crafted and immediately usable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient and well-organized, but some sections could be tightened. For example, the 'Module Boundaries' section has some redundancy with the 'Abstractions And Helpers' section regarding factories and wrappers. The review checklist partially restates rules already covered. However, it largely avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides concrete, executable TypeScript code examples for both 'avoid' and 'prefer' patterns across multiple dimensions (abstractions, module boundaries, error handling, types). The examples are copy-paste ready and clearly illustrate the intended style, making it straightforward for Claude to apply these preferences. | 3 / 3 |
Workflow Clarity | This is a style/preference skill rather than a multi-step process skill. The single task (apply coding style preferences) is unambiguous, and the review checklist at the end serves as an explicit validation checkpoint. The content is clearly sequenced from core principles through specific domains to a final review step. | 3 / 3 |
Progressive Disclosure | For a standalone style preference skill with no bundle files, the content is well-organized into clearly labeled sections with logical grouping. Each section is self-contained and scannable. The skill is under reasonable length and doesn't need external references, so the flat structure is appropriate. | 3 / 3 |
Total | 11 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- idrevnii/perks
- Commit
51dd9ad
- 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.