overnight-development
Automates software development overnight using git hooks to enforce test-driven Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
16
3%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/productivity/overnight-dev/skills/overnight-development/SKILL.mdQuality
Discovery
7%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 largely a placeholder with a truncated capability statement and boilerplate trigger guidance. The 'Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.' is generic filler that provides no value for skill selection. The core concept (overnight TDD automation via git hooks) is interesting but poorly articulated.
Suggestions
Replace the placeholder 'Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.' with specific trigger conditions, e.g., 'Use when the user asks about overnight development, automated TDD workflows, git hook automation, or batch code generation.'
Complete the truncated description and list concrete actions, e.g., 'Runs test suites via git hooks, generates code to pass failing tests, creates commits automatically, and reports progress by morning.'
Add natural trigger terms users would actually say, such as 'overnight coding', 'automated development', 'TDD automation', 'git pre-commit hooks', 'batch development'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions 'automates software development overnight using git hooks to enforce test-driven' which hints at a domain but is vague and incomplete ('test-driven' is cut off). No concrete actions like 'runs tests', 'generates code', or 'creates commits' are listed. | 1 / 3 |
Completeness | The 'what' is incomplete and vague ('automates software development overnight' with a truncated 'test-driven'), and the 'when' clause is a generic placeholder ('Use when appropriate context detected') that provides no actionable guidance whatsoever. | 1 / 3 |
Trigger Term Quality | The phrase 'Trigger with relevant phrases based on skill purpose' is a meaningless placeholder that provides zero actual trigger terms. Terms like 'git hooks' and 'overnight' are present but not framed as natural user language, and common variations are entirely absent. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'git hooks', 'overnight', and 'test-driven' gives it some niche identity that distinguishes it from generic coding skills, but the vagueness of 'automates software development' could easily overlap with many development automation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a generic template with no actual content related to overnight development, git hooks, or test-driven development. Every section contains placeholder text that could apply to literally any skill, providing zero actionable guidance. It fails on all dimensions because it teaches Claude nothing specific about the task it claims to automate.
Suggestions
Replace the generic instructions with specific git hook configurations (pre-commit, post-commit) including executable shell scripts or Python code for enforcing TDD.
Add concrete examples of the overnight development workflow: how tests are defined, how code generation proceeds iteratively, and how validation gates work between iterations.
Include actual error handling content inline or create the referenced errors.md bundle file with specific failure modes (e.g., test failures, merge conflicts, build errors) and recovery steps.
Define explicit validation checkpoints such as running the test suite, checking code coverage thresholds, and verifying git hook installation before proceeding.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely generic filler with no specific information about overnight development, git hooks, or TDD. Every section reads like a template placeholder that adds zero value beyond what Claude already knows. | 1 / 3 |
Actionability | There are no concrete commands, code examples, git hook configurations, or specific TDD workflows. Instructions like 'Execute skill workflow systematically' and 'Validate outputs meet requirements' are completely vague and non-actionable. | 1 / 3 |
Workflow Clarity | The six numbered steps are generic placeholders with no actual sequence for overnight development. There are no validation checkpoints, no git hook setup steps, no TDD cycle description, and no feedback loops for error recovery. | 1 / 3 |
Progressive Disclosure | References to errors.md and examples.md are mentioned but no bundle files exist, making these dead links. The main content itself is so devoid of substance that there's nothing meaningful to disclose progressively. | 1 / 3 |
Total | 4 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
6e9558f
- 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.