SKILLEMALL.ai

BC investorclaw

Deterministic-first portfolio analyzer — holdings, performance, Sharpe + Sortino, FRED yield curves, bond duration, sector breakdowns, scenario rebalancing — via MCP-HTTP. Backed by ic-engine and clio.

ClawHub Agent Skills author: Jason Perlow v4.10.0 MIT-0 73 files body ≈ 10 327 tokens Open the sourceclawhub.ai analyzed 4 d ago

As a process C 58/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, execution cost

AnalyzerInfrastructureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
83/100
safety, quality, tests
Safety 60%
99
Quality 40%
58
Run on models
none yet
Process rating
C
58/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
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 SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Dangerous commands cmd-cron-mention docs/EOD_REPORT.md:82
    Mentions editing / listing crontab
    # crontab -e

Files scanned: 53. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 10327 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 58/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. 19 mutating operations with no state check
  • 40Execution cost. Instruction body is 10327 tokens: crowds the task out of the window
  • 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 96 steps
  • 100Failures and branches. 11 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 22 top-level sections: this looks like several domains in one skill

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)
  • -2localhost URLs: will not work for another user
  • -410 reference files, but SKILL.md never points to them: the model will not open them
  • +1No license
  • +2Single-language instructions
  • +3Description length 201: enough signal without eating the budget
  • +4Structure: 50 headings
  • +3Step-by-step instructions: 96 items
  • +3Output format is stated explicitly
  • +4Has examples (22 code blocks)

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

External checks

ClawHub: suspicious
InvestorClaw is mostly a legitimate local portfolio-analysis service, but it also persists financial context and provider keys through local web/MCP surfaces with some under-scoped disclosure and hardening gaps.
LLM: suspicious (high) · VirusTotal: · 15 Jun 2026