lint-build-test
How to check code by linting, building, and testing.
Install with Tessl CLI
npx tessl i github:MetaMask/ocap-kernel --skill lint-build-test72
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%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 provides a basic understanding of the skill's purpose but lacks the explicit trigger guidance needed for Claude to reliably select it from a large skill library. It names general actions without sufficient specificity or natural user language variations, and critically omits any 'Use when...' clause.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks to lint code, run tests, check for errors, build a project, or verify code quality'
Include more natural trigger terms users would say: 'lint', 'run tests', 'compile', 'check errors', 'CI checks', 'code quality'
Specify concrete actions or supported tools/languages to increase specificity, e.g., 'Run linters (ESLint, pylint), execute test suites, and compile/build projects'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (code checking) and lists three actions (linting, building, testing), but these are general categories rather than concrete specific actions like 'run ESLint', 'execute pytest', or 'compile TypeScript'. | 2 / 3 |
Completeness | Describes what the skill does (check code via linting/building/testing) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'linting', 'building', 'testing', and 'code' that users might say, but misses common variations like 'lint', 'compile', 'run tests', 'CI', 'check errors', or specific tool names. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to code quality checking, but could overlap with general coding skills, CI/CD skills, or language-specific testing skills. The broad terms 'linting', 'building', 'testing' could conflict with more specialized skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently guides Claude through a code checking workflow. It excels at conciseness and actionability with specific commands and clear decision logic. The only gap is the lack of explicit error handling or validation checkpoints between the lint/build/test steps.
Suggestions
Add brief guidance on what to do when a step fails (e.g., 'If lint fails, fix issues and re-run before proceeding to build')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, with no unnecessary explanations. It assumes Claude knows what linting, building, and testing are, and every line serves a purpose. | 3 / 3 |
Actionability | Provides specific, copy-paste ready commands for each scenario. The exact yarn commands are given for both package-specific and monorepo-wide operations. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and the decision tree is logical, but there's no explicit validation or error recovery guidance beyond 'report any errors encountered.' For operations that could fail at multiple stages, feedback loops would strengthen this. | 2 / 3 |
Progressive Disclosure | For a simple, focused skill under 50 lines, the content is well-organized with clear sections and headers. No external references are needed given the scope. | 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.
- 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.