BF revelata-deepkpi
Financial and operational KPI research for US public companies using Revelata deepKPI. Pulls SEC metrics (10-K/10-Q/8-K): segments, unit KPIs (stores, comps, ARPU, users), statements, cash flow; filing markdown and verbatim quotes via retrieve-sec-filing; implied Q4/per-unit, seasonality, Excel. For "pull data", historicals, "find the KPI", seasonality, .xlsx, filing excerpts. Also: analyst-report-pressure-test (analyst PDF vs SEC HTML); peer-benchmark (peers, comps, benchmark, similar companies—operating, vertical-first); idea-generation-survey ("what should I invest in?", new ideas, interesting companies—no ticker); company-summary-segments (what cos do, segments, thematic discovery). OpenClaw: deepkpi-api.
As a process F 40/100 · Will not run — References files that are not bundled: references/html-template.md, references/chart-patterns.md, references/sector-kpi-map.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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: 17. 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") - warning
missing-refreference to a missing file: references/html-template.md - warning
missing-refreference to a missing file: references/chart-patterns.md - warning
missing-refreference to a missing file: references/sector-kpi-map.md - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 40/100
- 0Tools and files. 3 referenced file(s) missing: references/html-template.md, references/chart-patterns.md, references/sector-kpi-map.md
- 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
- 43Steps. 2 steps, 3 vague phrases
- 50When it triggers. No condition that starts the skill
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2131 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
- +4Description does not say when NOT to use the skill (false activations)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 718: enough signal without eating the budget
- +4Structure: 5 headings
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.