SKILLEMALL.ai

BF gangtise-data

通过 Gangtise 金融 Open API 拉取结构化量化数据,包括日K行情、财务三大报表、主营构成与估值分位等。需在 scripts 目录配置授权(.authorization),证券参数须为完整代码(如 600519.SH)。当用户需要可落盘的表格化行情与基本面数据时使用。

ClawHub Agent Skills author: GangtiseGts v1.4.3 MIT-0 15 files body ≈ 1 102 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process F 35/100 · Will not run — References files that are not bundled: scripts/*.py, scripts/.authorization

IntegrationInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
60
Run on models
none yet
Process rating
F
35/100
Will not run
References files that are not bundled: scripts/*.py, scripts/.authorization
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
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.
  2. The text references files that are not there: add them or drop the references.
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: 15. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 12, column 22: description: 用于配置ak/sk, 内容为{"accessKey": "<ak>", "secretAccessKey": "<s… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: scripts/*.py
  • warning missing-ref reference to a missing file: scripts/.authorization

Process rating: all ten parameters 35/100

Will not run. References files that are not bundled: scripts/*.py, scripts/.authorization
  • 0Tools and files. 2 referenced file(s) missing: scripts/*.py, scripts/.authorization
  • 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
  • 100Steps. 8 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1102 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
  • +1No license
  • +2Single-language instructions
  • +3Description length 141: enough signal without eating the budget
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 8 items
  • +4Has examples (15 code blocks)
  • +4Reference files are cited in the instructions (6 of 6)
  • +3All 7 scripts are documented

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

External checks

ClawHub: suspicious
The skill mostly matches its financial-data purpose, but one shareholder API path can send its authorization token to an undocumented environment-chosen URL.
LLM: suspicious (high) · VirusTotal: · 29 May 2026