FD soul-forge
从家庭群聊记录(微信/WhatsApp/其他)提炼数字人格。 输出 soul.md(集体人格)+ 每位成员的 persona 文件,可直接用于 AI agent 的人格底座。 关键词:群聊分析、家庭人格、soul、persona、数字人格、聊天记录、微信导出、人格提炼。
As a process D 39/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
The same skill appears in 2 more places: ClawHub, ClawHub
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.
The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.
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
- Remove the critical guard findings (secrets, dangerous commands, hidden instructions): while they stand the skill is blocked and cannot grade above F.
- 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 · 11
-
critical Secrets in code
secret-openai-keypipeline/03_extract_kimi_openclaw.py:20OpenAI-style API key (quoted — discussed, not commanded)API_KEY = os.environ.get("KIMI_API_KEY") or "sk-k…xAI"quoted -
critical Secrets in code
secret-openai-keypipeline/03_extract_kimi_v2.py:19OpenAI-style API key (quoted — discussed, not commanded)API_KEY = "sk-k…xAI"
quoted -
critical Secrets in code
secret-openai-keypipeline/03_extract_simple.py:16OpenAI-style API key (quoted — discussed, not commanded)API_KEY = "sk-k…xAI"
quoted -
critical Secrets in code
secret-openai-keypipeline/04_synthesize_simple.py:15OpenAI-style API key (quoted — discussed, not commanded)API_KEY = "sk-k…xAI"
quoted
Medium and low: 7
-
medium Broad scope
meta-agent-memory-dumpoutputs/soul.mdAgent memory / workspace files bundled with the skill (1) — likely a workspace dump with personal data or tokensoutputs/soul.md
-
medium Secrets in code
secret-labelled-tokenpipeline/03_extract_kimi_v2.py:19Labelled token / key literal (vendor format unknown — verify it is not a live credential)API_KEY = "sk-k…xAI"
-
medium Secrets in code
secret-labelled-tokenpipeline/03_extract_simple.py:16Labelled token / key literal (vendor format unknown — verify it is not a live credential)API_KEY = "sk-k…xAI"
-
medium Secrets in code
secret-labelled-tokenpipeline/04_synthesize_simple.py:15Labelled token / key literal (vendor format unknown — verify it is not a live credential)API_KEY = "sk-k…xAI"
-
low Secrets in code
secret-password-literalpipeline/03_extract_kimi_v2.py:19Hard-coded password / key literal (may be an example)API_KEY = "sk-k…xAI"
-
low Secrets in code
secret-password-literalpipeline/03_extract_simple.py:16Hard-coded password / key literal (may be an example)API_KEY = "sk-k…xAI"
-
low Secrets in code
secret-password-literalpipeline/04_synthesize_simple.py:15Hard-coded password / key literal (may be an example)API_KEY = "sk-k…xAI"
Files scanned: 20. 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 "requires"
Process rating: all ten parameters 39/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. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (soul-forge) differs from the folder (family-analyzer)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 21 steps
- 100Execution cost. Instruction body is 668 tokens
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
- +1No license
- +2Single-language instructions
- +3Description length 135: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 21 items
- +4Has examples (6 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.