Skills/ClawHub/peakflo-spaces

peakflo-spaces@1.0.2

CAUTION· static only

Publisher claims: "Connect OpenClaw to Spaces by Peakflo, a hosted MCP server for finance and ops work. Hand off one-off or recurring tasks to cloud agents or people, and query workflows, data tables, reports, policy documents and approvals. Sign in with OAuth; no API keys." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher peakflo · publishing for 5 daysInstalls 132Last detonated 4d ago
What would fix thisWatchDispute verdict

Coverage

Static only; nothing was run yet.

The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-10 and scored it 67/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Authorization escalation language. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

HIGH
Authorization escalation languageSKILL.md:55 · Authorization escalation language- In the Control UI, a person with admin access can instead use **+ → Plugins → Add MCP server…** with the same URL, Streamable HTTP and OAuth.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01

No other findings across 177 lines in 4 files.

Cost to the agent

Instructions loaded
≈2,118 tok
1 file · 4 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.

What would make this Verified

13 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim peakflo: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim peakfloPropose a patch to the maintainer