CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dialectic

Work out an unsettled idea together through its intent, proposed form, and consequences in practice. Use when the user explicitly requests standalone dialectic, or another active skill invokes it within its task.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/dialectic/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 lays out a coherent, well-gated conversational method with concrete formatting rules, explicit recognition checkpoints, and an exemplary one-level-deep reference structure. Its weaknesses are recurring repetition of the recognition/reopening rules across three sections and a stage sequence that must be assembled from prose rather than a consolidated workflow.

Suggestions

Consolidate the recognition/reopening guidance (currently restated at lines ~35-37, ~42, and ~75-81) into a single statement, e.g. one paragraph on recognition gates and when to reopen, cutting roughly 15 lines.

Add a short ordered summary of the core loop (1. articulate intent in a blockquote, 2. wait for recognition, 3. propose vision, 4. pause for recognition, 5. work backward into form) at the top so the sequence is graspable without reading all sections.

DimensionReasoningScore

Conciseness

The recognition/reopening rule is restated nearly verbatim in three places ("wait for the user to recognize it as right before proposing visions", "Reopen the intent when a correction changes what success means", "Pause for recognition of the intent and the vision before building work that depends on them... Reopen an earlier understanding"), and abstract passages like "Exercise greenfield thinking throughout" could be tightened. There is no padding with concepts Claude already knows, so it is above anchor 2, but the recurring redundancy fits anchor 3 (could be tightened) rather than 4 (only minor instances).

3 / 5

Actionability

The guidance gives concrete, executable conversational moves with formatting specifics: "offer a clear articulation of intent in a blockquote", "bold the parts that need particular attention", "show the current and proposed versions together", "Keep the proposal and the invitation to respond visibly separate". This matches anchor 4 (mostly executable, minor gaps) — not 5 because all example exchanges are deferred to the reference file rather than covering common cases inline, and not 3 because the behavioral guidance is specific and complete for the method.

4 / 5

Workflow Clarity

A clear stage sequence is present (articulate intent -> wait for recognition -> propose vision -> recognition -> work backward into concrete form), organized under matching sections, with explicit checkpoints ("Pause for recognition of the intent and the vision before building work that depends on them") and error-recovery loops ("Reopen an earlier understanding when a correction changes success or a later discovery changes its premise"). It matches anchor 4 rather than 5 because the sequence is scattered across interleaved prose with no consolidated ordered workflow or checklist.

4 / 5

Progressive Disclosure

The body is a well-sectioned overview (## Clarify the intent, ## Develop the vision, ## Work backward into concrete form, ## References) with exactly one well-signaled, one-level-deep reference — "Read [the example conversations](references/conversations.md) when calibrating the progression or how to make a proposal judgeable" — which was verified to exist and to contain the promised example conversations, with an honest caveat that the exchanges are illustrations. Content is appropriately split between method guidance inline and examples in the reference, matching anchor 5.

5 / 5

Total

16

/

20

Passed

Description

66%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 explicitly answers both what and when with a well-gated, distinctive trigger, and correctly uses third-person voice with no over-claims. Its main weakness is abstraction: the capability is described as a single vague action ("work out") rather than concrete actions, and trigger coverage is a single term with no natural synonyms.

Suggestions

Enumerate 1-2 concrete actions in the what-clause, e.g. "Articulate the intent in a blockquote, propose candidate visions, and work backward into concrete form" instead of the generic "Work out an unsettled idea together".

Add one or two natural user phrasings as triggers alongside the explicit-request gate, e.g. "or when the user asks to think through or explore an unsettled idea together", so the skill is discoverable through common synonyms.

DimensionReasoningScore

Specificity

"Work out an unsettled idea together through its intent, proposed form, and consequences in practice" names the domain and a three-stage arc, but the single action verb "work out" is abstract with no enumerated concrete capabilities. It sits at anchor 3 (domain plus 1-2 actions) rather than 4, which expects several specific actions, and above 2 because the named stages add substance beyond a purely generic action.

3 / 5

Completeness

Both parts are explicit: the what ("Work out an unsettled idea together through its intent, proposed form, and consequences in practice") and a concrete when ("Use when the user explicitly requests standalone dialectic, or another active skill invokes it within its task"). It falls between anchors 4 and 5: the when-clause is fully explicit, but the what-side lacks the concrete capability enumeration of the anchor-5 example.

4 / 5

Trigger Term Quality

The only natural trigger terms are "dialectic" and "unsettled idea" ("Use when the user explicitly requests standalone dialectic"), with no synonyms or common variations like "think through an idea" or "explore this together". This matches anchor 3 (some relevant keywords, missing variations) — the gating to explicit request is deliberate, but coverage is essentially a single term.

3 / 5

Distinctiveness Conflict Risk

"Use when the user explicitly requests standalone dialectic" defines a clear niche with deliberately gated triggers, making accidental triggering by brainstorming or discussion skills very unlikely. This matches anchor 5 (clear niche, distinct triggers, minimal conflict risk).

5 / 5

Total

15

/

20

Passed

Validation

100%

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

EpicenterHQ/epicenter

Path

.agents/skills/dialectic/SKILL.md

Reviewed

Table of Contents

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.