Token导航 LogoToken导航

Agent Skill · 开发

campaign-brief-generator(活动简介生成器)

campaign-brief-generator 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

campaign-brief-generator 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 19,470。

总安装 269周安装 11GitHub Stars 607下载 87核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:campaign-brief-generator(活动简介生成器)
来源仓库:https://github.com/athina-ai/goose-skills
仓库路径:skills/campaign-brief-generator
安装命令:
npx skills add https://github.com/athina-ai/goose-skills --skill campaign-brief-generator
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/athina-ai/goose-skills --skill campaign-brief-generator

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

根据产品背景与目标客户生成可执行的市场推广方案简报。整合渠道选择、内容策略与时间规划,适合初创团队快速启动活动。输出具体行动项而非模板,强调落地性与团队协作可行性。

安装命令:npx skills add https://github.com/athina-ai/goose-skills --skill campaign-brief-generator 需明确产品特性、目标人群及资源限制条件以提高建议相关性。

来源仓库内路径:skills/campaign-brief-generator

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/athina-ai/goose-skills --skill campaign-brief-…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

campaign-brief-generator 怎么安装?

在终端执行 npx skills add https://github.com/athina-ai/goose-skills --skill campaign-brief-generator。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

campaign-brief-generator 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

campaign-brief-generator 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

campaign-brief-generator 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

campaign-brief-generator 用的人多吗?

公开数据是累计安装 269 次,近一周安装 11 次,下载 87 次,GitHub 607 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

campaign-brief-generator 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
campaign-brief-generator

活动简介生成器 · 本页

269607需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Campaign Brief Generator

Pure reasoning skill. Takes a campaign goal, ICP, and product context — and produces a complete, actionable campaign brief a small team can actually execute.

Built for: Founders doing their own marketing. First marketing hires. GTM teams without a dedicated strategist. The output should be opinionated and specific, not a generic template.

When to Use

  • "Help me plan a campaign for [launch / feature / segment]"
  • "We're targeting [ICP], what channels and content should we run?"
  • "I need a 30-day campaign plan"
  • "We're launching [product/feature] — help me plan the GTM"
  • "Write me a campaign brief for [goal]"

Phase 0: Intake

Ask all questions in one go, grouped cleanly. This is a fast skill — don't make it feel like a form.

Campaign Context

  1. Goal — What does success look like in 30/60/90 days? (e.g., "50 signups from developer audience", "10 demos booked with Series B startups", "3 media mentions")
  2. Trigger — What's prompting this campaign? (product launch, new feature, new segment, funding, competitive threat, slow quarter)
  3. Timeline — How long should the campaign run? When should it start?

Audience

  1. ICP — Who exactly are you targeting? (Title, company type, stage, geography)
  2. Where do they hang out? — Channels they actively use (LinkedIn, Slack communities, specific newsletters, Twitter/X, etc.)
  3. What's their current pain? — The specific problem your product solves for them right now

Product & Positioning

  1. What are you promoting? — Specific product, feature, or offer (free trial, case study, webinar, etc.)
  2. Core value prop — In one sentence: what do you do and why does it matter?
  3. Social proof available — Customer logos, case study metrics, review quotes, press mentions
  4. What are you NOT — Key competitor or alternative you want to differentiate from

Constraints

  1. Team size — Who's executing this? (founder only, 1 marketer, SDR+marketing, etc.)
  2. Budget — Rough range for paid/sponsored channels (or "zero — organic only")
  3. Existing assets — What do you already have? (blog posts, case studies, demo video, email list)

Phase 1: Channel Strategy

Based on intake answers, recommend 2-4 primary channels. For seed/Series A, resist suggesting more than 4 — execution quality beats channel breadth.

Channel Selection Criteria

ChannelBest ForMinimum Resource
Founder LinkedInThought leadership, top-of-funnel awareness3 posts/week, 30 min/day
Cold email (outbound)Direct pipeline from ICP listSDR or founder time + Smartlead
LinkedIn adsTargeted awareness with limited list$1,000+/month budget
Community engagementSlack/Discord communities where ICP is active1 hour/day, no budget
Content SEOLong-term inbound, compounding2 posts/week, 2-3 month horizon
Newsletter sponsorshipReaching existing engaged audiences$500-5,000/newsletter
Product HuntDeveloper/startup audience, launch moment2 weeks prep, launch day hustle
Event/conferenceHigh-intent networking, deal accelerationAttendance + budget
Partner co-marketingShared audiences, low-cost reachPartnership agreement

