Agent skill

Growth Engineering

by indranilbanerjee in indranilbanerjee/digital-marketing-pro

Engineer growth systems: PLG motions, referrals, viral and retention loops.

MITAuto-check passedMarketing & SEO

Install Growth Engineering

skills CLI
$ npx skills add indranilbanerjee/digital-marketing-pro --skill growth-engineering -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install indranilbanerjee/digital-marketing-pro growth-engineering --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/growth-engineering .claude/skills/growth-engineering && rm -rf skills-src

Use ~/.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/

Facts

Skill name
growth-engineering
GitHub stars
862
Used in
1 other repo
Token cost
~4.1k tokens
SKILL.md length
1,981 words
Files
8
Skills in repo
162
Repo updated
First seen
Licence
MIT

At a glance

Engineer growth systems: PLG motions, referrals, viral and retention loops.

  • Works in 9 steps: Check session context — The active brand… → If you need the full profile, read:… → Apply brand voice — Formality, energy,… → …
  • Tasks that involve Referral and retention marketing
  • SKILL.md covers When to Use This Skill, Brand Context (Auto-Applied), Required Context and Capabilities, plus 5 more sections
  • Calls python

What it does

Growth Engineering is an agent skill from indranilbanerjee/digital-marketing-pro. Engineer growth systems: PLG motions, referrals, viral and retention loops. "design a referral program"

Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files (for example `affiliate-marketing.md`, `experimentation-frameworks.md` and `launch-strategy.md`).

It sits in Marketing & SEO, covering Referral and retention marketing. The repository describes itself as: An open-source AI marketing operating system for strategy, SEO, AEO/GEO, paid media, content, CRM, and analytics - grounded in brand context, human approval, and verifiable… The licence is MIT.

When your agent uses it

  • Tasks that involve Referral and retention marketing

Example prompts

  • “design a referral program”
  • “/growth-engineering”

Requirements

  • Python 3

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. Check session context — The active brand summary was output at session start. Use the brand name, industry, voice settings, channels…
  2. If you need the full profile, read: ~/.claude-marketing/brands/{slug}/profile.json
  3. Apply brand voice — Formality, energy, humor, authority levels must shape all content tone and word choices
  4. Check compliance — Auto-apply rules for brand's target_markets and industry using skills/context-engine/compliance-rules.md
  5. Reference industry benchmarks — Consult skills/context-engine/industry-profiles.md for the brand's industry
  6. Use platform specs — Reference skills/context-engine/platform-specs.md for character limits and format requirements
  7. Check campaign history — Run python "${CLAUDE_PLUGIN_ROOT}/scripts/campaign-tracker.py" --brand {slug} --action list-campaigns before…
  8. If no brand exists, say: "No brand profile found. Use /digital-marketing-pro:brand-setup to create one, or I can proceed with general best…
  9. Check brand guidelines — If ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json exists, load and enforce: restrictions.md for…

What it can do on your machine

Read from SKILL.md and the folder at commit 9e949f3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Growth Engineering loads about 4.1k tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 1,981 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~31
When it runs · the whole SKILL.md, loaded when a task matches
~4.1k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from indranilbanerjee/digital-marketing-pro at commit 9e949f3, republished under its MIT licence (© indranilbanerjee). 1,981 words, ~4,127 tokens.

Download SKILL.mdSave it as .claude/skills/growth-engineering/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
growth-engineering
description
Engineer growth systems: PLG motions, referrals, viral and retention loops. "design a referral program"

Growth Engineering

Script location. If your host does not set ${CLAUDE_PLUGIN_ROOT}, the scripts are in this plugin's scripts/ folder, next to skills/.

When to Use This Skill

