SKILLEMALL.ai
GitHub ↗ RU Sign in

BC fund-signal-monitor

［何时使用］当用户需要监控基金信号时；当基金季报/年报发布时；当基金经理变更时；当基金规模大幅变化时；当基金业绩异常波动时；当检测到风格漂移时。与 fund-analyzer-pro 配合使用：fund-analyzer-pro 负责主动分析 + 信号监控，本 skill 负责被动监控 + 自动推送（实际实现已集成到 fund-analyzer-pro 的 signal_checker.py）。

ClawHub Agent Skills author: lj22503 v1.1.0 MIT-0 9 files body ≈ 1 274 tokens Open the sourceclawhub.ai↗ analyzed 4 d ago

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

AnalyzerInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
67
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • 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: 9. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "created"
  • note frontmatter-key unknown frontmatter key "skill_type"
  • note frontmatter-key unknown frontmatter key "related_skills"

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. No external tools needed
  • 100Steps. 19 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1274 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
  • -216 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +3Description length 199: enough signal without eating the budget
  • +4Structure: 27 headings
  • +3Step-by-step instructions: 19 items
  • +4Has examples (17 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.

External checks

ClawHub: clean
This is a disclosed, documentation-only fund monitoring skill; users should still verify the separate fund-analyzer-pro implementation before enabling alerts.
LLM: benign (high) · VirusTotal: · 29 May 2026