SKILLEMALL.ai
GitHub ↗ RU Sign in

CB Portfolio Drift Monitor

Real-time Kalshi portfolio drift alerts — monitors positions and fires when any moves beyond your configured threshold since last check. Snapshot comparison, rate-limited checking, directional emoji indicators. Schedule hourly to catch position swings between morning and evening briefs. Part of the OpenClaw Prediction Market Trading Stack — risk management layer that pairs with Kalshi Command Center and Market Morning Brief.

Not recommendedcritical or high security findings
ClawHub Agent Skills author: kingmadellc v1.1.4 MIT-0 6 files body ≈ 1 920 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process B 68/100 · Nearly there — weak spots: when it triggers, consistency, progress reporting

ProcedureSlackInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
C
71/100
safety, quality, tests
Safety 60%
59
Quality 40%
89
Run on models
none yet
Process rating
B
68/100
Nearly there
Progress reporting w 2
0
When it triggers w 12
20
Consistency w 8
40
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Dangerous commands
If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

Secrets in code medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.

For the author

The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
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 · 3

  • high Dangerous commands cmd-persistence references/drift-config.md:348
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl load ~/Library/LaunchAgents/com.portfolio-drift-monitor.plist
  • high Dangerous commands cmd-persistence references/drift-config.md:354
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl unload ~/Library/LaunchAgents/com.portfolio-drift-monitor.plist
Medium and low: 1
  • medium Secrets in code secret-private-key references/drift-config.md:293
    Private key material (key header without key body; quoted — discussed, not commanded)
    cat $KALSHI_KEY_PATH | head -1  # Should start with "-----BEGIN PRIVATE KEY----- …
    header onlyquoted

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

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)

Process rating: all ten parameters 68/100

  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (Portfolio Drift Monitor) differs from the folder (portfolio-drift-monitor)
  • 60Tools and files. Uses tools (web, git, python) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 43 steps
  • 100Failures and branches. 2 branches, has a failure section
  • 100Execution cost. Instruction body is 1920 tokens
  • 100Running it twice. Mutating operations check current state
  • low 16 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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 428: enough signal without eating the budget
  • +4Structure: 27 headings
  • +3Step-by-step instructions: 43 items
  • +3Output format is stated explicitly
  • +4Has examples (8 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)
  • +3All 1 scripts are documented

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

External checks

ClawHub: suspicious
This appears to be a real Kalshi portfolio monitor, but it under-discloses Slack webhook sending of portfolio details and includes out-of-scope instructions for persistent code changes.
LLM: suspicious (high) · VirusTotal: · 29 May 2026