CC wendian-markethot-skill
This Skill is powered by the **Wendian Starmap (问象星图)** professional stock data analytics platform, exposing core market intelligence endpoints for **real-time quotes**, **K-line/OHLC bars**, **heatmaps**, and **sector rotation analytics**. It supports natural-language or direct API access to: 1) **Real-time market data** — heatmap snapshots (sector/stock heat), global index spot quotes, single-symbol and batch K-line data; 2) **Calendar & reference data** — trading calendar and stock basic info for screening, search, and business-logic gating; 3) **Heatmap & sector rotation (proprietary algorithms)** — sector/stock heat matrices, market-wide heat aggregate index, and per-stock concept heatmaps that visualize cross-sector rotation momentum; 4) **Concepts & constituents** — concept/theme list, batch concept constituents, and reverse lookup of a stock's concept memberships, supporting sector selection and linkage analysis. This skill provides authoritative, low-latency market and heat data for LLMs and applications, ideal for heatmap visualization, rotation analysis, and quantitative research workflows.
As a process C 55/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, consistency
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Shorten the description to 1024 characters.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
net-credential-useSKILL.md:482Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl.exe -X GET "https://markethot.wendian.net/app-api/member/skill-data/heatmap/realtime?limit=5&source=…&type=…" -H "Content-Type: application/json" -H "X-API-Key: $apiKey"
vendor-host
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1118 chars, limit 1024 - warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: This Skill is powered by the **Wendian Starmap (问象星图)** profession… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 5670 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "required_env_vars" - note
frontmatter-keyunknown frontmatter key "credentials"
Process rating: all ten parameters 55/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 40Consistency. Frontmatter name (wendian-markethot-skill) differs from the folder (wendian-stock-skill)
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 5670 tokens
- 100Steps. 32 steps
- 100Failures and branches. 1 branches, has a failure section
- low 13 top-level sections: this looks like several domains in one skill
- 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 1118: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 34 headings
- +3Step-by-step instructions: 32 items
- +3Output format is stated explicitly
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 25.