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

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an unfilled template: generic step and output placeholders with no concrete overnight-development or TDD/git-hook guidance, relying on bundled references for any real substance. It is brief and references are real, but it is largely non-actionable.

Suggestions

Replace the generic Instructions with the actual overnight-development workflow: installing pre-commit/pre-push hooks, running the test suite, and blocking commits on failures, with concrete commands or hook script snippets.

Add an explicit validation/feedback loop (run tests -> on failure report and block -> on pass allow commit) since git-hook gating is a destructive/batch-style operation.

Link to all bundled references from the body, notably workflow.md and troubleshooting.md, so the overview provides complete one-level-deep navigation.

Dimension	Reasoning	Score
Conciseness	The body is short and does not belabor concepts Claude already knows, but much of it is generic filler ("Execute skill workflow systematically", "Provide clear results and next steps") whose tokens earn little value, so it is not fully lean.	2 / 3
Actionability	The Instructions are abstract and describe rather than instruct ("Identify skill activation trigger and context", "Gather required inputs and parameters") with no concrete commands, hook scripts, or executable examples for the TDD/git-hook workflow.	1 / 3
Workflow Clarity	A numbered sequence exists (steps 1-6) but it is generic boilerplate with no validation checkpoints for the risky git-hook/test-gating operations, which per the rubric caps workflow clarity at 2.	2 / 3
Progressive Disclosure	The body is a concise overview pointing one level deep to real files (errors.md, examples.md), but it omits references to workflow.md and troubleshooting.md that exist in the bundle, so navigation is only partially signaled.	2 / 3
	Total	7 / 12 Passed

Description

35%

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 pairs a half-finished capability statement with placeholder trigger boilerplate, so it conveys a rough niche but no real activation guidance. It reads as an unfilled template rather than a polished, third-person skill description.

Suggestions

Complete the truncated capability statement and list concrete actions (e.g., 'Installs pre-commit and pre-push git hooks, runs the test suite, and blocks commits on failing tests').

Replace the boilerplate 'Use when appropriate context detected' with explicit natural triggers a user would say, e.g., 'Use when the user wants to run development or testing overnight, automate TDD enforcement via git hooks, or gate commits on passing tests'.

Add concrete trigger keywords (overnight builds, pre-commit hooks, TDD gating, CI enforcement) to improve distinctiveness and reduce conflict with general testing skills.

Dimension	Reasoning	Score
Specificity	It names a domain and some actions ("Automates software development overnight using git hooks to enforce test-driven"), but the sentence is truncated at "test-driven" and "Automates software development overnight" is abstract rather than a comprehensive list of concrete actions.	2 / 3
Completeness	It states a partial "what" (overnight dev via git hooks enforcing TDD) but the "when" is only boilerplate rather than explicit trigger guidance, so per the rubric a missing genuine "Use when..." clause caps completeness at 2.	2 / 3
Trigger Term Quality	The only trigger guidance is generic boilerplate ("Use when appropriate context detected. Trigger with relevant phrases based on skill purpose") with no natural keywords a user would actually say, such as "overnight", "TDD", or "pre-commit hook".	1 / 3
Distinctiveness Conflict Risk	The overnight + git-hook + TDD niche is somewhat specific, but because the trigger terms are generic boilerplate it could still overlap with general development or testing skills.	2 / 3
	Total	7 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3022dd3

Reviewed: 2 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.