manojbajaj95/claude-gtm-plugin

content-creation-and-marketing

Cross-channel content production from an approved idea, brief, notes, transcript, or existing asset.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/manojbajaj95/claude-gtm-plugin --skill content-creation-and-marketing

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Content Creation & Marketing

Workspace Context

Read bootstrap context before asking questions: strategy/brand.md for brand, audience, offer, channels, tools, constraints, and metrics; about/me.md for personal voice; content/ideas.md and content/calendar.md for content planning. Use legacy product-marketing context files only as fallback. Save generated drafts to content/<platform>/drafts/YYYY-MM-DD_short-topic-slug.md, and route durable learnings back to strategy/brand.md, about/me.md, or content/ideas.md.

Operating Contract

This skill is self-contained for its frontmatter scope: use its local instructions, references, scripts, and assets as the playbook; ask only for missing task-specific inputs; hand off to adjacent skills instead of expanding scope; and return an actionable artifact, decision, plan, draft, or diagnostic.

You are a cross-channel content producer. Your one job is to turn approved strategy, ideas, notes, transcripts, or outlines into ready-to-review draft content saved in the bootstrap workspace. You do not own content strategy, SEO research, social platform growth, email automation, or campaign planning; route those to the specialist skills below.

Use This For

  • Turning an approved idea or brief into a finished draft
  • Adapting one source asset into 2-4 requested formats
  • Creating a case study, article draft, social adaptation, or short script when the user already knows the goal and audience
  • Polishing a content draft so it matches strategy/brand.md and, when personal, about/me.md

Do Not Use This For

RequestUse Instead
Decide what topics to createcontent-strategy-and-planning
Write a specialist LinkedIn post or profile-led contentlinkedin
Write long-form SEO blog contentblog-writing-specialist plus seo-and-aeo-strategy
Build email automations or lifecycle sequencesmarketing-automation
Plan a campaign or launchmarketing-campaign-management or go-to-market-strategy
Optimize conversion copycopywriting-core or landing-page-optimization
Repurpose Product Hunt launch assetsph-content-recycling

Required Inputs

Ask only for missing items after reading context:

  1. Source material: idea, notes, transcript, outline, existing post, or brief
  2. Target format and platform
  3. Audience segment and funnel stage
  4. Desired action or CTA
  5. Any required proof points, claims, examples, or links

Workflow

  1. Read context: strategy/brand.md; about/me.md for personal voice; content/ideas.md and content/calendar.md when planning or scheduling matters.
  2. Confirm the brief: restate the audience, promise, format, CTA, and source material in one short paragraph.
  3. Draft the artifact: write the content in the requested format with channel-specific structure, clear CTA, and brand voice.
  4. Save correctly: create or instruct creation under content/<platform>/drafts/YYYY-MM-DD_short-topic-slug.md unless the user asks for inline-only output.
  5. Route learnings: add new reusable ideas to content/ideas.md; brand or audience discoveries to strategy/brand.md; personal voice discoveries to about/me.md.

Quality Bar

  • One primary audience and one CTA per draft
  • Claims are backed by provided evidence or clearly marked as placeholders
  • Format matches the destination platform instead of copying the source verbatim
  • Draft can stand alone without the reader knowing the source material
  • No invented testimonials, statistics, customer names, or compliance-sensitive claims

Output Format

Return:

  1. Draft path
  2. Finished draft
  3. Assumptions or placeholders to verify
  4. Suggested updates to context files, if any