BC kungfu_finance
Mainland China A-share stock and sector analysis tool (中国A股个股与板块分析). Current repo build focuses on stable deterministic products for stock snapshots, basic finance indicators, chip/price levels, sector detail lookup, plus bucket, phase-2 strategy, researcher, bayesian monitor, and preview stock/sector deep research flows.
As a process C 58/100 · Has gaps — weak spots: result and completion, consistency, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Risky intent
intent-offensive-securityreferences/research-flows/sector-analysis/modules/step-4-thesis.md:50Offensive-security / dual-use content (legitimate for authorised testing; review intended use)### 4.8 反面审查 (Red Team Review) ⭐⭐ 独立步骤 — 防止确认偏误的最后防线
-
low Risky intent
intent-offensive-securityreferences/research-flows/sector-analysis/modules/step-4-thesis.md:59Offensive-security / dual-use content (legitimate for authorised testing; review intended use)### 反面审查 (Red Team Review)
-
low Risky intent
intent-offensive-securityreferences/research-flows/stock-analysis/modules/step-5-thesis.md:121Offensive-security / dual-use content (legitimate for authorised testing; review intended use)## 5.3 反面审查 (Red Team Review)
Files scanned: 80. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 6148 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 58/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 12 mutating operations with no state check
- 40Consistency. Frontmatter name (kungfu_finance) differs from the folder (kungfu-finance)
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 6148 tokens
- 100Steps. 174 steps
- 100Failures and branches. 10 branches, has a failure section
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 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
- +1No license
- +2Single-language instructions
- +3Description length 323: enough signal without eating the budget
- +4Structure: 63 headings
- +3Step-by-step instructions: 174 items
- +4Has examples (31 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.