SkillAgentSearch skills...

closed-loop-analytics-upgrade

Upgrade marketing, content, SEO/AEO/GEO, and revenue skills so changes are judged by platform analytics instead of vibes

Install / Use

npx skills add ericosiu/ai-marketing-skills --skill closed-loop-analytics-upgrade

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Category

Automation

Supported Platforms

Universal

Tags

Our assessment of closed-loop-analytics-upgrade

closed-loop-analytics-upgrade scores 87/100 on our quality scale, 1652nd of 2,780 Automation skills we index.

Its SKILL.md is 4.2 KB long, well organised into 20 sections with 1 code example: a solid amount of guidance for an agent.

With 3,573 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
17/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so closed-loop-analytics-upgrade is actively maintained.
  • Our last check on 2026-11-02 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

closed-loop-analytics-upgrade compared with similar skills

All 4 of these similar skills score higher than closed-loop-analytics-upgrade; compare them before choosing.

SkillScoreStarsUpdatedFormat
closed-loop-analytics-upgrade (this skill)by ericosiu873.6k55d agoSKILL.md
Agent-Reachby Panniantong100112.3k9d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install closed-loop-analytics-upgrade?
Run npx skills add ericosiu/ai-marketing-skills --skill closed-loop-analytics-upgrade. The install tabs above show the steps for each supported agent.
Which AI agents does closed-loop-analytics-upgrade work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is closed-loop-analytics-upgrade safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is closed-loop-analytics-upgrade still maintained?
The repository was last updated about 2 months ago, so closed-loop-analytics-upgrade is actively maintained.

name: closed-loop-analytics-upgrade description: Upgrade marketing, content, SEO/AEO/GEO, and revenue skills so changes are judged by platform analytics instead of vibes. Use when applying closed-loop learning to X, YouTube, SEO, AEO/GEO, outbound, paid creative, or revenue workflows.

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

  1. Input: usage logs, recommendations, shipped changes, platform analytics, owner feedback, and cost/runtime data.
  2. AI action: compare baseline vs candidate, find repeatable signals, and propose a skill/playbook patch.
  3. Output: candidate patch to a prompt, skill, connector, brief template, scoring rubric, or next-action rule.
  4. Judgment: success rate, speed, cost, quality, human correction rate, and actual performance delta.
  5. 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>

Related Skills

View on GitHub
GitHub Stars3.6k
CategoryAutomation
Updated1mo ago
Forks684

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions
closed-loop-analytics-upgrade — Universal Skill: Install & Safety Check | SkillAgent