od-new-generation

Default reference pipeline for the new-generation taskKind — discovery → plan → generate → critique with a critique-theater devloop.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/_official/scenarios/od-new-generation/SKILL.md

Quality

Content

78%Weight 40%Scale 1-5

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

The body is a tight, well-structured reference with an executable pipeline config and a built-in critique feedback loop; its main weakness is mild explanatory prose and a thin note on how plugins override the default.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, leading with a spec citation and a compact jsonc block; the prose restating each stage's purpose could be trimmed slightly since the stage names are largely self-documenting.	4 / 5
Actionability	It provides a concrete, copy-paste-ready jsonc pipeline configuration with real atom identifiers and a real repeat/until condition, leaving only minor gaps around how a plugin actually declares its own od.pipeline.	4 / 5
Workflow Clarity	The stages are clearly sequenced and the critique stage encodes an explicit feedback loop with a convergence checkpoint ('critique.score>=4 \|\| iterations>=3'); it stops just short of step-by-step validation guidance.	4 / 5
Progressive Disclosure	At under 50 lines with no need for external references, the content is well organized into clearly signaled sections (Default pipeline, Plugins that customise this scenario), satisfying the simple-skill exception.	5 / 5
	Total	17 / 20 Passed

Description

46%Weight 40%Scale 1-5

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 distinct about a narrow internal pipeline, but relies entirely on jargon with no natural trigger terms and omits any explicit 'when to use' guidance.

Suggestions

Add a 'Use when...' clause stating when Claude should apply this default pipeline (e.g., when a plugin omits od.pipeline for the new-generation taskKind).

Soften the jargon with at least one natural user-facing phrase so the skill is discoverable by intent rather than only by internal term names.

Make the 'what' actionable by briefly framing the stages as outcomes (e.g., 'clarifies intent, commits a plan, generates the artifact, then iterates critique until quality converges').

Dimension	Reasoning	Score
Specificity	Names the domain ('new-generation taskKind') and several concrete pipeline stages (discovery → plan → generate → critique), but the actions are stage labels rather than a comprehensive set of capabilities.	3 / 5
Completeness	It states clearly what the skill is (the default reference pipeline and its stages) but provides no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the guidelines.	3 / 5
Trigger Term Quality	The terms ('new-generation taskKind', 'critique-theater devloop', 'od.pipeline') are internal technical jargon rather than the natural phrases a user would say when they need this skill.	2 / 5
Distinctiveness Conflict Risk	The niche is specific (the default pipeline for the new-generation taskKind) and unlikely to trigger for unrelated skills, with only minor overlap risk against other pipeline/scenario skills.	4 / 5
	Total	12 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: plugins/_official/scenarios/od-new-generation/SKILL.md
Commit: f580271

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