Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Cross-module KPIs, financial ratios, trends, and dashboards for ERPClaw — read-only, gracefully degrades when optional skills are missing
Cross-module KPIs, financial ratios, trends, and dashboards for ERPClaw — read-only, gracefully degrades when optional skills are missing
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Umami API timestamps: Use milliseconds, not seconds. Date.now() in JS, int(time.time() * 1000) in Python. Plausible API v2: Requires site_id parameter, NOT domain name. Get site_id from dashboard URL first. PostHog events: Properties must be JSON serializable. Never pass DOM elements or functions. Rate limits: Umami 600/hour, Plausible 600/hour, PostHog 1000/minute. Implement exponential backoff on 429.
Development: ALWAYS use separate project/site for local testing. Production data pollution is irreversible. Tracking domains: Never hardcode. Use env vars to switch between localhost and production. Bot filtering: Enable in settings. Privacy tools have weaker bot detection than Google Analytics.
EU visitors need explicit consent even for privacy-first tools. Check IP geolocation before tracking. Data retention: Set automatic deletion - Umami in Settings > Data, Plausible 30 days max, PostHog in project settings. Cookie-free warning: Umami/Plausible don't use cookies but still need consent for EU visitors if collecting identifiers.
Verify script loads before sending events. Check for umami, plausible, or posthog globals first. Never track PII (email, names, IP) in custom events. Violates privacy principles. Batch PostHog events via /batch endpoint. Umami/Plausible require individual requests.
Store API keys in environment variables only. Never hardcode. Umami: Requires website ID + API key combination. Plausible: Uses Bearer token authentication. PostHog: Uses project-specific API key.
Data access, storage, extraction, analysis, reporting, and insight generation.
Largest current source with strong distribution and engagement signals.