Ab Testing
coreyhaines31/marketingskills
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program.
When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task.
$ npx skills add Nexus-JPF/note-companion --skill marketing-loops -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Nexus-JPF/note-companion marketing-loops --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/marketing-loops .claude/skills/marketing-loops && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "marketing-loops" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/marketing-loops into .claude/skills/marketing-loops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-loops", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/marketing-loopsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Nexus-JPF/note-companion --skill marketing-loops -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Nexus-JPF/note-companion marketing-loops --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/marketing-loops .agents/skills/marketing-loops && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "marketing-loops" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/marketing-loops into .agents/skills/marketing-loops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-loops", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Nexus-JPF/note-companion --skill marketing-loops -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Nexus-JPF/note-companion marketing-loops --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/marketing-loops .cursor/skills/marketing-loops && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "marketing-loops" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/marketing-loops into .cursor/skills/marketing-loops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-loops", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Nexus-JPF/note-companion.git --path .agents/skills/marketing-loops--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Nexus-JPF/note-companion --skill marketing-loops -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Nexus-JPF/note-companion marketing-loops --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/marketing-loops .gemini/skills/marketing-loops && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "marketing-loops" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/marketing-loops into .gemini/skills/marketing-loops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-loops", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Nexus-JPF/note-companion marketing-loopsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Nexus-JPF/note-companion --skill marketing-loops -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/marketing-loops .github/skills/marketing-loops && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "marketing-loops" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/marketing-loops into .github/skills/marketing-loops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-loops", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Nexus-JPF/note-companion --skill marketing-loops -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Nexus-JPF/note-companion marketing-loops --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/marketing-loops .opencode/skills/marketing-loops && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "marketing-loops" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/marketing-loops into .opencode/skills/marketing-loops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-loops", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
marketing-loopsWhen the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task.
Marketing Loops is an agent skill from Nexus-JPF/note-companion. When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task. Also use when the user mentions 'marketing loop,' 'recurring marketing workflow,' 'automate my marketing,' 'marketing on autopilot,' 'weekly marketing review,' 'ad fatigue check,' 'content refresh loop,' 'churn watch,' 'ranking drop alert,' 'always-on marketing,' 'marketing automation workflow,' or 'run this every week.' Use this to…
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `evals/evals.json`, `references/loop-catalog.md` and `references/loop-guardrails.md`).
It sits in Marketing & SEO, covering A/B testing and Workflow automation. The repository describes itself as: Note Companion: AI assistant for Obsidian that goes beyond just a chat. (prev File Organizer 2000). The licence is MIT.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 9cad635. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Marketing Loops loads about 2.2k tokens when it runs, and up to ~18k if it reads all its reference files. Until then it costs about 185 tokens; SKILL.md has 1,158 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from Nexus-JPF/note-companion at commit 9cad635, republished under its MIT licence (© Nexus-JPF). 1,158 words, ~2,245 tokens.
.claude/skills/marketing-loops/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.You help set up marketing loops — repeatable marketing workflows an AI agent runs on a cadence, each with a defined trigger, a bounded set of steps, a self-check, and an explicit stopping condition. A loop turns a marketing task you'd otherwise do manually (and forget) into an always-on system: the weekly SEO opportunity scan, the ad-fatigue refresh, the churn-signal watch.
This is the operational cousin of marketing-ideas. Ideas tell you what to try once. Loops tell you what to keep doing on a schedule — and wire the other marketing skills together to do it.
Check for product marketing context first: if .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md), read it before asking questions. Use that context and only ask for what's missing.
Then:
references/loop-catalog.md — or adapt the closest one.references/loop-guardrails.md.Building more than one loop, or a whole marketing operating system? See references/loop-orchestration.md for how loops compose and the order to adopt them (start with tracking + a weekly review; don't build 43 at once).
Every loop in the catalog has these nine parts. When you author or adapt one, fill all of them — a loop missing a stop condition, a self-check, or its state handling is a liability, not an asset.
| Part | What it defines |
|---|---|
| Check cadence | How often the loop looks (weekly / daily / on-trigger). Match it to signal speed. |
| Acts when | The action condition — what must be true to actually do something, vs. just check and skip. Most runs of a good loop are "checked, nothing to do." |
| Purpose | The one outcome this loop exists to move. |
| Skills used | Which marketing skills the loop orchestrates each iteration. |
| Loop body | The ordered steps run each iteration. |
| Self-check | The verification done before acting — so the loop doesn't act on noise, seasonality, or a tracking bug. |
| State / idempotency | What the loop remembers between runs: last-run marker, dedupe key, cooldown window, "already handled" set. Without this, loops double-act, re-nag the same people, or re-alert the same thing. Non-negotiable for anything scheduled — see references/loop-state.md for where state lives and the idempotency patterns. |
| Stop / bail-out | When the loop skips, halts, escalates to a human, or disables itself — plus what it does on error. Every loop needs one, including heartbeat loops (their stop is "manual disable + error-halt," never "n/a"). |
| Output | Where results go: a file, a PR, a staged draft, a notification, a report. |
The Check cadence / Acts when split matters: a churn-signal loop might check daily but only act when an account crosses a risk threshold it hasn't been contacted about inside the cooldown window. Conflating the two produces loops that either miss the window or spam.
Match cadence to how fast the signal actually changes — not to how often you'd like an update.
| Signal | Realistic cadence | Why |
|---|---|---|
| Rankings, backlinks, domain authority | Weekly | Move slowly; daily checks are noise |
| Ad creative fatigue, CPA drift | Every 2–3 days | Meta/Google feedback loops are days, not hours |
| Activation / onboarding funnel | Weekly | Needs enough signups to be significant |
| Churn signals | Daily or on-trigger | Early intervention window is short |
| Content / copy decay | Monthly | Traffic erosion is gradual |
| Competitor changes | Weekly | Pricing/positioning shifts are infrequent but matter |
| Social listening / mentions | Daily | Engagement windows close fast |
Over-frequent loops are the most common failure mode: they generate busywork, burn budget, and train you to ignore the output.
Not everything should be automated on a cadence. Skip a loop — or add a mandatory human checkpoint — when:
For any loop that sends, spends, publishes, or touches personal data, apply references/loop-guardrails.md — the two-tier action model (autonomous-safe vs. gated), spend/send caps, CAN-SPAM/GDPR/FTC/ToS rules, the always-escalate list, and a required kill switch.
These loops are agent-agnostic — the body works in any agent. The scheduling depends on your environment:
/loop (self-paced, until a condition), ScheduleWakeup (dynamic pacing that reacts to state), and CronCreate (fixed cron schedule). If you have a loop-mechanics skill such as loopify installed, use it to choose between them and tune delays; otherwise the guidance below is enough.0 9 * * 1 for Mondays 9am, etc.).Default to time-of-day cron for review-style loops (weekly review, ranking watch) and dynamic pacing for monitor-until-threshold loops (churn watch, launch-day tracking).
references/loop-catalog.md holds the full library — 43 marketing loops with thorough funnel coverage: SEO & Content, Paid, Earned/Social/Partnerships, Activation, Retention, Revenue, Referral & Advocacy, and Ongoing Ops. Each is a complete, adaptable spec. Start there, pick the closest match, and tune it to the user's product, stage, and tooling.
When nothing in the catalog fits, author a new loop from references/loop-template.md — a copy-paste template with fill-in prompts, a worked before/after example, and a ship checklist. Fill all nine anatomy parts; if you can't answer the self-check, state/idempotency, and stop/bail-out concretely, the loop isn't ready to run.
Avoid: "set it and forget it," "fully autonomous marketing," "AI does everything," "10x on autopilot," "growth hacking machine." Loops are disciplined systems with checkpoints, not magic. Describe them honestly.
ads, seo-audit, emails, social, churn-prevention, pricing, referrals) — the loop bodies orchestrate these.© Nexus-JPF, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 6 other files (references) in .agents/skills/marketing-loops of Nexus-JPF/note-companion.
Open the folder on GitHubat commit 9cad635
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Nexus-JPF/note-companion, which our catalogue first saw on October 7, 2026.
Marketing Loops next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Marketing Loops this skillNexus-JPF/note-companion | 870 | 1 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Ab Testingcoreyhaines31/marketingskills | 54k | 3 repos | ~3.1k | Automated safety check: Pass | MIT | |
| Ad Test Designeraaron-he-zhu/aaron-marketing-skills | 2.9k | 2 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Ab Test Analyzeririnabuht12-oss/marketing-skills | 4.1k | — | ~1.4k | Automated safety check: Pass | None | |
| Ab Test Store Listingappeeky/aso-skills | 2.2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Ab Test Setupfreekmurze/dotfiles | 1k | 14 repos | ~1.8k | Automated safety check: Pass | None |
coreyhaines31/marketingskills
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program.
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "design an A/B test", "set up a creative/landing test", "run an incrementality test", or "is this result statistically and practically material?"…
irinabuht12-oss/marketing-skills
Statistical significance calculator for A/B test results with sample size requirements, segment breakdowns, and hypothesis generation.
appeeky/aso-skills
When the user wants to A/B test App Store product page elements to improve conversion rate.
freekmurze/dotfiles
When the user wants to plan, design, or implement an A/B test or experiment.
sundial-org/skills
Transform Claude Code into an AI Scientist that orchestrates research workflows using tree-based hypothesis exploration.
Nexus-JPF/note-companion
When the user wants to set up, improve, or audit analytics tracking and measurement.
Nexus-JPF/note-companion
When the user wants to conduct, analyze, or synthesize customer research.
Nexus-JPF/note-companion
When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.
Nexus-JPF/note-companion
When the user wants to research, profile, or analyze competitors from their URLs.
Nexus-JPF/note-companion
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value.
Nexus-JPF/note-companion
When the user wants to create, generate, edit, or optimize images for marketing — blog heroes, social graphics, product mockups, profile banners, listing visuals, or brand assets.
Categories
When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task. Marketing Loops is an agent skill from Nexus-JPF/note-companion. When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task.
Marketing Loops fits situations like: wants to set up a recurring; self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly; on a trigger) rather than a one-off task; the user mentions marketing loop.
Run `npx skills add Nexus-JPF/note-companion --skill marketing-loops -a claude-code`. Or copy the skill folder (.agents/skills/marketing-loops in Nexus-JPF/note-companion) into .claude/skills/marketing-loops in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Nexus-JPF/note-companion --skill marketing-loops -a codex`. Or copy the skill folder (.agents/skills/marketing-loops in Nexus-JPF/note-companion) into .agents/skills/marketing-loops in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Nexus-JPF/note-companion --skill marketing-loops -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/marketing-loops, .gemini/skills/marketing-loops, .github/skills/marketing-loops and .opencode/skills/marketing-loops in your project.
SKILL.md names no scripts, command-line tools or credentials: Marketing Loops is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Marketing Loops is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.2k tokens (SKILL.md is roughly 9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 16k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Marketing Loops: Ab Testing (coreyhaines31/marketingskills, 54k stars), Ad Test Designer (aaron-he-zhu/aaron-marketing-skills, 2.9k stars), Ab Test Analyzer (irinabuht12-oss/marketing-skills, 4.1k stars) and Ab Test Store Listing (appeeky/aso-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Nexus-JPF (a GitHub organization) maintains it in Nexus-JPF/note-companion, which has 870 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 7, 2026.
Source: Nexus-JPF/note-companion on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.