Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Closed Loop Analytics Upgrade

ASecurity

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.

7 stars
0 votes
0 copies
0 views
Added 9/20/2026
ai-agentsgotestingperformance

Works with

cli

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add unempyd/revenueos --skill closed-loop-analytics-upgrade --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Closed Loop Analytics Upgrade?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Closed Loop Analytics Upgrade
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/unempyd-closed-loop-analytics-upgrade/badge)](https://www.skillsdirectory.com/skills/unempyd-closed-loop-analytics-upgrade)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
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

```markdown
# 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>
```

Attribution

unempydunempyd
View sourceMore from unempyd →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Caveman

Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.

1023331 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3331 votes

catchup

Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.

611 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →