CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

universe-of-thoughts

Creative reasoning framework for ill-defined problems where conventional solutions are suboptimal. Use when the problem has ambiguous goals, vast solution space, no single correct answer, or requires innovation. Implements three paradigms — combinational (novel combinations of familiar ideas), exploratory (expand solution space boundaries), transformative (alter fundamental constraints). Do not use for well-defined problems, mathematical puzzles, or tasks requiring convergent reasoning.

62

Quality

78%

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 ./.claude/skills/universe-of-thoughts/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.

A highly actionable, well-sequenced reasoning framework with an exemplary worked example, held back by token efficiency and file organization. The body duplicates frontmatter content and inlines ~200 lines of per-paradigm templates that belong in separate reference files.

Suggestions

Trim or remove the "When to Use"/"When NOT to Use" sections, which restate the frontmatter description that is loaded anyway.

Move the per-paradigm step templates into one-level-deep reference files (e.g., references/combinational.md, references/exploratory.md, references/transformative.md) and keep SKILL.md to the overview, selection table, integration pipeline, and evaluation criteria.

Add a feedback loop for failed validation: instruct Claude to regenerate or refine solutions that fail the feasibility gate rather than only filtering them out.

DimensionReasoningScore

Conciseness

Mostly efficient — no explanations of concepts Claude already knows — but the "When to Use"/"When NOT to Use" bullet lists duplicate the frontmatter description, and the Integration section re-states "run all three sequentially. Each builds on the previous." These could be trimmed for a tighter body.

3 / 5

Actionability

Fully followable for an instruction-only skill: explicit stepwise procedures (C1–C4, E1–E4, T1–T4) with fill-in templates, enumerated transformation types ("Inversion | Relaxation | Substitution | Elimination"), a concrete ranking formula ("Rank passing solutions by (Utility × Novelty)"), and a complete worked example (single-lane bridge) demonstrating all three paradigms.

5 / 5

Workflow Clarity

Clear sequence (Phase 0 → paradigm selection → paradigms → tiered portfolio) with checkpoints ("Select top 2 solutions" after each paradigm; feasibility pass/fail gate). Not 5 because there is no feedback loop telling Claude what to do when solutions fail the feasibility gate.

4 / 5

Progressive Disclosure

Good section headers make the ~250-line body navigable, but everything is inline with no reference files; the per-paradigm templates are prime candidates for one-level-deep reference files (e.g., references/combinational.md), keeping SKILL.md as an overview with the selection table and integration pipeline.

3 / 5

Total

15

/

20

Passed

Description

76%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.

A strong description that clearly states what the skill does and when to use it, with an unusually good negative-trigger exclusion list. Its main weakness is trigger vocabulary: it uses framework language where more natural user phrasings (brainstorm, ideation, out-of-the-box) would improve discovery.

Suggestions

Add natural trigger synonyms to the 'Use when' clause, e.g. "brainstorming, ideation, out-of-the-box thinking, or when conventional approaches are stuck".

Mention the concrete deliverable (a tiered portfolio of solutions ranked by feasibility, utility, and novelty) to sharpen the 'what' portion.

Include the domain triggers already present in the body ("strategy, design, research direction, or policy") in the description so users in those domains discover the skill.

DimensionReasoningScore

Specificity

Lists several concrete capabilities — "Implements three paradigms — combinational (novel combinations of familiar ideas), exploratory (expand solution space boundaries), transformative (alter fundamental constraints)" — each with a clear definition. Not 5 because it omits deliverables (e.g., a tiered portfolio of solutions) and output specifics, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers "what" (a creative reasoning framework implementing three named paradigms with definitions) and "when" ("Use when the problem has ambiguous goals, vast solution space, no single correct answer, or requires innovation"), plus a negative trigger list ("Do not use for well-defined problems, mathematical puzzles, or tasks requiring convergent reasoning"). Both halves are concrete and explicit.

5 / 5

Trigger Term Quality

Includes some relevant natural phrases ("ambiguous goals", "no single correct answer", "requires innovation") but misses common variations users would actually say such as "brainstorm", "ideation", "out-of-the-box", or "novel ideas". Coverage is moderate rather than good, matching anchor 3.

3 / 5

Distinctiveness Conflict Risk

The niche is distinct (creative reasoning for ill-defined problems) and the explicit exclusion list reduces mis-triggering, but "creative reasoning" and "innovation" still overlap broadly with generic brainstorming/ideation skills. Mostly distinct with minor overlap risk.

4 / 5

Total

16

/

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

Jamie-BitFlight/claude_skills

Path

.claude/skills/universe-of-thoughts/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.