dstack-marketing

Plugin dstack-marketing from marketplace dstack in gosuda/dalcom-skills. Commands read from the repo's manifest — 3 days ago.

Skills (28)

• buzzword-hijack

  Use when a user wants to choose and execute a bounded positioning move that rides a jargon wave. Not for describing the jargon weather of a domain.

• competitive-content

  Use when preparing an honest alternative or comparison page brief or draft from source-backed claims. Not for false claims, implied endorsement, or uncited testimonials.

• competitive-intelligence

  Use when mapping the competitive landscape and battlecards for a developer product from authoritative sources. Not for per-feature changelog research or unsourced market predictions.

• content-evidence-brief

  Use when designing a long-form marketing or developer content piece from a source pack before drafting. Not for publishing the article or cross-posting it.

• developer-advocacy

  Use when preparing a conference talk, workshop, demo, podcast appearance, or building-in-public brief. Not for unsolicited pitches, submissions, or fabricated reach figures.

• developer-audience-context

  Use when grounding developer marketing in a confirmed audience profile of persona, pains, alternatives, and trust signals. Not for inventing quotes, benchmarks, or audience facts.

• developer-champion-programs

  Use when designing a consent-aware advocate or champion program with qualification, benefits, and opt-in records. Not for unsolicited contact, quotas, or forced referrals.

• developer-community-posting

  Use when preparing a Hacker News or Reddit post package with eligibility, disclosure, and do-not-post conditions. Not for posting, replying, voting, or account activity.

• developer-community

  Use when designing developer community operations including platform choice, moderation, and health metrics. Not for creating servers, inviting members, or automated outreach.

• developer-content

  Use when preparing an evidence-backed developer content package with runnable examples and accuracy checks. Not for publishing, fabricating results, or unverified performance claims.

• developer-discovery-surfaces

  Use when auditing GitHub presence or preparing curated directory submission packets for a developer tool. Not for star manipulation, automated PRs, or directory spam.

• developer-docs-led-growth

  Use when auditing docs or planning quickstart and API-reference improvements that drive acquisition and activation. Not for deploying docs or changing product code.

• developer-lifecycle-messaging

  Use when drafting consent-segmented newsletter, onboarding, activation, or re-engagement messages from real product behavior. Not for sending, list imports, or unsolicited win-back.

• developer-listening

  Use when collecting dated per-conversation evidence from public developer discussions to triage opportunities. Not for continuous monitoring, replies, or unsolicited engagement.

• developer-publishing

  Use when adapting a finished technical draft for Dev.to or Hashnode with correct canonical and metadata handling. Not for account creation, publication, or scheduling.

• developer-release-communication

  Use when writing factual release notes or upgrade notices from a release diff or changelog. Not for promotional copy, commits, releases, or publishing.

• developer-search

  Use when mapping technical search opportunities by exact query, intent, and source evidence. Not for inventing search volume, rankings, or time-to-result promises.

• developer-social-drafts

  Use when drafting evergreen technical X and LinkedIn posts from the same evidence with distinct shapes. Not for scheduling, automation, DMs, or follower manipulation.

• developer-utility-growth

  Use when designing a free tool or ungated resource brief for developer acquisition. Not for building, deploying, gating accounts, or collecting data.

• developer-video

  Use when preparing a developer video script, storyboard, demo runbook, and accessibility checklist. Not for recording, uploading, or channel management.

• marketing-assumption-grill

  Use when pressure-testing one marketing decision, idea, or plan before committing. Not for executing the decision or asking the user for facts the environment already holds.

• marketing-behavior-audit

  Use when diagnosing observed buyer or market behavior with evidence before changing copy, offer, or interface. Not for running experiments or claiming uplift.

• marketing-decision-map

  Use when a marketing initiative is too broad for a brief and needs its decisions charted before action. Not for executing the selected strategy or tracking tasks.

• offer-page-brief

  Use when designing an evidence-led offer or comparison page from confirmed facts before writing final copy. Not for implementing or publishing the page.

• open-source-adoption

  Use when planning open-source adoption through README quality, contributor funnel, and sustainable maintenance. Not for fake stars, coordinated votes, or fabricated metrics.

• release-promotion

  Use when asked to draft launch or promotion copy for a shipped feature across channels via /release-promotion. Not for posting, publishing, scheduling, committing, or final landing page copy.

• social-sentiment

  Use when the user asks for a weekly sentiment report, weekly social summary, or how mentions looked this week. Not for continuous monitoring or alerting.

• viral-opportunity-scout

  Use when asked to find distribution opportunities for a template, tool, or artifact. Not for content creation, campaign management, or paid placement.

Similar plugins