FC small-molecule-rd-analysis
分析小分子结构、性质、合成路线和研发风险。适用于:分析小分子结构、理化性质、作用机制、合成路线和研发风险,用于化合物档案、项目评审和药化团队信息准备。
分析小分子结构、性质、合成路线和研发风险。适用于:分析小分子结构、理化性质、作用机制、合成路线和研发风险,用于化合物档案、项目评审和药化团队信息准备。
As a process C 55/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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.
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 · 9
-
critical Secrets in code
secret-openai-keyskill-card.md:40OpenAI-style API key- [Zhihuiya chemical molecule MCP endpoint](https://connect.zhihuiya.com/713886/logic-mcp?apikey=…)
-
critical Secrets in code
secret-openai-keySKILL.md:11OpenAI-style API key (quoted — discussed, not commanded)本技能是化学分子领域的专业情报分析平台,通过集成 MCP 工具(`https://connect.zhihuiya.com/713886/logic-mcp?apikey=…
quoted -
critical Secrets in code
secret-openai-keySKILL.md:41OpenAI-style API key (quoted — discussed, not commanded)**MCP 端点**:`https://connect.zhihuiya.com/713886/logic-mcp?apikey=…
quoted
Medium and low: 6
-
medium Secrets in code
secret-labelled-tokenskill-card.md:40Labelled token / key literal (vendor format unknown — verify it is not a live credential)- [Zhihuiya chemical molecule MCP endpoint](https://connect.zhihuiya.com/713886/logic-mcp?apikey=…)
-
low Secrets in code
secret-password-literalskill-card.md:40Hard-coded password / key literal (may be an example)- [Zhihuiya chemical molecule MCP endpoint](https://connect.zhihuiya.com/713886/logic-mcp?apikey=…)
-
low Secrets in code
secret-labelled-tokenSKILL.md:11Labelled token / key literal (vendor format unknown — verify it is not a live credential) (quoted — discussed, not commanded)本技能是化学分子领域的专业情报分析平台,通过集成 MCP 工具(`https://connect.zhihuiya.com/713886/logic-mcp?apikey=…
quoted -
low Secrets in code
secret-password-literalSKILL.md:11Hard-coded password / key literal (may be an example) (quoted — discussed, not commanded)本技能是化学分子领域的专业情报分析平台,通过集成 MCP 工具(`https://connect.zhihuiya.com/713886/logic-mcp?apikey=…
quoted -
low Secrets in code
secret-labelled-tokenSKILL.md:41Labelled token / key literal (vendor format unknown — verify it is not a live credential) (quoted — discussed, not commanded)**MCP 端点**:`https://connect.zhihuiya.com/713886/logic-mcp?apikey=…
quoted -
low Secrets in code
secret-password-literalSKILL.md:41Hard-coded password / key literal (may be an example) (quoted — discussed, not commanded)**MCP 端点**:`https://connect.zhihuiya.com/713886/logic-mcp?apikey=…
quoted
Files scanned: 3. 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 "copyright"
Process rating: all ten parameters 55/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
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 64 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1249 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- 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)
- +3Description length 75: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 26 headings
- +3Step-by-step instructions: 64 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.