Token导航 LogoToken导航

Agent Skill · 研究检索

mkt-content-briefs(市场内容简介)

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

mkt-content-briefs 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 73,543。

总安装 1周安装 8GitHub Stars 2下载 65核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:mkt-content-briefs(市场内容简介)
来源仓库:https://github.com/hungv47/agent-skills
仓库路径:skills/mkt-content-briefs
安装命令:
npx skills add https://github.com/hungv47/agent-skills --skill mkt-content-briefs
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/hungv47/agent-skills --skill mkt-content-briefs

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

mkt-content-briefs 辅助文档结构与内容稿件整理。适合提炼 README、Markdown 或对外文案的框架。保留已有事实,统一术语,避免过度营销表述。涉及外部链接或数据引用时应交叉验证来源。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/mkt-content-briefs

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

mkt-content-briefs 怎么安装?

在终端执行 npx skills add https://github.com/hungv47/agent-skills --skill mkt-content-briefs。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

mkt-content-briefs 支持哪些 AI 工具?

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

mkt-content-briefs 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

mkt-content-briefs 是免费的吗?

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

mkt-content-briefs 用的人多吗?

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

mkt-content-briefs 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

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

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

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

研究检索类 Skill 对比

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

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
mkt-content-briefs

市场内容简介 · 本页

12只读未明确通过

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

SKILL.md 原文

Content Briefs

*Part of the Problem → Solution → Communicate framework. Executes the Communicate phase — turning IMC plans into production-ready content.*

Transform IMC plan outputs (angles, channels, pillars) into production-ready creative content—complete with written copy, hooks, scripts, and CTAs. The production team only needs to design/produce the visuals.

Philosophy

  • Platform-native content beats generic posts
  • Complete copy beats placeholder text
  • Specific CTAs beat "learn more"
  • Content should advance KPIs, not just fill feeds
  • Every piece serves a purpose in the awareness journey

Before Starting

Check if they have an IMC plan. If not, suggest mkt-imc first or gather:

  • Angle with hook type, trigger, awareness stage
  • Channel (native + type + name)
  • Pillar context
  • Voice/tone guidelines

Ask: *"Do you have an IMC plan with angles and channel allocation? If not, what angle and channel are we creating content for?"*


The Flow

IMC Plan → Select Angle/Channel → Distribution Target → Content Specification → Write Full Copy → Production Guidelines

Phase 1: Select from IMC Plan

If they have an IMC plan, pull from the allocation table.

Ask: *"Which angle from your IMC plan are we creating content for? Which channel?"*

Need:

ElementSourceExample
AngleAllocation table"Teams waste 5hrs/week on status updates"
Hook TypeAngle bankData
TriggerAngle bankFrustration
StageAngle bankProblem Aware
PillarPillar tableProductivity
Channel NativeAllocationLinkedIn
Channel TypeAllocationOwned
Channel NameAllocation@brand
Voice/ToneStrategy FoundationDirect, data-backed

Phase 2: Distribution Target

Confirm the exact placement and pull platform specs.

Step 1: Confirm Channel Details

FieldValue
Channel Native[X/TikTok/Instagram/LinkedIn/YouTube/etc.]
Channel Type[Owned/Partner/Paid KOL/Ecosystem/Earned]
Channel Name[Specific account]
Placement[Feed/Stories/Reels/Thread/Carousel/etc.]

Step 2: Pull Platform Specs

Reference platform-specs.md for:

  • Aspect ratio and resolution
  • Max duration or character count
  • Caption/subtitle requirements
  • Audio specs
  • Safe areas
  • Platform-native patterns

Example output:

SpecValue
PlatformTikTok
PlacementIn-feed video
Aspect Ratio9:16 (1080x1920)
Duration15-60 seconds
CaptionsRequired (burned in or native)
AudioMusic/voice allowed, trending sounds boost reach
Safe AreaTop 150px (username), bottom 270px (buttons)

Phase 3: Content Specification

Derive the content spec from the angle and channel.

Purpose (from Awareness Stage)

StageContent PurposeGoal
UnawareSurface the problemMake them say "I didn't realize..."
Problem AwareValidate and agitateMake them say "This is exactly my struggle"
Solution AwareDifferentiateMake them say "This is different because..."
Product AwareOvercome objectionsMake them say "My concern was X, but..."
Most AwareDrive actionMake them say "I'm ready to..."

Content Type (from Hook Type)

Hook TypeContent TypeFormat Pattern
QuestionCuriosity-drivenOpen with question, reveal answer
Bold claimThesis-drivenState claim, back with proof
How-toEducationalStep-by-step, actionable
StoryNarrativeSetup, conflict, resolution
DataEvidence-drivenNumbers first, context second
Sneak peekExclusive revealBehind the scenes, insider access
ContrarianCounter-narrativeCommon belief vs. reality
AnalogyExplainerComplex → simple comparison

Format (from Channel Native)

Match format to platform patterns. See platform-specs.md.

Narrative Throughline

One sentence that captures the journey:

"[Target audience] thinks [current belief], but [angle insight] because [reason], so they should [action]."

Example:

"Engineering managers think adding headcount fixes slow shipping, but process bottlenecks cause most delays because code review queues and unclear ownership stall PRs, so they should map their actual workflow before hiring."

Phase 4: Content Creation (Full Copy)

Write the complete creative—not specs, not placeholders, but actual copy ready for production.

Hook (First 3 Seconds / First Line)

The hook stops the scroll. Write the exact text.

