SKILLEMALL.ai
GitHub ↗ RU Sign in

BC mu-pyramid-principle

金字塔原理逻辑教练,支持快捷模式(贴文本自动诊断重组)和引导模式(对话构建金字塔)。触发词:金字塔原理、逻辑诊断、结构化思考、MECE、SCQA、结论先行、帮我理清思路、逻辑有问题、汇报结构。不适用:纯语法修改(用mu-humanizer-minesweeping)、PPT制作(用mu-ippt)、批判性思维提问(用mu-critical-thinking)。

ClawHub Agent Skills author: 木先生iPPT v1.0.2 MIT-0 9 files body ≈ 1 631 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

金字塔原理逻辑教练…

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

Proceduretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
73
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "display_name"
  • note frontmatter-key unknown frontmatter key "visibility"

Process rating: all ten parameters 53/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 100Tools and files. No external tools needed
  • 100Steps. 47 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1631 tokens
  • 100Running it twice. No mutating operations
  • low 13 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -220 emoji in the instructions: noise for the model
  • +2Single-language instructions
  • +3Description length 181: enough signal without eating the budget
  • +4Structure: 31 headings
  • +3Step-by-step instructions: 47 items
  • +4Has examples (8 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.

External checks

ClawHub: clean
This is a Markdown writing-coach skill with some broad activation wording and external links, but no evidence that it runs code, uses credentials, persists data, or exfiltrates content.
LLM: benign (high) · VirusTotal: · 3 Sept 2026