continuous-improvement-loop

continuous-improvement-loop is a skill for Claude Code from indranilbanerjee/digital-marketing-pro. It costs 27 tokens per session (3,060 once invoked), scanned A, original, MIT.

A recurring review process that combines customer, competitor, quarterly business, and operating signals into recommendations for improving a product, offer, or service.

In plain words
What is it for?
It produces quarterly leadership briefs and shorter briefs when important signals arrive, feeding findings back into ongoing product and marketing decisions.
Why use it?
It prevents marketing decisions from staying tied to assumptions that were made months earlier as customers, markets, and competitors change.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is (If any of the signals warrant a source-document version bump per the [update-back-rule.md](../context-engine/update-back-rule.md), list them here. The actual u.

Part of the digital-marketing-pro plugin — 164 skills, 5 commands, 24 agents shipped together

Good fit It produces quarterly leadership briefs and shorter briefs when important signals arrive, feeding findings back into ongoing product and marketing decisions.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro
agentmods
npx agentmods add skills/indranilbanerjee/digital-marketing-pro/continuous-improvement-loop

Made for: Claude Code.

Or install digital-marketing-pro, the plugin that ships this one along with the rest of its 164 skills, 5 commands, 24 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for continuous-improvement-loop

README.md
[![agentmods](https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/continuous-improvement-loop/github.svg)](https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/continuous-improvement-loop)
Your own site
<a href="https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/continuous-improvement-loop"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/continuous-improvement-loop/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for continuous-improvement-loop

Your own site · 80×15
<a href="https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/continuous-improvement-loop"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/continuous-improvement-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,060 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.03060
Opus 5.5 $0.00011 $0.01224
Sonnet 5.5 $0.00005 $0.00612
Haiku 4.5 $0.00003 $0.00306

Measured 17d ago against content hash b56650eb7546, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

continuous-improvement-loop scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 17d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills/continuous-improvement-loop/SKILL.md · 282 lines

How it starts

The opening of the file, as written. The whole thing — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/digital-marketing-pro:continuous-improvement-loop — Part 12 Continuous Loop

Part 12 is the continuous improvement loop that runs alongside live operations from go-live onwards. It aggregates market signals and operating signals into recommendations that feed back into the brand's product, offering, and service decisions.

Context efficiency

Heavy skill. Grep before Read any referenced file, then Read only matched ranges with offset + limit. List the brand's workspace at ~/.claude-marketing/brands/{slug}/ (or $CLAUDE_PLUGIN_DATA/digital-marketing-pro/brands/{slug}/ when that env var is set) before opening files. On re-invocation mid-session, skip files already in context.

This is not a one-time activity. It runs perpetually once Part 11 is complete, with formal output at each Quarterly Business Review (QBR) and ad-hoc output when significant signals warrant.

Why this exists

Without an explicit feedback loop, marketing operates on assumptions made months ago. Markets shift, customers evolve, competitors move, products are refined — but if these shifts do not flow back into the strategy, the engagement silently grows stale.

Part 12 closes the loop:

  • Market signals → strategy refresh
  • Operating signals → tactical optimisation
  • Product / offering signals → recommendations to product / business teams

The 4 Signal Sources

Source 1: Quarterly Business Reviews

Every quarterly review (per reporting-cadence.md) generates structured signals:

  • KPIs vs targets (which targets were missed; which were beaten; pattern across quarters?)
  • Channel-mix performance (any channel consistently outperforming or underperforming the v2 plan?)
  • Audience segment performance (any segment showing different behaviour than the personas predicted?)
  • Competitive shifts (any competitor moves that materially change the landscape?)
  • Strategy alignment audit (is what we are executing still what the v2 strategy says we should be executing?)

Read the full file on GitHub · 282 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 17d ago Changed · -121 tokens per session b56650eb7546
  2. 22d ago Changed · -7 lines 38dc578baf16
  3. 1mo ago First seen · 289 lines · 148 tokens per session scan A 18c0637c1227

Subscribe to this mod's changes

continuous-improvement-loop is a skill published in the GitHub repository indranilbanerjee/digital-marketing-pro (911 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 3,060 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.