CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-foundation-philosopher

Strategic thinking framework integrating First Principles Analysis, Stanford Design Thinking, and MIT Systems Engineering for deeper problem-solving. Use for architecture decisions or root cause analysis.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.moai/archive/skills/v3.0/moai-foundation-philosopher/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 well-sequenced and unusually actionable for a thinking-framework skill, with concrete question sets, formats, and a decision-record template. Its two real weaknesses are verbosity — long stretches re-explain standard concepts Claude already knows — and a progressive-disclosure structure whose reference links are broken or mis-rooted, leaving the inlined bulk as the only usable content.

Suggestions

Fix the reference structure: create the four modules/ files (or relink to existing files) and correct 'examples.md'/'reference.md' to references/examples.md and references/reference.md so the Quick Access and deep-dive links resolve.

Trim concept explanations Claude already knows — the bias definitions, Five Whys walkthrough, and generic assumption categories — down to the operational question lists and formats, and remove the invented percentage statistics.

Add an explicit recovery loop to the workflow, e.g. 'If any Verification checklist item fails, return to the corresponding phase and re-run it before finalizing the decision record.'

DimensionReasoningScore

Conciseness

The ~330-line body spends much of its length explaining concepts Claude already knows — definitions of anchoring, confirmation bias, and sunk cost ('Over-reliance on first information encountered', 'Continuing due to past investment'), a walkthrough of the Five Whys, and generic assumption categories — plus padded invented statistics ('prevents 40-60% of mid-project pivots', 'reduces solution complexity by 30-50%'). This is noticeably verbose with several padded sections, matching the 2 anchor rather than the mostly-efficient 3 anchor.

2 / 5

Actionability

For an instruction-only skill the guidance is concrete: per-phase question lists ('What if this assumption turns out to be wrong?'), a five-field assumption documentation format, a weighted scoring method with explicit steps, and a full Strategic Decision Record template. Minor gaps keep it below 5 — the scoring method has no worked example with numbers, and some sections (e.g. the creativity techniques) stay at the level of named prompts rather than executable procedure.

4 / 5

Workflow Clarity

The five phases are explicitly sequenced with per-phase purposes, reinforced by a Quick Decision Matrix mapping task types to phases, time-allocation guidelines, and a closing Verification checklist ('At least two alternative approaches documented before selecting one'). It falls short of the 5 anchor because there is no error-recovery loop — nothing says what to do when a verification item fails or when to revisit an earlier phase.

4 / 5

Progressive Disclosure

The three-tier reading structure (30 seconds / 5 minutes / 10+ minutes) is a good idea, but the actual bundle does not support it: the four module links ('modules/assumption-matrix.md', 'modules/first-principles.md', etc.) point to files that do not exist, and 'examples.md' and 'reference.md' are linked at the skill root while the real files live under references/. Meanwhile the full detail that supposedly lives in the modules is inlined in the 5-minute section. This matches the 2 anchor — content that belongs in separate files is inlined and references are effectively broken — rather than the partially-organized 3 anchor.

2 / 5

Total

12

/

20

Passed

Description

58%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 competent description with a clear what and an explicit 'Use for...' trigger clause, undermined by abstract capability language and a narrow trigger vocabulary relative to the skill's actual scope. It would benefit from naming concrete activities and the trade-off/technology-selection triggers the skill is designed for.

Suggestions

Replace the abstract 'for deeper problem-solving' with concrete actions, e.g. 'Break decisions into first principles, generate and score alternatives, and surface trade-offs and cognitive biases in a documented decision record.'

Expand the 'Use for' clause to include the skill's natural triggers already used in the body: technology/library selection, trade-off analysis, refactoring scope, and breaking-change decisions.

Add a distinguishing phrase (e.g. 'five-phase strategic decision analysis') so the description does not read as a generic planning/analysis skill that conflicts with debugging or planning skills.

DimensionReasoningScore

Specificity

The description names the domain ('Strategic thinking framework') and its three constituent methodologies ('First Principles Analysis, Stanford Design Thinking, and MIT Systems Engineering'), but the actual capability is abstract — 'for deeper problem-solving' names no concrete action. It matches the anchor of naming a domain with identifiable components but not comprehensive concrete actions, and is not merely generic like 'Processes PDF files'.

3 / 5

Completeness

It has a clear 'what' ('Strategic thinking framework integrating... for deeper problem-solving') and an explicit 'when' clause ('Use for architecture decisions or root cause analysis'). The 'when' is genuine but narrow — two trigger conditions for a five-phase framework whose own body lists technology selection, trade-offs, and refactoring scope — so it fits 'both present, when could be more specific' rather than the fully concrete 5 anchor.

4 / 5

Trigger Term Quality

Two natural, plausible user phrases are present ('architecture decisions', 'root cause analysis'), but common variations the skill itself targets are missing from the description — 'trade-off', 'technology/library selection', 'cognitive bias', 'framework selection'. That is some relevant keywords with missing common variations rather than the good-but-incomplete coverage of the 4 anchor.

3 / 5

Distinctiveness Conflict Risk

The methodology trio gives it some distinct identity, but 'Strategic thinking framework' plus 'architecture decisions' and 'root cause analysis' are broad phrases that overlap with debugging, planning, and general analysis skills. It is somewhat specific yet could still trigger for a related skill, matching the 3 anchor rather than the mostly-distinct 4 anchor.

3 / 5

Total

13

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 10 missing

Warning

Total

13

/

16

Passed

Repository

modu-ai/moai-adk

Path

.moai/archive/skills/v3.0/moai-foundation-philosopher/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.