Cursor install notes
- Skill root: this folder (scripts + references live here).
- Vendor source:
~/.cursor/skills/_vendor/ai-marketing-skills/ (git pull to update).
- Telemetry is optional; skip
telemetry/*.py unless you opt in.
- Run Python from this skill directory so relative paths resolve.
- Prefer
python on Windows if python3 is missing.
Closed-Loop Analytics Upgrade
Working directory
cd ~/.cursor/skills/ams-closed-loop-analytics-upgrade
# Windows: cd $env:USERPROFILE\.cursor\skills\ams-closed-loop-analytics-upgrade
Principle
A workflow is not a closed loop until it checks whether the change worked and updates the playbook from that evidence.
For marketing skills, that means pulling analytics after the change window. Manual opinions are useful. Platform truth wins.
Core pattern
- Input: usage logs, recommendations, shipped changes, platform analytics, owner feedback, and cost/runtime data.
- AI action: compare baseline vs candidate, find repeatable signals, and propose a skill/playbook patch.
- Output: candidate patch to a prompt, skill, connector, brief template, scoring rubric, or next-action rule.
- Judgment: success rate, speed, cost, quality, human correction rate, and actual performance delta.
- Self-improvement: promote only if it beats baseline. Otherwise keep testing, rollback, or mark unproven.
Analytics by surface
X/Twitter
Track:
- impressions
- engagement rate
- replies
- reposts
- bookmarks
- profile clicks
- follower delta
- post length
- hook style
- proof number
- CTA type
- topic bucket
Use for:
- title/hook formulas
- longform structure
- CTA patterns
- post timing
- topic scoring
YouTube
Track:
- impressions
- CTR
- average view duration
- retention curve
- watch time
- subscribers gained
- comments
- traffic source
- title/thumbnail/hook metadata
- video length and topic bucket
Use for:
- title formulas
- thumbnail rules
- first-15-second hook
- retention beats
- chapter structure
- Shorts cutdowns
- repurposing guidance
SEO/AEO/GEO
Track:
- GSC clicks, impressions, CTR, average position, query/page mix
- GA4 sessions, engaged sessions, conversions, assisted leads
- Ahrefs rankings, backlinks, traffic estimates, keyword movement
- ClickFlow opportunities
- AI-search / answer-engine visibility where available
- CMS/page change log
Use for:
- content refresh patterns
- AEO/GEO opportunity scoring
- query/page prioritization
- internal linking and schema recommendations
- rollback decisions
Revenue / outbound
Track:
- HubSpot owner, lead, deal, and pipeline movement
- Gong call language, objections, buying signals, and outcomes
- Instantly/Smartlead positive replies, booked meetings, unsubscribes, spam risk
- Metricool/LinkedIn post performance
- GA4/HubSpot attribution
Use for:
- outbound sequence patches
- offer angle scoring
- sales follow-up language
- content-to-pipeline investment decisions
Required readback fields
Every promoted change needs:
- change made
- owner
- baseline window
- candidate window
- source systems pulled
- primary metric
- secondary metrics
- metric winner
- caveats/confounders
- decision: promote / keep testing / rollback / unproven
- next patch
- next readback date
Promotion rules
Promote when:
- the candidate beats baseline on the primary metric, or
- the candidate exposes a repeatable audience/customer signal, and
- downside metrics are not meaningfully worse.
Do not promote when:
- volume is too low
- attribution is too dirty
- the result is explained by seasonality or unrelated campaigns
- the connector failed
- only the author liked it
That last one is harsh but spiritually important.
Safety boundaries
Read-only analytics pulls are fine. External writes still require approval:
- posting to X/LinkedIn/YouTube
- publishing or editing CMS content
- changing ad accounts, bids, budgets, targeting, or creative
- mutating CRM/outbound tools
- sending emails or DMs
- changing credentials or production systems
Output template
# Readback: <skill/change>
## Verdict
Promote / keep testing / rollback / unproven
## Change tested
<what changed>
## Data pulled
| Source | Window | Status |
|---|---|---|
## Baseline vs candidate
| Metric | Baseline | Candidate | Delta | Interpretation |
|---|---:|---:|---:|---|
## Caveats
<confounders and missing data>
## Patch
<what changes in the skill/playbook>
## Next readback
<date + metric>
1---2name: ivx-ams-closed-loop-analytics-upgrade3description: Upgrade marketing workflows so changes are judged by platform analytics, not vibes. Use for closed-loop learning on X, YouTube, SEO, outbound, or paid creative.4---56## Cursor install notes78- Skill root: this folder (scripts + references live here).9- Vendor source: `~/.cursor/skills/_vendor/ai-marketing-skills/` (git pull to update).10- Telemetry is optional; skip `telemetry/*.py` unless you opt in.11- Run Python from this skill directory so relative paths resolve.12- Prefer `python` on Windows if `python3` is missing.1314# Closed-Loop Analytics Upgrade1516## Working directory1718```bash19cd ~/.cursor/skills/ams-closed-loop-analytics-upgrade20# Windows: cd $env:USERPROFILE\.cursor\skills\ams-closed-loop-analytics-upgrade21```2223## Principle2425A workflow is not a closed loop until it checks whether the change worked and updates the playbook from that evidence.2627For marketing skills, that means pulling analytics after the change window. Manual opinions are useful. Platform truth wins.2829## Core pattern30311. **Input**: usage logs, recommendations, shipped changes, platform analytics, owner feedback, and cost/runtime data.322. **AI action**: compare baseline vs candidate, find repeatable signals, and propose a skill/playbook patch.333. **Output**: candidate patch to a prompt, skill, connector, brief template, scoring rubric, or next-action rule.344. **Judgment**: success rate, speed, cost, quality, human correction rate, and actual performance delta.355. **Self-improvement**: promote only if it beats baseline. Otherwise keep testing, rollback, or mark unproven.3637## Analytics by surface3839### X/Twitter40Track:41- impressions42- engagement rate43- replies44- reposts45- bookmarks46- profile clicks47- follower delta48- post length49- hook style50- proof number51- CTA type52- topic bucket5354Use for:55- title/hook formulas56- longform structure57- CTA patterns58- post timing59- topic scoring6061### YouTube62Track:63- impressions64- CTR65- average view duration66- retention curve67- watch time68- subscribers gained69- comments70- traffic source71- title/thumbnail/hook metadata72- video length and topic bucket7374Use for:75- title formulas76- thumbnail rules77- first-15-second hook78- retention beats79- chapter structure80- Shorts cutdowns81- repurposing guidance8283### SEO/AEO/GEO84Track:85- GSC clicks, impressions, CTR, average position, query/page mix86- GA4 sessions, engaged sessions, conversions, assisted leads87- Ahrefs rankings, backlinks, traffic estimates, keyword movement88- ClickFlow opportunities89- AI-search / answer-engine visibility where available90- CMS/page change log9192Use for:93- content refresh patterns94- AEO/GEO opportunity scoring95- query/page prioritization96- internal linking and schema recommendations97- rollback decisions9899### Revenue / outbound100Track:101- HubSpot owner, lead, deal, and pipeline movement102- Gong call language, objections, buying signals, and outcomes103- Instantly/Smartlead positive replies, booked meetings, unsubscribes, spam risk104- Metricool/LinkedIn post performance105- GA4/HubSpot attribution106107Use for:108- outbound sequence patches109- offer angle scoring110- sales follow-up language111- content-to-pipeline investment decisions112113## Required readback fields114115Every promoted change needs:116117- change made118- owner119- baseline window120- candidate window121- source systems pulled122- primary metric123- secondary metrics124- metric winner125- caveats/confounders126- decision: promote / keep testing / rollback / unproven127- next patch128- next readback date129130## Promotion rules131132Promote when:133- the candidate beats baseline on the primary metric, or134- the candidate exposes a repeatable audience/customer signal, and135- downside metrics are not meaningfully worse.136137Do not promote when:138- volume is too low139- attribution is too dirty140- the result is explained by seasonality or unrelated campaigns141- the connector failed142- only the author liked it143144That last one is harsh but spiritually important.145146## Safety boundaries147148Read-only analytics pulls are fine. External writes still require approval:149150- posting to X/LinkedIn/YouTube151- publishing or editing CMS content152- changing ad accounts, bids, budgets, targeting, or creative153- mutating CRM/outbound tools154- sending emails or DMs155- changing credentials or production systems156157## Output template158159```markdown160# Readback: <skill/change>161162## Verdict163Promote / keep testing / rollback / unproven164165## Change tested166<what changed>167168## Data pulled169| Source | Window | Status |170|---|---|---|171172## Baseline vs candidate173| Metric | Baseline | Candidate | Delta | Interpretation |174|---|---:|---:|---:|---|175176## Caveats177<confounders and missing data>178179## Patch180<what changes in the skill/playbook>181182## Next readback183<date + metric>184```