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.

Quality

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/productivity/overnight-dev/skills/overnight-development/SKILL.md

Quality

Discovery

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 boilerplate trigger language ('Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.') that provides no actionable selection guidance. The capability description is truncated ('test-driven' appears cut off) and lacks concrete actions. It would be nearly impossible for Claude to reliably select this skill from a pool of alternatives.

Suggestions

Replace the boilerplate 'Use when appropriate context detected' with specific trigger conditions, e.g., 'Use when the user asks about overnight development automation, git hook workflows, or automated test-driven development pipelines.'

Complete the truncated description and list concrete actions, e.g., 'Sets up git pre-commit hooks, runs test suites automatically, generates code changes based on failing tests, and commits passing changes overnight.'

Add natural trigger terms users would actually say, such as 'overnight coding', 'automated TDD', 'git hooks', 'batch development', 'unattended 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 boilerplate placeholder ('Use when appropriate context detected') that provides no actual guidance on when to select this skill.	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 still overlap with many development-related skills.	2 / 3
	Total	5 / 12 Passed

Implementation

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 placeholder text that has not been filled in with any actual content about overnight development, git hooks, or TDD. It provides zero actionable guidance — every section could be copy-pasted into any skill without modification. The skill completely fails to teach Claude how to perform the described task.

Suggestions

Replace the generic instructions with a concrete workflow: show the actual git hook scripts (pre-commit, post-commit), the TDD cycle commands (run tests, check coverage), and how to orchestrate overnight batch development.

Add executable code examples for setting up git hooks (e.g., a pre-commit hook that runs the test suite and blocks commits on failure).

Define specific validation checkpoints: e.g., 'Run `pytest --cov` and verify coverage >= threshold before committing', 'Check git status is clean before proceeding to next task'.

Remove all generic placeholder text ('Understanding of skill functionality', 'Primary deliverables based on skill purpose') and replace with specifics about what overnight development produces and how success is measured.

Dimension	Reasoning	Score
Conciseness	The content is entirely generic filler with no specific information about overnight development, git hooks, or TDD. Every section contains vague placeholder text that provides zero value — phrases like 'Understanding of skill functionality' and 'Primary deliverables based on skill purpose' are meaningless padding.	1 / 3
Actionability	There is no concrete, executable guidance whatsoever — no git hook code, no TDD workflow commands, no configuration examples. The instructions are completely abstract ('Execute skill workflow systematically') and could apply to literally any task.	1 / 3
Workflow Clarity	The six numbered steps are entirely generic placeholders with no specificity to overnight development, git hooks, or test-driven development. There are no validation checkpoints, no feedback loops, and no actual sequence of operations relevant to the described skill.	1 / 3
Progressive Disclosure	The structure references external files for errors and examples, which is appropriate progressive disclosure in principle. However, the main content is so devoid of substance that the references serve as a crutch rather than a complement — the overview itself provides nothing useful to build upon.	2 / 3
	Total	5 / 12 Passed

Validation

81%

Warnings & errors only

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

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 4dee593

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.