tessl-labs/typescript-project-structure
TypeScript project structure, strict tsconfig, module resolution, path aliases, shared types, and monorepo patterns
90
84%
Does it follow best practices?
Impact
100%
1.09xAverage score across 5 eval scenarios
Passed
No known issues
Quality
Discovery
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.
This is an excellent skill description that follows best practices. It provides specific capabilities, comprehensive trigger terms covering both setup scenarios and error conditions, explicit 'Use when' and 'Triggers on' clauses, and is clearly distinguishable from other skills through TypeScript-specific terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'tsconfig configuration', 'build setup', 'configuring path aliases', 'separating src from config', 'setting up ESM modules', 'creating build/dev scripts'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('TypeScript project structure, tsconfig configuration, and build setup') and when with explicit 'Use when...' clause and detailed 'Triggers on:' section covering multiple scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'new TypeScript project', 'tsconfig setup', 'cannot find module errors', 'path alias', 'strict mode', 'barrel exports', 'monorepo setup'. Includes both technical terms and error messages users would encounter. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to TypeScript project setup with distinct triggers like 'tsconfig.json', 'path aliases', 'ESM modules', and TypeScript-specific errors. Unlikely to conflict with general coding or other language skills. | 3 / 3 |
Total | 12 / 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 comprehensive and highly actionable TypeScript project setup guide with excellent code examples that are immediately usable. The main weaknesses are verbosity in explanatory sections that assume less of Claude's knowledge than necessary, and a lack of explicit validation checkpoints in the workflows. The content would benefit from being split into a concise overview with links to detailed reference files.
Suggestions
Add explicit validation steps after key configuration changes (e.g., 'Run `npm run typecheck` to verify tsconfig is correct before proceeding')
Move detailed sections like monorepo patterns, ESLint configuration, and barrel exports to separate reference files, keeping SKILL.md as a concise overview
Remove explanatory text about what strict mode options do individually - Claude knows this; just state 'enable strict: true' with the critical addition of noUncheckedIndexedAccess
Add a troubleshooting section with common error messages and their fixes (e.g., 'cannot find module' errors mentioned in the skill description)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is generally efficient with good code examples, but includes some explanatory text that Claude would already know (e.g., explaining what strict mode options do individually, explaining why not to commit dist/). Some sections could be tightened. | 2 / 3 |
Actionability | Excellent actionability with fully executable, copy-paste ready code examples throughout. Every pattern includes complete tsconfig.json snippets, package.json scripts, directory structures, and TypeScript code examples that can be used directly. | 3 / 3 |
Workflow Clarity | The checklist at the end provides good structure, but the document lacks explicit validation steps and feedback loops. For example, there's no 'run typecheck after configuring tsconfig' or 'verify path aliases work before proceeding' guidance. Multi-step processes like monorepo setup don't have clear validation checkpoints. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers, but it's a monolithic document (~400 lines) that could benefit from splitting advanced topics (monorepo patterns, ESLint config) into separate files. The verifiers section at the end references external files appropriately, but the main content doesn't leverage progressive disclosure. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (562 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
Reviewed
Table of Contents