Initialize a cogni-marketing project by discovering cogni-trends and cogni-portfolio sources, configuring brand voice, and selecting markets with GTM paths. Use this skill when the user asks to 'set up marketing', 'create a marketing project', 'initialize marketing', 'start marketing content', 'configure brand', 'marketing setup', or wants to begin creating marketing content for a portfolio — even if they don't say 'setup' explicitly.
From cogni-marketingnpx claudepluginhub cogni-work/insight-wave --plugin cogni-marketingThis skill is limited to using the following tools:
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
Initialize a cogni-marketing project by:
Scan the working directory for existing sources:
**/portfolio.json files. For each, read to confirm it has products and markets populated.**/tips-project.json files. For each, check that tips-value-model.json exists alongside it (value-modeler completed).**/marketing-project.json to avoid duplicates.output/communicate/customer-narrative/ exists. If it does, list the files found (overview, market-level, customer-level narratives). These are pre-written audience-tailored narratives that content generation skills can reference for richer voice and messaging consistency. Store discovered paths in marketing-project.json under sources.enriched_portfolio_narratives.Present discovered sources to user:
Portfolio projects found:
1. acme-cloud (4 products, 3 markets, 12 propositions)
└─ Customer narratives: 1 overview, 3 market, 5 persona (enrichment available)
2. beta-services (2 products, 1 market, 4 propositions)
TIPS projects found:
1. b2b-ict-ai-trends (5 themes, 18 solution templates)
2. manufacturing-digital (4 themes, 12 solution templates)
If customer narratives were found, note this briefly — they will be available as optional enrichment for content generation skills (voice consistency, messaging alignment).
Ask user to select one portfolio and one TIPS project. If only one of each exists, confirm automatically.
Ask user for brand details. Provide smart defaults from portfolio company data:
Brand name: [from portfolio.json company.name]
Brand voice: [suggest based on industry]
CTA style: soft-ask | direct | value-exchange
Visual direction: [optional, for creative briefs]
Industry-based voice defaults:
For tone modifiers, use the defaults from ${CLAUDE_PLUGIN_ROOT}/references/content-formats.md — user can override later.
Read all markets from the portfolio project (markets/*.json). Present with key metrics:
Available markets:
1. [primary] mid-market-saas-dach — TAM €2.4B, 3 propositions, 2 competitors
2. [expansion] enterprise-manufacturing-dach — TAM €5.1B, 4 propositions, 3 competitors
3. [aspirational] startup-fintech-eu — TAM €800M, 1 proposition, 0 competitors
Ask user to select markets and set priority (primary/secondary). Recommend starting with primary/expansion markets that have the most propositions.
For each selected market, read the TIPS value model (tips-value-model.json). Present strategic themes ranked by solution ranking value:
GTM paths for mid-market-saas-dach:
Theme | Ranking | Top ST readiness | Recommendation
AI-Driven Predictive Maint. | 4.2 | 0.82 | ★ Primary GTM path
Cloud-Native Transformation | 3.8 | 0.64 | ★ Secondary
Sustainability Reporting | 3.1 | 0.45 | Consider later
Legacy Modernization | 2.4 | 0.31 | Low priority
For each theme, show which portfolio propositions map to it (via solution template → portfolio anchor → proposition). Ask user to select 2-4 GTM paths per market.
For each selected GTM path, determine funnel focus (must use schema enum: awareness|consideration|decision|full-funnel):
Present default content settings from ${CLAUDE_PLUGIN_ROOT}/references/content-formats.md. Ask:
"These are the default content specifications. Would you like to adjust any word counts, formats, or cadence? Or proceed with defaults?"
Determine project slug: {brand-name}-marketing (kebab-case).
Create directory structure:
mkdir -p cogni-marketing/{slug}/content/{thought-leadership,demand-generation,lead-generation,sales-enablement,abm}
mkdir -p cogni-marketing/{slug}/{campaigns,calendar,output/exports,.logs}
Write marketing-project.json with all configured data following the schema in ${CLAUDE_PLUGIN_ROOT}/references/data-model.md.
Display project summary:
Marketing project initialized: {slug}
Brand: {name} ({voice})
Language: {language}
Markets: {count} ({list})
GTM paths: {count} across {market_count} markets
Source portfolio: {path}
Source TIPS: {path}
Next steps:
1. Run /content-strategy to build the content matrix
2. Or jump directly to /thought-leadership for your first content piece
Read language from portfolio project's portfolio.json → language field. Default to the same for marketing. If TIPS project has a different language, ask user which to use for marketing output. Marketing projects can be bilingual — content is generated in the project language, with the option to generate parallel versions in the other language.