luna/marketingskills
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Files
development
marketingskills/tools/integrations/coupler.md
T
Corey Haines 30f9b9a729 feat: v2.0 skill renames and CRO consolidation (#291) 
* 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>
2026-05-13 22:05:15 -07:00

3.5 KiB
Raw Permalink Blame History

Coupler.io

Data integration platform that connects marketing, sales, analytics, and e-commerce data sources to destinations like spreadsheets, BI tools, and data warehouses with automated scheduling.

Capabilities

Integration Available Notes
API ✓ Importers, Runs, Sources, Destinations
MCP ✓ Claude connector
CLI ✓ coupler.js
SDK - REST API only

Authentication

Common Agent Operations

List Importers

GET https://api.coupler.io/v1/importers

Get Importer Details

GET https://api.coupler.io/v1/importers/{id}

Trigger an Importer Run

POST https://api.coupler.io/v1/importers/{id}/run

Create an Importer

POST https://api.coupler.io/v1/importers

{
  "source_type": "google_analytics",
  "destination_type": "google_sheets",
  "name": "GA4 to Sheets Daily"
}

Delete an Importer

DELETE https://api.coupler.io/v1/importers/{id}

List Runs for an Importer

GET https://api.coupler.io/v1/importers/{id}/runs

Get Run Details

GET https://api.coupler.io/v1/runs/{id}

List Available Sources

GET https://api.coupler.io/v1/sources

List Available Destinations

GET https://api.coupler.io/v1/destinations

Key Metrics

Importer Data

  • id - Importer ID
  • name - Importer name
  • source_type - Source connector type
  • destination_type - Destination connector type
  • schedule - Automation schedule
  • status - Current status
  • last_run_at - Last run timestamp

Run Data

  • id - Run ID
  • importer_id - Parent importer
  • status - Run status (pending, running, completed, failed)
  • started_at - Start timestamp
  • finished_at - Finish timestamp
  • rows_imported - Number of rows processed
  • error - Error message if failed

Parameters

Importer Creation

  • source_type - Source connector (e.g., google_analytics, google_ads, facebook_ads, hubspot, shopify, stripe, airtable)
  • destination_type - Destination connector (e.g., google_sheets, bigquery, snowflake, postgresql)
  • name - Importer name
  • schedule - Automation schedule (e.g., hourly, daily, weekly)

Supported Sources

  • Analytics: Google Analytics, Adobe Analytics
  • Ads: Google Ads, Facebook Ads, LinkedIn Ads, TikTok Ads
  • CRM: HubSpot, Salesforce, Pipedrive
  • E-commerce: Shopify, Stripe, WooCommerce
  • Other: Airtable, Google Sheets, BigQuery, MySQL, PostgreSQL

Supported Destinations

  • Spreadsheets: Google Sheets, Excel Online
  • BI Tools: Looker Studio, Power BI, Tableau
  • Data Warehouses: BigQuery, Snowflake, Redshift
  • Databases: PostgreSQL, MySQL

When to Use

  • Automating marketing data pipelines from ads and analytics platforms
  • Consolidating multi-channel campaign data into a single destination
  • Scheduling recurring data syncs from CRM to spreadsheets or BI tools
  • Building marketing dashboards with fresh data from multiple sources
  • Exporting e-commerce data for reporting and analysis
  • Connecting data sources without writing custom ETL code

Rate Limits

  • Rate limits vary by plan
  • Standard: API access available on Professional and higher plans
  • Importer run frequency depends on plan tier

Relevant Skills

  • analytics
  • ads
  • revops
Reference in New Issue View Git Blame Copy Permalink