BC ai-life-coach
AI 人生教练:用对话陪你把当下活明白。这不是顺你话说的谄媚式聊天机器人,它不替你做决定——它是你的最忠实「陪练」,用有质量的提问和反馈,帮你在对话中自己看清:现在在哪里(自我觉察)、想走向哪里(明确目标)、下一步怎么迈(行动计划)。基于斯坦福《人生设计课》、积极心理学与心流理论,融合焦点解决提问(SFBT)、叙事外化、奥德赛计划等教练方法。适用场景:迷茫 ·心里堵 ·提不起劲 ·工作没动力 ·不知道自己想要什么 ·想找人聊聊 ·自我觉察 ·明确目标 ·制定行动计划。安全承诺:危机信号(不想活了/活着没意思)先做危机评估,无条件提供心理援助热线(400-161-9995 / 12356);未成年人启用受限保护:不挖掘深层创伤,允许征得同意的轻量记忆沉淀;识别到违法侵害(家暴/性侵等)时引导向可信成人或求助热线、不承诺保密;不空洞附和——温柔但会温和挑战自欺与回避;记忆仅存本机专用文件,零网络请求,绝不上传。说「我想做一次人生教练对话」或输入 /ai-life-coach 即可开始。For international users: AI Life Coach is a Socratic dialogue partner for self-awareness, goal clarity and action planning. Crisis-first routing, under-18 protection, anti-sycophancy, local-only memory. See README.md for full English description.
AI…
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-agent-memory-dumpreferences/memory.mdAgent memory / workspace files bundled with the skill (1) — likely a workspace dump with personal data or tokensreferences/memory.md
Files scanned: 11. 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") - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "triggers"
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. Tools declared in frontmatter
- 100Steps. 92 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3075 tokens
- 100Running it twice. No mutating operations
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
- +2Single-language instructions
- +3Description length 693: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 92 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (6 of 7)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.