Activate this skill when the user's request involves any of the following:

  • Designing or improving a product-led growth (PLG) motion
  • Building or optimizing referral programs (customer referral, partner referral, ambassador programs)
  • Creating viral loops or increasing organic sharing mechanics
  • Planning a product or company launch (Product Hunt, beta launches, waitlists)
  • Improving user retention, reducing churn, or designing re-engagement campaigns
  • Running growth experiments and building an experimentation culture
  • Setting up or optimizing affiliate marketing programs
  • Designing activation flows and reducing time-to-value for new users
  • Building growth models or forecasting viral growth coefficients
  • Solving cold-start problems for marketplaces or platforms
  • Identifying and scoring product-qualified leads (PQLs)
  • Any question about growth levers, growth loops, or sustainable acquisition strategies

Brand Context (Auto-Applied)

Before producing any marketing output from this module:

  1. Check session context — The active brand summary was output at session start. Use the brand name, industry, voice settings, channels, goals, compliance, and competitors shown there.
  2. If you need the full profile, read: ~/.claude-marketing/brands/{slug}/profile.json
  3. Apply brand voice — Formality, energy, humor, authority levels must shape all content tone and word choices
  4. Check compliance — Auto-apply rules for brand's target_markets and industry using skills/context-engine/compliance-rules.md
  5. Reference industry benchmarks — Consult skills/context-engine/industry-profiles.md for the brand's industry
  6. Use platform specs — Reference skills/context-engine/platform-specs.md for character limits and format requirements
  7. Check campaign history — Run python "${CLAUDE_PLUGIN_ROOT}/scripts/campaign-tracker.py" --brand {slug} --action list-campaigns before planning new work
  8. If no brand exists, say: "No brand profile found. Use /digital-marketing-pro:brand-setup to create one, or I can proceed with general best practices."
  9. Check brand guidelines — If ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json exists, load and enforce: restrictions.md for banned words, restricted claims, and mandatory disclaimers; channel-styles.md for channel-specific tone overrides (may differ from base voice); messaging.md for approved key messages, taglines, and positioning language; voice-and-tone.md for detailed voice rules beyond the 4 numeric scores. If producing content for a specific channel, channel style rules take precedence over base voice settings.

Do not ask the user for information that already exists in their brand profile.

Required Context

Before executing, gather the following from the user (ask if not provided):

  • Product type: SaaS, marketplace, ecommerce, mobile app, content platform, service business
  • Business model: Subscription, transactional, freemium, free-trial, advertising-supported
  • Current stage: Pre-launch, early traction (under 1,000 users), growth stage, scale stage
  • Key metrics: Current MRR/ARR, user count, activation rate, retention rate, churn rate, NPS
  • Existing growth channels: Which acquisition channels are active and their relative performance
  • Viral potential: Whether the product has inherent sharing mechanics or requires artificial virality
  • Team and resources: Engineering capacity for growth features, marketing budget, partnership resources
  • Target user: Who the ideal user is and what their primary motivation for using the product is
  • Competitive landscape: Key competitors and their growth strategies

Capabilities

Product-Led Growth (PLG) Strategy
  • Free-to-paid conversion: Freemium model design, free trial optimization, feature gating strategy, usage-based pricing triggers
  • Activation metrics: Define the "aha moment," map the steps to reach it, measure and optimize activation rate
  • Time-to-value optimization: Reduce friction between signup and first value experience through onboarding design, templates, sample data, and guided tours
  • PQL scoring: Define product-qualified lead criteria based on usage patterns, feature adoption, team size, and engagement frequency
  • Self-serve expansion: In-product upgrade prompts, usage limit notifications, team invite flows, seat expansion triggers
  • Reverse trial: Give full access first, then downgrade to free -- when this works better than traditional freemium
