typescript
TypeScript strict mode with eslint and jest
54
43%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/typescript/SKILL.mdQuality
Discovery
22%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 description is essentially a list of technology keywords with no verbs, actions, or trigger guidance. It fails to communicate what the skill actually does or when Claude should select it, making it very difficult to distinguish from other TypeScript-related skills in a large skill library.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Configures TypeScript strict mode, sets up eslint rules, and scaffolds jest test suites.'
Add an explicit 'Use when...' clause with trigger terms, e.g., 'Use when the user asks to set up TypeScript with strict type checking, configure linting, or add unit testing with Jest.'
Include common natural-language variations users might say, such as 'linting', 'type checking', 'unit tests', 'test configuration', '.ts files'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists technologies (TypeScript, eslint, jest) but does not describe any concrete actions. There are no verbs indicating what the skill does—it reads more like a tag list than a capability description. | 1 / 3 |
Completeness | There is no explanation of what the skill does nor any 'Use when...' clause or equivalent trigger guidance. Both the 'what' and 'when' are missing or extremely weak. | 1 / 3 |
Trigger Term Quality | It includes some natural keywords a user might mention ('TypeScript', 'eslint', 'jest', 'strict mode'), but lacks common variations or broader terms like 'linting', 'testing', 'type checking', or 'unit tests'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of TypeScript strict mode, eslint, and jest provides some specificity, but without describing concrete actions it could easily overlap with any TypeScript development, linting, or testing skill. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable TypeScript skill with concrete, executable configurations and good coverage of tooling, testing, and type patterns. Its main weaknesses are verbosity (including boilerplate Claude can generate on its own, like GitHub Actions setup and project structure trees) and lack of an explicit development workflow tying all the tools together. Splitting detailed configurations into referenced files would improve token efficiency.
Suggestions
Extract GitHub Actions, pre-commit hooks, and type patterns into separate referenced files to reduce the main skill's token footprint
Add a brief development workflow section that sequences the tools: write code → typecheck → lint → test → commit, with explicit validation checkpoints
Remove the project structure tree and the explanatory sentence about pre-commit hooks ('This runs on every commit...') — Claude can infer these
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes useful configuration and patterns but is somewhat verbose for what it covers. The project structure, GitHub Actions workflow, and pre-commit hooks sections are lengthy and contain setup details Claude already knows how to produce. The 'This runs on every commit' explanation at the end of pre-commit hooks is unnecessary. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready configurations (tsconfig.json, eslint.config.js, package.json scripts, GitHub Actions YAML, Jest tests, Husky setup). Code examples are concrete and complete with real file paths and realistic values. | 3 / 3 |
Workflow Clarity | The skill presents individual tool configurations clearly but lacks an explicit workflow for how to use them together when developing. The pre-commit hooks section describes a sequence, but there's no overall development workflow with validation checkpoints (e.g., 'after writing code, run typecheck, then lint, then test'). For a skill involving multiple quality gates, explicit sequencing would be valuable. | 2 / 3 |
Progressive Disclosure | The content is well-sectioned with clear headers, but it's a monolithic file that could benefit from splitting. The type patterns, GitHub Actions, and testing sections could be referenced as separate files. The '*Load with: base.md*' reference suggests awareness of progressive disclosure but the main file itself is quite long with inline detail. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- alinaqi/claude-bootstrap
- Commit
d4ddb03
- 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.