ClawHub

Clawver Store Analytics

v1.0.1

Monitor Clawver store performance. Query revenue, top products, conversion rates, growth trends. Use when asked about sales data, store metrics, performance reports, or business analytics.

⭐ 1· 1.8k·6 current·6 all-time
by@nwang783
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (store analytics) match the actions shown in SKILL.md: querying revenue, products, orders, and reviews from api.clawver.store. The only required credential is CLAW_API_KEY which is appropriate for an API-backed analytics integration. Minor metadata inconsistency: SKILL.md lists version 1.1.0 while registry metadata lists 1.0.1 — worth double-checking but not a functional mismatch.
ℹ
Instruction Scope
Instructions are narrowly scoped to calling Clawver API endpoints and to computing basic aggregates. Example code references (curl and Python snippets) only use CLAW_API_KEY. One ambiguity: Python snippets call api.get(...) without shipping an SDK or explaining how 'api' is provided — this is a documentation gap but not malicious. No instructions request reading local files, other env vars, or sending data to third-party endpoints.
✓
Install Mechanism
No install spec and no code files — instruction-only skill. This minimizes disk writes and third-party package installations (low install risk).
✓
Credentials
Only CLAW_API_KEY is required and declared as the primary credential; this is proportionate for an API-based analytics skill. The SKILL.md references Stripe verification as a store-side condition but does not request Stripe secrets (which is appropriate).
✓
Persistence & Privilege
Skill does not request always:true, does not modify other skills or system config, and is user-invocable only. It does not request persistent system privileges.
Assessment
This skill appears internally consistent: it only needs a CLAW_API_KEY and calls api.clawver.store endpoints for analytics. Before installing, verify the CLAW_API_KEY you supply has least privilege (store-read/analytics-only, if possible), confirm the api.clawver.store domain is the official Clawver endpoint, and avoid reusing the same API key across unrelated services. Note the small documentation gaps (version mismatch and an unexplained api.get() client in examples) — you may want to test with a scoped key in a non-production store and confirm returned data and outbound requests. Revoke or rotate the key if anything unexpected appears.

Like a lobster shell, security has layers — review code before you run it.

latestvk971c0qd372dafpxesq2p110kd813t8d

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

📊 Clawdis
EnvCLAW_API_KEY
Primary envCLAW_API_KEY

Comments