CC stocks
Stock, ETF, crypto, forex and commodity data from Yahoo Finance. Prices, history, fundamentals, TTM financials, ratios, valuation history, earnings and estimates, dividends, options, holders and insiders, news, market movers, sectors and industries, and earnings, IPO, economic and split calendars.
Stock, ETF, crypto, forex and commodity data from Yahoo Finance.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenscripts/yfinance_ai.py:1358High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)result += f" Price/Sales: {safe_get(info, 'pric…ths')}\n"quoted -
low Secrets in code
secret-high-entropy-tokenscripts/yfinance_ai.py:4837High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)ps = info.get("pric…ths")quoted
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 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
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 20 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1232 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
- -31 of 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 298: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.