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

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

56%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 is well-structured with a clear five-phase workflow, decision matrix, and verification checklist, and it provides actionable templates. Its main weaknesses are verbosity (explaining well-known concepts and asserting unfounded impact statistics) and broken/incorrect bundle references.

Suggestions

Trim or remove explanations of concepts Claude already knows (Five Whys mechanics, cognitive-bias definitions) and drop the unverifiable "IMPACT" percentage claims to tighten token efficiency.

Fix the bundle references: either create the missing `modules/*.md` files or remove the dead links, and correct `examples.md`/`reference.md` paths to `references/examples.md` and `references/reference.md`.

Move the long per-phase detail into the referenced module files so SKILL.md reads as a concise overview pointing one level deep.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose (~330 lines) and explains concepts Claude already knows (the Five Whys technique, definitions of anchoring/confirmation/sunk-cost bias), while padded "WHY"/"IMPACT" lines assert unverifiable statistics ("prevents 40-60% of mid-project pivots", "reduces complexity by 30-50%").	2 / 5
Actionability	As an instruction-only thinking skill it provides concrete checklists, named questions, a weighted-scoring method, and a full Strategic Decision Record template, giving mostly actionable guidance with only minor gaps.	4 / 5
Workflow Clarity	The five-phase process is clearly numbered and sequenced, paired with a "When to Activate" list, a Quick Decision Matrix, and a "Verification" checklist with explicit checkboxes serving as validation checkpoints.	4 / 5
Progressive Disclosure	There is reasonable tiering (Quick Reference / Implementation Guide / Advanced) and references to modules, examples, and reference files, but four referenced `modules/*.md` files do not exist and the `examples.md`/`reference.md` links point at root paths while the actual files live under `references/`, so navigation is partly broken.	3 / 5
	Total	13 / 20 Passed

Description

75%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 is well-constructed: it states what the skill does, names concrete methodologies, and provides explicit "Use for..." trigger guidance. It sits solidly above midpoint across all dimensions, with room only for broader trigger-term coverage.

Suggestions

Expand the "Use when..." clause to list a few more natural trigger phrases users would say (e.g., "trade-off analysis", "choosing between options", "technology selection").

Consider adding synonyms or variant phrasings to broaden natural-keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain plus three concrete named methodologies ("First Principles Analysis, Stanford Design Thinking, and MIT Systems Engineering") and specific use cases ("architecture decisions or root cause analysis"), giving several specific actions with only minor coverage gaps.	4 / 5
Completeness	Explicitly answers both "what" ("Strategic thinking framework integrating ... for deeper problem-solving") and "when" ("Use for architecture decisions or root cause analysis"), with the "when" clause present and concrete but not exhaustively enumerated.	4 / 5
Trigger Term Quality	Includes natural user phrases like "architecture decisions" and "root cause analysis" that a user would actually say, though it misses common synonyms and file-type extensions.	4 / 5
Distinctiveness Conflict Risk	The three named methodologies and concrete triggers carve a mostly-distinct niche with only minor overlap risk against closely related decision-making skills.	4 / 5
	Total	16 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
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
Commit: 4100d87

Reviewed: 2 days 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.