Referral Systems
  • Give-and-get programs: Both referrer and referee receive incentives (e.g., Dropbox's extra storage model)
  • Tiered referral rewards: Escalating incentives based on number of successful referrals
  • Milestone referrals: Rewards triggered at referral count milestones (1, 5, 10, 25) to maintain momentum
  • NPS-to-referral pipeline: Target promoters (NPS 9-10) with referral requests at the moment of highest satisfaction
  • Double-sided incentive design: Balancing referrer reward (motivation to share) with referee reward (motivation to convert)
  • Referral channel optimization: Email, unique link, social share, in-app invite, SMS -- which channels perform for which product types
  • Fraud prevention: Detecting self-referral, fake accounts, and incentive gaming without creating friction for legitimate referrers
Viral Loop Design
  • Inherent virality: The product naturally requires others to use it (Slack, Zoom, Google Docs)
  • Artificial virality: Manufactured sharing through incentives, social features, or content creation (shareable reports, badges, results)
  • Content virality: User-generated content that surfaces on external platforms and drives new users back
  • Social proof virality: Visible usage signals (badges, signatures, "powered by" links, public profiles)
  • Viral coefficient calculation: K-factor = invites per user x conversion rate of invites. K > 1 means exponential growth; K between 0.5-1.0 augments paid acquisition significantly
  • Viral cycle time: Reducing the time between a user joining and their invitees joining. Shorter cycles compound faster even with lower K-factors
Launch Playbooks
  • Tier 1 launch (major product): Full press campaign, influencer seeding, Product Hunt, beta community, launch event, paid amplification
  • Tier 2 launch (feature/update): Existing user announcement, targeted outreach, community posts, changelog, email campaign
  • Tier 3 launch (minor update): In-app notification, changelog update, social media post
  • Pre-launch waitlist: Viral waitlist mechanics (share to move up), early access incentives, drip content to maintain interest
  • Product Hunt launch: Preparation timeline (2-4 weeks), hunter selection, launch day playbook, post-launch engagement
  • Beta program design: Closed beta recruitment, feedback loops, beta-to-launch transition, early adopter community building
Retention Loops
  • Engagement design: Habit loops (trigger, action, variable reward, investment), notification strategy, content cadence
  • Re-engagement campaigns: Email sequences, push notifications, in-app messages, retargeting ads triggered by inactivity signals
  • Churn prediction: Behavioral signals that indicate churn risk (login frequency drop, feature usage decline, support ticket patterns)
  • Winback sequences: Timed outreach to churned users with personalized value reminders, product updates, and incentive offers
  • Cohort analysis: Track retention by signup cohort, acquisition channel, activation status, and feature adoption to identify what drives long-term retention
  • Expansion revenue: Upsell and cross-sell triggers based on usage patterns, team growth, and feature engagement
Affiliate Marketing
  • Program design: Commission structure (percentage, flat fee, tiered, recurring), cookie duration, attribution rules
  • Network selection: When to use affiliate networks (ShareASale, CJ, Impact) vs building a custom program
  • Affiliate recruitment: Finding high-quality affiliates through competitor analysis, content partnerships, and niche community outreach
  • Commission optimization: Balancing commission rates to attract affiliates while maintaining profitability; performance tiers to reward top performers
  • Fraud detection: Click fraud, cookie stuffing, brand bidding violations, trademark misuse, coupon abuse
  • Content affiliate strategy: Working with bloggers, review sites, comparison sites, and niche publishers
  • Affiliate-influencer hybrids: Creator partnerships with performance-based compensation models

Process

PLG Implementation (Most Common Use Case)
  1. Map the user journey -- Document every step from first awareness to paid conversion. Identify where users currently drop off and where they experience value.
  2. Define the activation metric -- Determine the specific action or combination of actions that correlates with long-term retention. This is the "aha moment" the entire PLG motion revolves around.
  3. Design the free offering -- Structure the free tier or trial to give users enough value to experience the activation moment while creating natural upgrade triggers. Reference common models: feature-limited freemium, usage-limited freemium, time-limited trial, reverse trial.
  4. Optimize time-to-value -- Redesign onboarding to get users to the activation metric as fast as possible. Remove unnecessary steps, add templates/sample data, implement guided tours, and offer quick-start paths.
  5. Build PQL scoring -- Define the behavioral signals that indicate a free user is ready for a sales touch or upgrade prompt. Combine usage frequency, feature breadth, team size, and engagement depth into a composite score.
  6. Implement expansion loops -- Design in-product mechanisms for organic growth: team invites, shared workspaces, public outputs, integrations that touch other teams, and usage-based upgrade paths.
  7. Measure and iterate -- Track activation rate, free-to-paid conversion rate, time-to-activation, expansion revenue, and viral coefficient. Run experiments on each stage of the funnel.
Show full SKILL.md (699 more words)Show less
Referral Program Build
  1. Assess viral potential -- Determine whether the product has inherent sharing mechanics or requires incentive-driven referrals. Analyze NPS data to identify promoter concentration.
  2. Design incentive structure -- Choose the referral model (give-and-get, tiered, milestone) based on product type, customer LTV, and competitive benchmarks. Set incentive values at 10-25% of customer acquisition cost.
  3. Build referral mechanics -- Create unique referral links, sharing interfaces, tracking infrastructure, and reward fulfillment flows. Make sharing frictionless (one-click, pre-written messages).
  4. Integrate referral touchpoints -- Embed referral prompts at high-satisfaction moments: post-purchase, after achieving a milestone, after a positive support interaction, at NPS survey completion.
  5. Launch and promote -- Announce the program to existing users, feature it in onboarding, add it to account dashboards, and include it in email communications.
  6. Monitor and optimize -- Track share rate, invite conversion rate, referral revenue, and fraud signals. A/B test incentive types, sharing copy, and prompt placement.

Reference Files

  • product-led-growth.md -- PLG frameworks, freemium vs trial decision trees, activation metric identification, PQL scoring models
  • referral-systems.md -- Referral program templates, incentive design principles, fraud prevention tactics, and case studies
  • viral-loops.md -- Viral coefficient calculations, loop design patterns, virality assessment frameworks
  • launch-strategy.md -- Tier 1/2/3 launch playbooks, Product Hunt guide, waitlist mechanics, beta program design
  • retention-loops.md -- Engagement frameworks, churn prediction models, winback sequences, cohort analysis methods
  • affiliate-marketing.md -- Program setup guides, network comparisons, commission optimization, fraud detection systems
  • experimentation-frameworks.md -- Experiment prioritization (ICE/RICE), hypothesis formats, statistical foundations, AARRR experiment categories, and experimentation velocity benchmarks

Output Formats

  • PLG strategy document: User journey map, activation metric definition, free tier design, PQL criteria, expansion loop mechanics, and success metrics
  • Referral program spec: Incentive structure, mechanics description, integration points, launch plan, and monitoring dashboard requirements
  • Launch playbook: Pre-launch timeline, launch day checklist, channel-by-channel activation plan, post-launch follow-up sequence
  • Retention analysis: Cohort retention curves, churn risk indicators, re-engagement campaign designs, and winback sequence templates
  • Growth model: Spreadsheet-ready model with viral coefficient, cycle time, channel-level CAC, retention curves, and projected growth trajectories
  • Affiliate program blueprint: Commission structure, network/platform recommendation, recruitment strategy, compliance guidelines, and fraud monitoring plan

Edge Cases

Non-Viral Products

Some products have no inherent sharing mechanic (e.g., personal finance tools, solo productivity apps). For these, create artificial virality through shareable outputs (reports, achievements, results), social proof features (public profiles, leaderboards), content creation tools that naturally surface the brand, or incentive-driven referrals. Not every product needs a viral coefficient above 1 -- even K=0.3 meaningfully reduces CAC.

Marketplace Cold-Start Problem

Two-sided marketplaces face the chicken-and-egg problem: no supply without demand, no demand without supply. Solve by starting with one side (usually supply) through manual recruitment, seeding content, or offering the supply side a standalone value proposition. Concentrate on a narrow geography or vertical first. Reference strategies: Uber started with black cars, Airbnb started with events, and Yelp started with reviews before transactions.

B2B vs B2C Retention Dynamics

B2B retention depends on product becoming embedded in workflows, multi-user adoption within an organization, and integration with other tools. B2C retention depends on habit formation, content freshness, and emotional engagement. Do not apply B2C engagement tactics (daily push notifications, gamification) to B2B products. B2B retention is measured monthly or quarterly, not daily.

Referral Fraud Prevention

Common referral fraud patterns include self-referral with multiple accounts, referral rings between friends who churn after receiving rewards, and bot-generated fake referrals. Mitigate by requiring the referred user to complete a meaningful action (purchase, usage threshold) before rewards are distributed, implementing device fingerprinting, setting reasonable reward caps, and monitoring for anomalous patterns.

International Launch Sequencing

When launching internationally, do not launch everywhere simultaneously. Sequence by market attractiveness (TAM, competitive density, regulatory complexity), language/localization readiness, and existing demand signals. Start with one new market, prove the playbook, then expand. Payment methods, compliance requirements, and cultural norms vary significantly and can break launch plans built for the home market.

  • Paid Advertising -- Paid acquisition that PLG and viral loops can amplify or replace over time
  • CRO -- Activation and onboarding optimization overlaps heavily with CRO principles
  • Content Engine -- Content marketing that feeds growth loops and launch amplification
  • Analytics & Insights -- Cohort analysis, experiment measurement, and growth modeling
  • Influencer & Creator Marketing -- Creator partnerships for launch amplification and affiliate-influencer hybrids
  • Funnel Architect -- Growth engineering strategies plug into the broader acquisition and retention funnel

© indranilbanerjee, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files in skills/growth-engineering of indranilbanerjee/digital-marketing-pro.

  • SKILL.md
  • affiliate-marketing.md
  • experimentation-frameworks.md
  • launch-strategy.md
  • product-led-growth.md
  • referral-systems.md
  • retention-loops.md
  • viral-loops.md

Open the folder on GitHubat commit 9e949f3

Used in 1 other repository

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 indranilbanerjee/digital-marketing-pro, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Growth Engineering 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.

Growth Engineering compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Growth Engineering this skillindranilbanerjee/digital-marketing-pro8621 repos~4.1kAutomated safety check: PassMIT
Referralscoreyhaines31/marketingskills54k2 repos~2.6kAutomated safety check: PassMIT
Referral Programfreekmurze/dotfiles1k17 repos~1.8kAutomated safety check: PassNone
Churn Preventionrongxinzy/RongxinAI1543 repos~2.6kAutomated safety check: PassMIT
100m Leadsgetagentseal/founder-playbook729—~2.3kAutomated safety check: PassMIT
Churn Preventionfreekmurze/dotfiles1k13 repos~4.4kAutomated safety check: PassNone

Similar skills

  • Referrals

    coreyhaines31/marketingskills

    When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy.

    54k GitHub starsUsed in 2 repos~2.6k tokens
    Marketing & SEOAuto-check passed
  • Referral Program

    freekmurze/dotfiles

    When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy.

    1k GitHub starsUsed in 17 repos~1.8k tokens
    Marketing & SEOAuto-check passed
  • Churn Prevention

    rongxinzy/RongxinAI

    Reduce voluntary and involuntary churn through cancel flow design, save offers, exit surveys, and dunning sequences.

    154 GitHub starsUsed in 3 repos~2.6k tokens
    Marketing & SEOAuto-check passed
  • 100m Leads

    getagentseal/founder-playbook

    Builds lead generation systems using Alex Hormozi's Core Four framework (warm outreach, content, cold outreach, paid ads), lead magnets, and Rule of 100.

    729 GitHub stars~2.3k tokensUpdated 4 days ago
    Marketing & SEOAuto-check passed
  • Churn Prevention

    freekmurze/dotfiles

    When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies.

    1k GitHub starsUsed in 13 repos~4.4k tokens
    Marketing & SEOAuto-check passed
  • Sms

    coreyhaines31/marketingskills

    When the user wants to plan, build, or optimize SMS, MMS, or WhatsApp marketing — including welcome flows, abandoned cart texts, post-purchase, win-back, promotional sends, or transactional/auth SMS.

    54k GitHub starsUsed in 1 repo~4.6k tokens
    Marketing & SEOAuto-check passed

More from indranilbanerjee/digital-marketing-pro

All 162 skills in this repo
  • Import Template

    indranilbanerjee/digital-marketing-pro

    Import a deliverable template as a reusable placeholder template per brand.

    862 GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed
  • Ab Test Plan

    indranilbanerjee/digital-marketing-pro

    Plan an A/B test by script: sample size per variant, days to run, stopping rules.

    862 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Aeo Audit

    indranilbanerjee/digital-marketing-pro

    Run a one-time AEO audit of six AI answer engines, scored per surface.

    862 GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Agent Readiness Audit

    indranilbanerjee/digital-marketing-pro

    Audit agent readiness by script: AI-crawler rules, product schema, no-JS HTML, feeds.

    862 GitHub starsUsed in 1 repo~3.7k tokens
    Auto-check passed
  • Backlink Gap

    indranilbanerjee/digital-marketing-pro

    Find backlink gap domains linking to competitors, not you, scored by script.

    862 GitHub starsUsed in 1 repo~2.6k tokens
    Auto-check passed
  • C2pa Metadata

    indranilbanerjee/digital-marketing-pro

    Embed C2PA provenance in AI-generated images, video or PDF by script.

    862 GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

Categories

Questions about Growth Engineering

What does Growth Engineering do?

Engineer growth systems: PLG motions, referrals, viral and retention loops. Growth Engineering is an agent skill from indranilbanerjee/digital-marketing-pro. Engineer growth systems: PLG motions, referrals, viral and retention loops.

When should I use Growth Engineering?

Growth Engineering fits situations like: tasks that involve Referral and retention marketing.

How do I install Growth Engineering in Claude Code?

Run `npx skills add indranilbanerjee/digital-marketing-pro --skill growth-engineering -a claude-code`. Or copy the skill folder (skills/growth-engineering in indranilbanerjee/digital-marketing-pro) into .claude/skills/growth-engineering in your project. Claude Code loads it when a task matches its description.

How do I install Growth Engineering in Codex?

Run `npx skills add indranilbanerjee/digital-marketing-pro --skill growth-engineering -a codex`. Or copy the skill folder (skills/growth-engineering in indranilbanerjee/digital-marketing-pro) into .agents/skills/growth-engineering in your project. Codex loads it when a task matches its description.

Can I use Growth Engineering in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add indranilbanerjee/digital-marketing-pro --skill growth-engineering -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/growth-engineering, .gemini/skills/growth-engineering, .github/skills/growth-engineering and .opencode/skills/growth-engineering in your project.

What does Growth Engineering need to run?

Going by SKILL.md and its folder, Growth Engineering needs the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Growth Engineering access the network?

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.

Is Growth Engineering safe to install?

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.

What licence does Growth Engineering use?

Growth Engineering is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Growth Engineering use?

About 4.1k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Growth Engineering?

Skills that share tags, products or a category with Growth Engineering: Referrals (coreyhaines31/marketingskills, 54k stars), Referral Program (freekmurze/dotfiles, 1k stars), Churn Prevention (rongxinzy/RongxinAI, 154 stars) and 100m Leads (getagentseal/founder-playbook, 729 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Growth Engineering?

indranilbanerjee (a GitHub user) maintains it in indranilbanerjee/digital-marketing-pro, which has 862 GitHub stars. The repository holds 162 skills in this directory. The repository was last updated on October 9, 2026.

Source: indranilbanerjee/digital-marketing-pro on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.