overnight-development
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill overnight-developmentAutomates software development overnight using git hooks to enforce test-driven Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
24%
Overall
Validation
Implementation
Activation
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
7%This skill is a generic template with no actual content about overnight development, Git hooks, or TDD. Every section contains placeholder text that could apply to any skill, providing zero actionable guidance. The description promises automation of software development but the body delivers only abstract boilerplate.
Suggestions
Add concrete Git hook configuration code showing how to enforce TDD (e.g., pre-commit hook that runs tests)
Provide specific workflow steps for overnight development: how Claude should identify work, write tests first, implement code, and validate results
Include executable examples of the TDD cycle with actual test and implementation code
Replace generic prerequisites and instructions with specific requirements (e.g., 'pytest installed', 'git repository initialized') and concrete commands
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no specific value. Phrases like 'Understanding of skill functionality' and 'Execute skill workflow systematically' are meaningless filler that waste tokens without teaching Claude anything actionable about overnight development or TDD. | 1 / 3 |
Actionability | The skill contains zero concrete code, commands, or specific instructions. Every section is abstract and vague - 'Identify skill activation trigger', 'Execute skill workflow systematically' - without any actual implementation details for Git hooks, TDD enforcement, or overnight automation. | 1 / 3 |
Workflow Clarity | The numbered steps are completely generic placeholders that could apply to any skill. There's no actual workflow for overnight development, no Git hook configuration, no TDD process steps, and no validation checkpoints for the claimed functionality. | 1 / 3 |
Progressive Disclosure | The skill does reference external files for errors and examples (one level deep), but the main content is so devoid of substance that the references feel like an excuse to avoid providing real content. The structure exists but serves no purpose without meaningful overview content. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
7%This description is severely deficient, containing placeholder text ('Use when appropriate context detected. Trigger with relevant phrases based on skill purpose') instead of actual guidance. The capability description is truncated ('test-driven' appears incomplete) and lacks concrete actions. This would be nearly useless for skill selection among multiple options.
Suggestions
Replace the placeholder 'Use when...' clause with specific triggers like 'Use when user mentions overnight development, git hooks, pre-commit testing, TDD automation, or automated test enforcement'
Complete and expand the capability description with concrete actions: 'Configures git hooks to run test suites before commits, blocks commits with failing tests, generates overnight test reports'
Add natural user terms like 'pre-commit hooks', 'automated testing', 'continuous testing', 'test gates', 'overnight builds'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions 'automates software development overnight using git hooks to enforce test-driven' but this is vague and incomplete - 'test-driven' is cut off, and 'automates software development' is abstract without listing concrete actions like 'runs tests', 'generates reports', or 'blocks commits'. | 1 / 3 |
Completeness | The 'what' is incomplete and vague ('test-driven' is truncated), and the 'when' clause is entirely placeholder text ('Use when appropriate context detected') that provides no actual guidance on when to use this skill. | 1 / 3 |
Trigger Term Quality | The phrase 'Trigger with relevant phrases based on skill purpose' is a placeholder that provides zero actual trigger terms. Users would never say 'appropriate context detected' - natural terms like 'overnight builds', 'git hooks', 'TDD', 'automated testing' are completely absent. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'git hooks' and 'overnight' provides some specificity that distinguishes it from generic development skills, but the vague 'automates software development' could easily overlap with CI/CD, testing, or general automation skills. | 2 / 3 |
Total | 5 / 12 Passed |
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.