enrichment-module-builder

Build a new Nemesis file enrichment module end-to-end with explicit user approval gates for output mode, library choice, sample files, and integration testing.

1.41x

Quality

72%

Does it follow best practices?

Impact

99%

1.41x

Average score across 3 eval scenarios

Securityby

Risky

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/enrichment-module-builder/SKILL.md

Quality

Content

77%

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

The content is highly actionable with excellent workflow gating and validation checkpoints, making it a strong operational guide. Its weaknesses are length/boilerplate verbosity and a monolithic structure that does not split large templates into reference files.

Suggestions

Move the analyzer.py template, test harness template, and E2E integration procedure into separate reference files (e.g. references/analyzer_template.py, references/e2e_testing.md) and link to them from SKILL.md to improve progressive disclosure.

Replace the verbose 'Format your recommendation' boilerplate blocks with a brief bullet list of required fields, trusting Claude to format the presentation itself.

Trim the Overview sentence explaining what enrichment modules do, since Claude can infer this from the reference modules table that follows.

Dimension	Reasoning	Score
Conciseness	The ~650-line body is mostly efficient and does not explain concepts Claude already knows, but the repeated 'Format your recommendation' boilerplate templates with placeholder fill-ins are verbose padding the model could generate itself.	2 / 3
Actionability	Provides fully executable guidance - a real analyzer.py template with correct imports, exact docker/psql commands with schema references, concrete uv run pytest invocations, and copy-paste SQL queries.	3 / 3
Workflow Clarity	Eight clearly numbered steps with explicit GATE 1-4 STOP instructions, verification and completion checklists, an E2E PASS/FAIL report template, and a feedback loop for re-running on failure.	3 / 3
Progressive Disclosure	The skill is monolithic - no references/scripts/assets bundle files exist, and large code templates, test scaffolding, and the E2E procedure that could live in separate reference files are all inline; repo paths like DEVELOPMENT_GUIDE.md are one-level and well signaled.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 is specific and distinctive, clearly scoped to building Nemesis enrichment modules with concrete approval-gated actions. Its main weakness is the absence of explicit 'when to use' trigger guidance and natural user-facing trigger terms.

Suggestions

Add a 'Use when...' clause with natural trigger phrasing, e.g. 'Use when the user asks to create or add a Nemesis enrichment module, analyze a new file type in Nemesis, or add a file_enrichment_modules analyzer.'

Include common natural variations users might say ('enrichment module', 'Nemesis analyzer', 'add a file parser to Nemesis') alongside the technical terms.

Keep the concrete approval-gate detail but consider trimming it from the description into the body so the description stays a concise what+when trigger.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions - 'Build a new Nemesis file enrichment module end-to-end' plus explicit approval gates for output mode, library choice, sample files, and integration testing - rather than vague language.	3 / 3
Completeness	Clearly answers 'what' the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric completeness is capped at 2.	2 / 3
Trigger Term Quality	Contains relevant domain keywords ('Nemesis file enrichment module') but relies on technical jargon ('enrichment module', 'approval gates') and lacks the natural trigger variations a user would actually say.	2 / 3
Distinctiveness Conflict Risk	Tied to a specific platform and artifact type (Nemesis file enrichment modules), giving it a clear niche unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (654 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: SpecterOps/Nemesis
Commit: d77fafe

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