dialectic

Minimal compatibility wrapper for vibe Dialectic Mode (multi-perspective design analysis).

Quality

58%

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 ./bundled/skills/dialectic/SKILL.md

Quality

Content

73%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 skill body is exceptionally concise and well-structured as a thin routing adapter, with a clear sequenced contract and grade-based branching. Its weakness is actionability: it routes to external files rather than giving executable, self-contained steps.

Suggestions

Include at least one concrete invocation example or minimal inline command so Claude can act without first reading external files.

Add a brief validation/confirmation checkpoint (e.g. confirm consensus, divergences, blind spots, synthesis are all present before returning).

Verify the referenced vibe paths exist in the bundle and, if possible, mirror the key Template 6 outline inline so the skill is self-sufficient when vibe is absent.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: short sections, no padding, no explanations of concepts Claude already knows, every line carries information.	5 / 5
Actionability	It points to concrete file paths (vibe/protocols/team.md, references/team-templates.md, Template 6/7) but provides no executable commands or code; the guidance is routing-level rather than copy-paste ready, and the cited files are external and unverifiable here.	3 / 5
Workflow Clarity	A clear two-step sequence (route to vibe Dialectic Mode, then produce a named four-part output) with grade-specific branches; minor gap is that no validation/checkpoint is shown, though the operation is non-destructive routing.	4 / 5
Progressive Disclosure	Content is well organized into clearly signaled sections (Use Cases, Execution Contract, Compatibility Notes) with one-level-deep references to the vibe bundle; minor gap is that the referenced paths point to another skill's bundle rather than a local references/ directory.	4 / 5
	Total	16 / 20 Passed

Description

42%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 conveys the skill's purpose as a lightweight adapter but relies on jargon and omits explicit 'Use when...' trigger guidance, which caps completeness. Trigger terms are technical rather than natural user phrasings.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for the think-tank / multi-perspective design comparison flow (e.g. "dialectic-design", "$vibe dialectic")'.

Reword to favor natural user phrasings over internal jargon ('vibe', 'Dialectic Mode') so trigger-term quality improves.

Name the concrete output the skill produces (consensus, divergences, blind spots, synthesis) so the capability is more specific.

Dimension	Reasoning	Score
Specificity	The phrase 'multi-perspective design analysis' names the domain and the wrapper action ('routing/adapter'), but the concrete actions it performs are minimal and generic rather than a list of specific capabilities.	3 / 5
Completeness	A clear 'what' is present (compatibility wrapper for vibe Dialectic Mode), but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description, capping completeness at 3 per the guidelines.	3 / 5
Trigger Term Quality	It surfaces a few technical trigger strings ('dialectic-design', 'Dialectic Mode') but lacks the natural synonyms and phrasings a user would say; 'compatibility wrapper for vibe' is jargon-heavy and unlikely as a user utterance.	2 / 5
Distinctiveness Conflict Risk	'Dialectic Mode' and 'vibe' give it a niche, but it is a thin adapter to another skill so it overlaps with and relies on that sibling skill, leaving moderate conflict risk.	3 / 5
	Total	11 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/dialectic/SKILL.md
Commit: d5ae560

Reviewed: 1 day 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.