Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Query, analyze, and manage Matomo Analytics with API integration, custom reports, and goal tracking.
Query, analyze, and manage Matomo Analytics with API integration, custom reports, and goal tracking.
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.
On first use, read setup.md for integration guidelines. The skill stores configuration in ~/matomo/.
User needs to query Matomo analytics, generate reports, track goals, or manage their self-hosted analytics. Agent handles API queries, data analysis, visitor insights, and conversion tracking.
Memory lives in ~/matomo/. See memory-template.md for structure. ~/matomo/ โโโ memory.md # Sites, credentials ref, preferences โโโ reports/ # Saved report templates โโโ queries/ # Reusable API query templates
TopicFileSetup processsetup.mdMemory templatememory-template.mdAPI referenceapi.mdReport templatesreports.md
Token is stored in system keychain or env var, never in memory files Refer to credentials by reference name only If user pastes token in chat, warn and suggest secure storage
# Base pattern curl -s "https://{matomo_url}/index.php?module=API&method={method}&idSite={site_id}&period={period}&date={date}&format=json&token_auth={token}" Common methods: VisitsSummary.get โ visitors, visits, pageviews Actions.getPageUrls โ top pages Referrers.getWebsites โ traffic sources Goals.get โ conversion data
PeriodDate FormatExampledayYYYY-MM-DD2025-01-15weekYYYY-MM-DDWeek containing that datemonthYYYY-MM2025-01yearYYYY2025rangeYYYY-MM-DD,YYYY-MM-DD2025-01-01,2025-01-31 Special dates: today, yesterday, last7, last30, lastMonth, lastYear
Always confirm which site before querying Store site list in memory.md with idSite mappings Default to most-used site if configured
Round percentages to 1 decimal Use K/M suffixes for large numbers Compare periods when context helps (vs last week/month) Highlight significant changes (>10% delta)
Batch related queries into single date range when possible Cache recent results in memory for follow-up questions Avoid querying same data repeatedly in conversation
Segments filter data by visitor attributes. Add &segment= to any query: # Mobile visitors only &segment=deviceType==smartphone # From specific country &segment=countryCode==US # Returning visitors who converted &segment=visitorType==returning;goalConversionsSome>0 # Combine with AND (;) or OR (,) &segment=browserCode==CH;operatingSystemCode==WIN Common segment dimensions: deviceType โ smartphone, tablet, desktop browserCode โ CH (Chrome), FF (Firefox), SF (Safari) countryCode โ ISO 2-letter code visitorType โ new, returning referrerType โ direct, search, website, campaign
Wrong idSite โ querying wrong property, misleading data. Always confirm site first. Forgetting token_auth โ 403 or empty response. Token required for all non-public methods. date vs period mismatch โ confusing results. period=range requires date=start,end format. Expecting GA terminology โ Matomo uses "visits" not "sessions", "actions" not "events". Translate mentally. Ignoring segments โ missing the real insight. Segments filter data by visitor attributes.
EndpointData SentPurpose{user_matomo_url}/index.phpAPI method, site ID, date range, auth tokenQuery analytics data No other data is sent externally. All requests go to user's own Matomo instance.
Data that leaves your machine: API queries sent to user's Matomo instance only Auth token included in requests (user-controlled) Data that stays local: Site configurations in ~/matomo/ Report templates No data sent to third parties This skill does NOT: Store auth tokens in plain text Send data to any service except user's Matomo Access files outside ~/matomo/
Install with clawhub install <slug> if user confirms: analytics โ general analytics patterns umami โ privacy-focused analytics api โ REST API integration
If useful: clawhub star matomo Stay updated: clawhub sync
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.