build-fix
Incrementally fixes TypeScript and build errors with verification and rollback capabilities
Install with Tessl CLI
npx tessl i github:sc30gsw/claude-code-customes --skill build-fix88
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
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
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 well-structured, concise skill that clearly defines an incremental build-fix workflow with appropriate validation checkpoints and stopping conditions. The main weakness is the lack of concrete code examples for error parsing and fix application, which would make the skill more actionable for complex scenarios.
Suggestions
Add a concrete code example showing how to parse TypeScript error output (e.g., regex patterns or structured output parsing)
Include an example of what 'show error context' output should look like with a sample error and proposed fix
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting only the essential workflow steps without explaining concepts Claude already knows. Every line serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides clear procedural steps but lacks concrete code examples. Commands like 'npm run build' are mentioned but no executable code snippets for parsing errors, applying fixes, or verification are provided. | 2 / 3 |
Workflow Clarity | Clear sequential workflow with explicit validation (re-run build, verify error resolved), stopping conditions (new errors, 3 attempts, user pause), and a feedback loop for error recovery. The one-at-a-time approach is explicitly stated for safety. | 3 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with clear sections (numbered steps, stopping conditions, summary). No external references are needed for this 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.