30f9b9a729
* feat: v2.0 skill renames and CRO consolidation BREAKING CHANGE: Users must reinstall skills after this update. ## Skill Renames (16) - ab-test-setup → ab-testing - analytics-tracking → analytics - aso-audit → aso - competitor-alternatives → competitors - email-sequence → emails - free-tool-strategy → free-tools - launch-strategy → launch - onboarding-cro → onboarding - paywall-upgrade-cro → paywalls - popup-cro → popups - pricing-strategy → pricing - product-marketing-context → product-marketing - referral-program → referrals - schema-markup → schema - signup-flow-cro → signup - social-content → social ## Consolidations (1) - page-cro + form-cro → cro (form content in references/form.md) ## Why 2.0? - Shorter, cleaner skill names - Consistent naming (no -strategy, -setup, -cro suffixes) - All cross-references updated across 100+ files Total skills: 40 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix(v2.0): update evals for renamed skills, fix validate script, clear warnings - Update 32 evals.json files to reference new skill names (page-cro → cro, product-marketing-context → product-marketing, etc.) — these were missed in the initial v2.0 rename pass since only SKILL.md and marketplace.json were updated. - Fix validate-skills.sh: replace GNU-only `head -n -1` with portable awk so frontmatter extraction works on macOS. - Move Copy Editing Checklist (56 lines) to references/checklist.md to bring copy-editing SKILL.md under the 500-line limit (508 → 457). - Add "see X" pointers to marketing-psychology description for skill discovery (cro, pricing, copywriting). - Update skill-request.yml issue template placeholder (page-cro → cro). All 40 skills now pass validation with zero warnings. * fix(v2.0): add evals for 8 missing skills, strip stale frontmatter from cro/form.md Adds 48 new eval cases (6 per skill) for skills that previously had no evals: aso, co-marketing, community-marketing, competitor-profiling, directory-submissions, image, lead-magnets, video. All 40 skills now have eval coverage (251 total cases). Strips leftover frontmatter from skills/cro/references/form.md — it was inherited from the old form-cro SKILL.md before consolidation. Reference files don't need frontmatter. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): rename paid-ads → ads One more v2.0 simplification — drops the redundant 'paid-' qualifier. Updates the skill directory, SKILL.md frontmatter, evals.json, README skill table, the v2.0 rename table in VERSIONS.md (now 17 renames), and all cross-references in related skills (ad-creative, aso, competitor-profiling, customer-research, lead-magnets, marketing-ideas) plus the tools/integrations guides. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): bump SKILL.md frontmatter version to 2.0.0 for all 40 skills VERSIONS.md was already updated to 2.0.0 but the metadata.version field inside each SKILL.md was still on 1.x. That mismatch would have caused the update-check flow to perpetually report 'update available' since it compares VERSIONS.md against local SKILL.md metadata versions. Caught by codex review (P1). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): add legacy product-marketing-context.md filename fallback Before this fix, users upgrading from v1.x who had a `product-marketing-context.md` file would lose automatic context loading — every skill only checked the new `product-marketing.md` filename. Now all 40 skills also accept the legacy filename (in either `.agents/` or `.claude/`), and the README migration command covers both legacy and current filenames. Caught by codex review (P1 + P2). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): re-sort README skills table alphabetically, fix ads box width The skills table had a few entries out of alphabetical order from the renames (co-marketing was after cold-email, ads was at the renamed position). Re-sorted alphabetically per sync-skills.js. Also padded the 'ads' cell in the ASCII flow diagram to keep the box width consistent. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): document folder cleanup on upgrade, stop sync-skills from re-adding skills array README upgrade guide now includes: - A clear cleanup step for stale v1.x skill folders (renamed + consolidated) so users don't end up with both old and new folders side-by-side after upgrading - The full v1 to v2 rename map for reference - Existing product-marketing-context.md migration steps (preserved) sync-skills.js no longer (re-)introduces a `skills` array on marketplace.json -- Claude Code's plugin schema discovers skills via the `skills/` directory, and the explicit array was failing validation. The script now refreshes the description count and strips the stale array if present. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
4.1 KiB
4.1 KiB
Plausible Analytics
Privacy-focused, open-source web analytics with a simple API for stats queries without cookies or personal data collection.
Capabilities
| Integration | Available | Notes |
|---|---|---|
| API | ✓ | Stats v2 Query, Sites Provisioning, Goals, Shared Links |
| MCP | - | Not available |
| CLI | ✓ | plausible.js |
| SDK | - | REST API only |
Authentication
- Type: Bearer Token
- Header:
Authorization: Bearer {api_key} - Get key: https://plausible.io/settings > API Keys
- Note: Sites API requires Enterprise plan
Common Agent Operations
Stats Query (v2)
POST https://plausible.io/api/v2/query
{
"site_id": "example.com",
"metrics": ["visitors", "pageviews", "bounce_rate", "visit_duration"],
"date_range": "30d"
}
Top Pages
POST https://plausible.io/api/v2/query
{
"site_id": "example.com",
"metrics": ["visitors", "pageviews"],
"date_range": "30d",
"dimensions": ["event:page"]
}
Traffic Sources
POST https://plausible.io/api/v2/query
{
"site_id": "example.com",
"metrics": ["visitors", "bounce_rate"],
"date_range": "30d",
"dimensions": ["visit:source"]
}
Time Series
POST https://plausible.io/api/v2/query
{
"site_id": "example.com",
"metrics": ["visitors", "pageviews"],
"date_range": "30d",
"dimensions": ["time:day"]
}
Breakdown by Country
POST https://plausible.io/api/v2/query
{
"site_id": "example.com",
"metrics": ["visitors", "percentage"],
"date_range": "30d",
"dimensions": ["visit:country"]
}
Filtered Query (specific page)
POST https://plausible.io/api/v2/query
{
"site_id": "example.com",
"metrics": ["visitors", "pageviews", "bounce_rate"],
"date_range": "30d",
"filters": [["is", "event:page", ["/pricing"]]]
}
Realtime Visitors (v1)
GET https://plausible.io/api/v1/stats/realtime/visitors?site_id=example.com
List Sites
GET https://plausible.io/api/v1/sites
Key Metrics
Available Metrics
visitors- Unique visitorsvisits- Total visits (sessions)pageviews- Total page viewsviews_per_visit- Pages per sessionbounce_rate- Bounce rate percentagevisit_duration- Average session duration (seconds)events- Total eventsconversion_rate- Goal conversion ratetime_on_page- Average time on pagescroll_depth- Average scroll depthpercentage- Share of total
Available Dimensions
event:page- Page pathevent:goal- Goal namevisit:source- Traffic sourcevisit:referrer- Referrer URLvisit:channel- Traffic channelvisit:utm_source,visit:utm_medium,visit:utm_campaign- UTM paramsvisit:device- Device typevisit:browser- Browser namevisit:os- Operating systemvisit:country,visit:region,visit:city- Locationvisit:entry_page,visit:exit_page- Entry/exit pagestime,time:day,time:week,time:month- Time periods
Parameters
Stats Query (v2)
site_id(required) - Domain registered in Plausiblemetrics(required) - Array of metrics to returndate_range(required) - Time period: "day", "7d", "30d", "month", "6mo", "12mo", "year", or custom ["2024-01-01", "2024-01-31"]dimensions- Array of dimensions to group byfilters- Array of filter conditions:[operator, dimension, values]order_by- Array of sort specs:[[metric, "desc"]]pagination-{ "limit": 100, "offset": 0 }
Filter Operators
is/is_not- Exact matchcontains/contains_not- Substring matchmatches/matches_not- Wildcard match
When to Use
- Privacy-first web analytics without cookies
- Simple, lightweight traffic analysis
- UTM campaign performance tracking
- Goal and conversion tracking
- Geographic and device breakdown
- GDPR/CCPA-compliant analytics alternative to GA4
Rate Limits
- 600 requests/hour per API key
- All requests must be over HTTPS
Relevant Skills
- analytics
- content-strategy
- programmatic-seo
- cro
- utm-tracking