For each recommended channel, specify:

  • Primary role: Awareness / Consideration / Conversion
  • Expected output: What does success look like on this channel?
  • Estimated effort: Hours per week + budget
  • Who owns it: Which team member

Phase 2: Messaging Architecture

Define 3 core messages for the campaign — the angles you'll repeat across channels.

Message Structure

For each core message:

Message: [1-sentence core claim]
Evidence: [proof point — metric, case study, quote]
For: [which ICP segment this resonates with most]
Channel fit: [best channel(s) to deploy this message]

Messaging Hierarchy

LevelMessageExample
Primary (use everywhere)Core positioning statement"The only [category] built for [ICP]"
Secondary A (proof-driven)Customer outcome story"[Customer] 3x'd pipeline in 30 days"
Secondary B (contrast)Differentiation from status quo"Unlike [category], we [differentiator]"

Phase 3: Content Plan

Map specific content pieces to the channel plan. Be concrete — give working titles, not just "write some blog posts."

Content Calendar Format

WeekChannelContent PieceFormatOwnerGoal
Week 1LinkedIn"[Working Title]"Insight postFounder500 impressions
Week 1Cold emailLaunch sequence (Touch 1)EmailSDR20 demos booked
Week 2LinkedIn"[Working Title]"Case study postMarketing200+ reactions
Week 2Blog"[Working Title]"How-to postMarketing50 organic visits
...

Content types for seed/Series A (in order of leverage):

  1. Founder insight post (LinkedIn) — personal brand + thought leadership
  2. Customer story/result (any channel) — social proof
  3. Contrarian take / hot take — engagement bait
  4. How-to / tactical guide — ICP utility value
  5. Launch announcement — news peg for outreach

Phase 4: Success Metrics

Define KPIs before the campaign starts. Split by phase:

MetricTargetHow to Measure
Awareness[N] LinkedIn impressionsLinkedIn Analytics
Consideration[N] profile visits / email opensLinkedIn, Smartlead
Conversion[N] signups / demos / repliesCRM / product analytics
Quality[N%] ICP match on conversionsManual tagging

North star for this campaign: [single most important metric]

Phase 5: Output Format

# Campaign Brief — [Campaign Name]
Created: [DATE] | Owner: [Name]

## Goal
[1-sentence goal with number and timeline]

## ICP Target
[2-3 sentences: who, what pain, why now]

## Timeline
Start: [date] | End: [date] | Review: [midpoint date]

---

## Channel Strategy

### Channel 1: [Name]
- Role: [Awareness/Consideration/Conversion]
- Effort: [hours/week + budget]
- Owner: [person]
- Success metric: [what good looks like]

### Channel 2: [Name]
...

---

## Core Messages

### Primary
> "[message]"
Evidence: [proof]

### Secondary A
> "[message]"
Evidence: [proof]

### Secondary B
> "[message]"
Evidence: [proof]

---

## Content Calendar (Weeks 1-4)

| Week | Channel | Content | Format | Owner |
|------|---------|---------|--------|-------|
...

---

## Success Metrics

| Metric | Target | Owner |
|--------|--------|-------|
...

**North star:** [metric]

---

## What We're NOT Doing
(Scope constraints to prevent scope creep)
- Not running [channel] — not enough budget/time
- Not targeting [segment] — outside ICP for this campaign
- Not launching [content type] — need [prerequisite] first

---

## Assets Needed Before Launch
- [ ] [Asset 1] — Owner: [name] — Due: [date]
- [ ] [Asset 2] — ...

Save to clients/<client-name>/campaigns/[campaign-slug]/brief.md.

Tools Required

None. Pure reasoning. Works with any LLM agent.

Trigger Phrases

  • "Write a campaign brief for [launch/goal]"
  • "Help me plan a campaign targeting [ICP]"
  • "We're launching [thing] — give me a campaign plan"
  • "I have [N] weeks and [budget] — what campaign should I run?"

平台分布

Codex

36.68%
按下载量换算32

Claude

27.36%
按下载量换算24

Cursor

16.6%
按下载量换算14

Gemini CLI

9.57%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills