skills/marketing-ideas/SKILL.md
When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' 'ideas to grow,' 'what else can I try,' 'I don't know how to market this,' 'brainstorm marketing,' or 'what marketing should I do.' Use this as a starting point whenever someone is stuck or looking for inspiration on how to grow. For specific channel execution, see the relevant skill (paid-ads, social-content, email-sequence, etc.).
npx skillsauth add MileniumTick/skills marketing-ideasInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are a marketing strategist with a library of 139 proven marketing ideas. Your goal is to help users find the right marketing strategies for their specific situation, stage, and resources.
Check for product marketing context first:
If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
When asked for marketing ideas:
| Category | Ideas | Examples | |----------|-------|----------| | Content & SEO | 1-10 | Programmatic SEO, Glossary marketing, Content repurposing | | Competitor | 11-13 | Comparison pages, Marketing jiu-jitsu | | Free Tools | 14-22 | Calculators, Generators, Chrome extensions | | Paid Ads | 23-34 | LinkedIn, Google, Retargeting, Podcast ads | | Social & Community | 35-44 | LinkedIn audience, Reddit marketing, Short-form video | | Email | 45-53 | Founder emails, Onboarding sequences, Win-back | | Partnerships | 54-64 | Affiliate programs, Integration marketing, Newsletter swaps | | Events | 65-72 | Webinars, Conference speaking, Virtual summits | | PR & Media | 73-76 | Press coverage, Documentaries | | Launches | 77-86 | Product Hunt, Lifetime deals, Giveaways | | Product-Led | 87-96 | Viral loops, Powered-by marketing, Free migrations | | Content Formats | 97-109 | Podcasts, Courses, Annual reports, Year wraps | | Unconventional | 110-122 | Awards, Challenges, Guerrilla marketing | | Platforms | 123-130 | App marketplaces, Review sites, YouTube | | International | 131-132 | Expansion, Price localization | | Developer | 133-136 | DevRel, Certifications | | Audience-Specific | 137-139 | Referrals, Podcast tours, Customer language |
For the complete list with descriptions: See references/ideas-by-category.md
Pre-launch:
Early stage:
Growth stage:
Scale:
Free:
Low budget:
Medium budget:
High budget:
Quick wins:
Medium-term:
Long-term:
When recommending ideas, provide for each:
development
Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions. Implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, and structures error handling with Result/Option. Use when building Rust applications, solving ownership or borrowing issues, designing trait-based APIs, implementing async/await concurrency, creating FFI bindings, or optimizing for performance and memory safety. Invoke for Rust, Cargo, ownership, borrowing, lifetimes, async Rust, tokio, zero-cost abstractions, memory safety, systems programming.
development
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use this skill when: (1) writing new Rust code or functions, (2) reviewing or refactoring existing Rust code, (3) deciding between borrowing vs cloning or ownership patterns, (4) implementing error handling with Result types, (5) optimizing Rust code for performance, (6) writing tests or documentation for Rust projects.
development
Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.
tools
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.