BD circuit-intimate-therapy
婚姻家庭咨询里用"电路类比"做理论解释、案例诊断、干预方案设计,并在每次回答末尾**生成一个上下文相关的 HTML 交互 app**(写到 ~/circapps/generated/),复用 ~/circapps/ 下 12 个 canonical app 的视觉系统(common.css/common.js)。基于 ~/circintimate.md 把 RLC + DC 偏置 + 复阻抗 + 串/并联共轭 + 二极管(单向 / 阈值 / Zener / 整流)映射到 Miller《亲密关系》第 1–14 章及 Gottman、Karney & Bradbury、Rusbult、Sternberg、Bartholomew、Murray、Leary、Bowen、Christensen & Heavey、Gable、Bolger、Finkel、Johnson。触发关键词:情绪流动 / 关系惯性 / DC 偏置 / 共轭 / 谐振 / 阻尼 / Zener / 整流 / photodiode / 燃烧型 / 室友型 / 隐忍型 / 内耗型 / 击穿型;Gottman 四类型;依恋四类型;Demand-Withdraw;Capitalization;VSA 模型;Forgiveness;Reactance;Sociometer;Negative affect reciprocity。也用于把咨询技术翻译成电路语言、对夫妻做"电路读数"、找一个可演示交互 demo 教概念。使用渐进式披露,按需读取 references/ 与按需推荐 circapps/。
As a process D 43/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: 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")
Process rating: all ten parameters 43/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
- 30Running it twice. 2 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 67 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1852 tokens
- low The response is described with custom markup (3 tags): a typed call is more reliable
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
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +3Description length 684: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 67 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (9 of 9)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.