CtrlK
BlogDocsLog inGet started
Tessl Logo

first-principles-thinking

Systematic first principles thinking for any problem domain. Use when the user says "analyze from first principles", "第一性原理", "从根本分析", "从零开始思考", "think from scratch", "question this design", "is this the right approach", "challenge assumptions", "挑战假设", "为什么要这样做", "有没有更好的方案", "why are we doing it this way", or needs to evaluate decisions, designs, or strategies without relying on analogies, conventions, or "best practices". Also triggers on "这个设计合理吗", "从本质上看", "回到基本面", "what's really true here", "what are we assuming", or any request to decompose a problem to its fundamentals.

71

Quality

89%

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

The canonical home for this skill is first-principles-thinking in mindfold-ai/Trellis

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 well-engineered methodology skill: six gated phases with mandatory artifacts, validation checkpoints, anti-drift and anti-shallow protocols, and a clean one-level-deep reference structure that keeps the deep material out of context. The main cost is token weight — several sections re-explain thinking models, traps, and biases Claude already knows, which pushes ~90KB of references plus a long body against the context budget.

Suggestions

Compress or cut the 'Common Traps', 'Bias Awareness', and 'Complementary Tools Quick Reference' sections to one-line pointers into the existing reference files — the ~60 lines of well-known concepts (sunk cost, 5 Whys, Inversion) are the largest token savings without losing the phase-mapping, which can survive as a single compact table in references/thinking-models-toolkit.md.

Move the Trellis Integration section into its own reference file (e.g. references/trellis-integration.md) and keep only a one-sentence trigger in the body — it is ecosystem-specific dead weight for any non-Trellis project yet occupies ~55 lines of core context.

Tighten the Phase 1 'Essence' and Phase 3 'Ground Truths' key-questions lists to match the template density of Phases 0, 2, and 4 — Phase 1 currently reads as discussion prompts where the other phases specify exact output artifacts.

DimensionReasoningScore

Conciseness

The core methodology (Phases 0–5 with gates, depth standards, progress tracker) is genuinely prescriptive and earns its tokens, but roughly a quarter of the body explains concepts Claude already knows: the 'Common Traps' section (analogy/complexity/legacy traps), the 'Bias Awareness' table (confirmation, anchoring, sunk cost, status quo, overconfidence), and the 'Complementary Tools' and 'Problem Decomposition' tables (Inversion, 5 Whys, Pre-Mortem, Issue Tree, Fishbone). This is 'mostly efficient but includes some unnecessary explanation' — more than the minor trimming of a 4, but far from the padded explaining-from-scratch of a 2, since each known concept is compressed into a compact table mapped to FP phases.

3 / 5

Actionability

For an instruction-only skill, the guidance is fully executable: copy-paste templates for axioms, the assumption table with exact columns and verdict vocabulary (Keep/Discard/Modify), ❌/✅ example pairs with concrete specifics ('P99 latency must be < 200ms per SLA contract §3.2'), a worked reasoning chain, a complete final-output skeleton, hard minimums (≥3 axioms, ≥5 assumptions, ≥3 ground truths), and literal commands for Trellis integration (`python3 ./.trellis/scripts/task.py add-context ...`). The scoring note says absence of code is not penalized when the guidance is actionable — and here it is, down to the exact markdown to emit for the progress tracker and drift-return message.

5 / 5

Workflow Clarity

The six phases (0–5) are strictly sequenced with a mandatory-artifact gate per phase ('No artifact → no next phase. If a gate is not met, stop and complete it.'), a summary gate table defining what each phase must produce and at what minimum depth, a Phase 5 completion gate of three explicit validation questions (traceability, completeness, honesty) that must all be 'yes', an anti-drift protocol with a running progress checklist and a scripted return-from-tangent message, and anti-shallow depth standards that name what failure looks like. This matches the top anchor: clear sequence, explicit validation, feedback loops, and checklists.

5 / 5

Progressive Disclosure

The body is a well-organized overview with clearly signaled, one-level-deep references: each inline pointer uses a blockquote ('> Deep methodology: `references/axiom-based-reasoning.md`'), all five referenced files exist on disk, no reference file points to further references, and a closing Reference Files table gives content description plus 'When to Read' for each. Long-tail material (12-bias catalog, 15 decomposition frameworks, case studies) is correctly summarized in compact tables and split into the reference files rather than inlined, matching the top anchor.

5 / 5

Total

18

/

20

Passed

Description

91%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 explicitly covers what the skill does and when to use it, with unusually thorough bilingual trigger coverage. The main residual risk is that a few very broad trigger phrases ('is this the right approach', 'what are we assuming') could over-trigger it in ordinary design discussions.

DimensionReasoningScore

Specificity

The description lists several distinct actions — 'decompose a problem to its fundamentals', 'evaluate decisions, designs, or strategies', 'challenge assumptions' — going beyond naming the domain. It falls short of 5 because the actions remain process-level verbs rather than the comprehensive, concrete operation list of the top anchor, and the opening 'Systematic first principles thinking for any problem domain' is itself somewhat abstract.

4 / 5

Completeness

It explicitly answers both questions: 'what' via 'Systematic first principles thinking... decompose a problem to its fundamentals' and 'when' via two explicit trigger clauses ('Use when the user says...' and 'Also triggers on...') with concrete quoted trigger phrases. This mirrors the 5-anchor example structure almost exactly; it is not 4 because the 'when' is not merely present but exhaustive with concrete phrases.

5 / 5

Trigger Term Quality

Trigger coverage is comprehensive with natural synonyms in two languages: 'analyze from first principles', '第一性原理', '从根本分析', '从零开始思考', 'think from scratch', 'challenge assumptions', '挑战假设', '有没有更好的方案', 'what's really true here', 'what are we assuming'. These are phrases a user would naturally say when wanting this skill, matching the top anchor's standard of synonym-level coverage.

5 / 5

Distinctiveness Conflict Risk

The niche is clear — first principles decomposition is a distinct methodology with dedicated triggers like '第一性原理' and 'analyze from first principles'. However, broad phrases such as 'is this the right approach', 'why are we doing it this way', and 'what are we assuming' could plausibly fire during general design-review or architecture discussions, creating minor overlap with critical-thinking/design-critique skills, which keeps it below the 'minimal conflict risk' of 5.

4 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository
mindfold-ai/Trellis
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.