AC sina-market
Fetch and inspect market data from Sina Finance public webpage resources across multiple market types. Use when a user wants A-share quotes, Hong Kong stock quotes, domestic futures quotes, futures page metadata, Chinese futures name to contract-code detection, contract/month discovery, code validation, or a unified Sina-based market lookup workflow involving symbols such as 600519, 000001, 00700, AG0, AU0, SC0, PG2607, EB2607, MA2605, or Chinese inputs such as 甲醇2605, 白银2606, 沥青2606.
Fetch and inspect market data from Sina Finance public webpage resources across multiple market types.
As a process C 60/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, progress reporting
The same skill appears in 1 more place: ClawHub
How to improve
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
edit-residuethe text marks something as outdated (lines 124): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 60/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
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 36 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 885 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)
- +1No license
- +2Single-language instructions
- +3Description length 489: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 36 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 94.