Hook TypePatternExample
Question"Have you ever [relatable experience]?""Have you ever spent more time reporting on work than doing it?"
Bold claim"[Controversial statement]""Your team doesn't have a productivity problem. You have a meetings problem."
How-to"How to [outcome] without [sacrifice]""How to ship 2x faster without hiring"
Story"I [action] and [unexpected result]""I cut our meetings by 80% and output doubled"
Data"[Surprising number/stat]""The average employee spends 31 hours/month in unproductive meetings"
Sneak peek"Here's what [insiders] actually do""Here's what high-performing eng teams actually measure"
Contrarian"Stop [common advice]""Stop tracking velocity. Track this instead."

For video: Write the opening line/visual exactly as it appears on screen or is spoken.

For static/carousel: Write the headline/title text.

For threads: Write the first tweet.

Body/Script

Write the complete content—not an outline, the actual copy.

For video scripts:

[0:00-0:03] HOOK
Text on screen: "[Hook text]"
Voiceover: "[What they say]"
Visual: [What's shown]

[0:03-0:15] SETUP
Text on screen: "[Text]"
Voiceover: "[Script]"
Visual: [Description]

[0:15-0:45] MAIN CONTENT
...

[0:45-0:60] CTA
Text on screen: "[CTA text]"
Voiceover: "[Script]"
Visual: [Final frame]

For static posts:

Write the complete caption—every word that will be posted.

For carousels:

Write every slide:

  • Slide 1: [Cover/Hook]
  • Slide 2: [Content]
  • ...
  • Final slide: [CTA]

For threads:

Write every post:

  • 1/ [First tweet with hook]
  • 2/ [Second tweet]
  • ...
  • [Final tweet with CTA]

CTA (Call to Action)

Write the exact CTA—what they click, tap, or do.

StageCTA PatternExample
UnawareLearn more"See why this matters →"
Problem AwareExplore"Discover the fix →"
Solution AwareCompare"See how we're different →"
Product AwareTry"Start free trial →"
Most AwareAct"Start now →"

Include:

  • CTA text: The exact button/link text
  • Destination: Where it goes
  • Tracking: UTM or attribution notes

Caption (if applicable)

For platforms with separate caption fields (Instagram, TikTok, YouTube), write the complete caption:

[First line hooks in feed preview]

[Body copy - expand on the content]

[CTA - what to do next]

[Hashtags if applicable]

Phase 5: Production Guidelines

Give the production team everything they need.

Visual Direction

Describe the visual style without creating the visuals:

  • Mood: [Energetic/Calm/Professional/Playful/etc.]
  • Color palette: [Brand colors to emphasize]
  • Typography: [Bold headlines/Clean minimalist/etc.]
  • Imagery style: [Screenshots/Motion graphics/Talking head/B-roll/etc.]
  • Key visual elements: [Charts, UI mockups, product shots, etc.]

Brand Tone Adaptation

How the brand voice adapts for this specific channel. See platform-specs.md for default tone adaptation by platform.

Do's and Don'ts

DoDon't
[Specific guidance][Specific warning]
[Example][Example]

Assets Needed

Checklist for production:

  • [Asset 1 with specs]
  • [Asset 2 with specs]
  • [Audio/music requirements]
  • [Brand assets needed]

Output Format

The final deliverable:

## Content Brief: [Title]

### Distribution Target
- **Channel:** [X/TikTok/etc.]
- **Placement:** [Feed/Stories/etc.]
- **Format:** [Video/Carousel/Thread/etc.]
- **Specs:** [Dimensions, duration, character limit]

### Content Specification
- **Purpose:** [From awareness stage]
- **Content Type:** [From hook type]
- **Narrative:** [One-line throughline]

### Creative Content

**Hook:**
[Full hook text exactly as it appears/is spoken]

**Body/Script:**
[Complete script with timestamps OR full post copy]

**CTA:**
- Text: [Exact CTA copy]
- Destination: [URL/action]

**Caption:**
[Full caption if applicable]

### Production Guidelines

**Visual Direction:**
[Mood, colors, typography, imagery style, key elements]

**Tone:** [How brand voice adapts — see platform-specs.md]

**Do's / Don'ts:**
- [Key guidance]

**Assets Needed:**
- [ ] [List with specs]

Working with Multiple Pieces

When creating content batches:

From One Angle → Multiple Formats

Repurpose systematically:

HERO: [Primary format for this angle]
├── DERIVATIVE 1: [Format]
├── DERIVATIVE 2: [Format]
└── DERIVATIVE 3: [Format]

MICRO:
├── [Format]
├── [Format]
└── [Format]

Content Calendar View

For batch briefs, organize by publish date:

DateAngleChannelFormatHook PreviewStatus
[Date][Angle][Channel][Format][First few words][Draft/Ready]

Examples

See references/examples.md for complete worked examples with full copy:

  • B2B SaaS: LinkedIn carousel with all slide copy
  • D2C Brand: TikTok video script with full dialogue
  • B2B SaaS: X thread with complete post sequence

Next Steps

After creating content briefs, use mkt-attribution to map each content piece to its initiative and KPI. This verifies every piece you're producing advances your goals and flags orphan content.

How to Work

  • Write the actual copy, not descriptions of copy
  • Be specific, not generic—"Link in bio" isn't a CTA
  • Match platform patterns—what works on TikTok doesn't work on LinkedIn
  • Include everything production needs—they shouldn't have to guess
  • Reference the angle's metadata—hook type, trigger, stage should shape the content
  • Ask questions if the angle or channel isn't clear
  • Adapt voice for channel while staying on-brand

平台分布

Codex

33.71%
按下载量换算22

Claude

29.65%
按下载量换算19

Cursor

19.54%
按下载量换算13

Gemini CLI

9.52%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills