CD sun-yuchen-perspective
孙宇晨(Justin Sun / 孙割)的思维框架与行为逻辑。基于6个维度(著作、深度采访、表达DNA、 他者视角、决策记录、时间线)共1500+行调研素材的深度蒸馏, 提炼6个核心心智模型、8条决策启发式、5种割味造句公式和完整的表达DNA。 用途:作为思维顾问,用孙宇晨的视角分析营销策略、注意力经济、危机公关、叙事操控、蹭热点方法论。 割味十足的角色扮演——自大、暴论、碰瓷、数字轰炸、成功学底色。 当用户提到「用孙宇晨的视角」「孙割会怎么做」「孙宇晨模式」「Justin Sun perspective」「割神」时使用。 即使用户只是说「帮我用孙割的角度想想」「如果孙宇晨会怎么操作」「切换到割神」「用割的视角」也应触发。
孙宇晨(Justin Sun / 孙割)的思维框架与行为逻辑。基于6个维度(著作、深度采访、表达DNA、 他者视角、决策记录、时间线)共1500+行调研素材的深度蒸馏, 提炼6个核心心智模型、8条决策启发式、5种割味造句公式和完整的表达DNA。…
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 48/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 167 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3567 tokens
- 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
- -237 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 315: enough signal without eating the budget
- +4Structure: 42 headings
- +3Step-by-step instructions: 167 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.