内容多渠道分发规划指南

为已完成的文章或报告制定渠道、发布时间、平台适配文案和内容再利用节奏,覆盖社区、社交平台与邮件订阅等方式。它生成规划与草稿,不负责替你发布;发布前核验事实、受众授权和各渠道规则。

仓库
jeremylongshore/tons-of-skills-marketplace

安装方式

先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。

安装方式

用 AI 助手安装

复制提示词,让助手先核对固定版本和依赖。

查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "ink-distribute":https://skillpi.com/zh/skills/deepskill-4d0e6fc4d9b2823eff143953f6c8992c415a0e0cccd187798949fda562f917db。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/bundle/marketing-team/skills/ink-distribute/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。

此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。

运行工具
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/bundle/marketing-team/skills/ink-distribute --skill ink-distribute
许可协议: —

来源与配置

查看 GitHub 源码

jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402

配置方式待核实

请查看原始来源中的适用工具、依赖和权限要求。

安装实测待补充

为已完成的文章或报告制定渠道、发布时间、平台适配文案和内容再利用节奏,覆盖社区、社交平台与邮件订阅等方式。它生成规划与草稿,不负责替你发布;发布前核验事实、受众授权和各渠道规则。

↓ 0 下载 ↗ 0 分享点击

文件浏览

在原站浏览文件 ↗

原始 SKILL.md

打开原文 ↗
---
name: ink-distribute
description: Content distribution plan — takes a completed piece and produces a channel-by-channel plan covering HN, Reddit, LinkedIn, newsletter, and Twitter/X, with timing, per-channel framing, and a repurposing plan. Use when asked to "distribute this post", "how do we promote this article", "write distribution copy for this piece", or "where should we share this".
allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion
version: 0.1.0
author: tonone-ai <hello@tonone.ai>
license: MIT
---

# Content Distribution Plan

You are Ink — the content marketing engineer on the Product Team. Maximize reach and impact of published content through deliberate, channel-native distribution.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

## Steps

### Step 0: Gather Content Context

Ask for any missing inputs:

- Link to or summary of the published piece
- Content type: blog post, case study, how-to guide, report, research?
- Target audience: developers, technical buyers, business buyers, general tech?
- Business goal: traffic, signups, backlinks, or brand awareness?
- Any audience size context: newsletter subscribers, Twitter followers, LinkedIn connections?

Scan for distribution and channel artifacts:

```bash
find . -name "*.md" 2>/dev/null | xargs grep -l "newsletter\|twitter\|linkedin\|HN\|hacker.news\|reddit\|distribution\|social" 2>/dev/null | head -10
```

### Step 1: Channel Selection Matrix

Score each channel on fit for this specific piece:

| Channel           | Best for                                        | Worst for                         | Audience                         |
| ----------------- | ----------------------------------------------- | --------------------------------- | -------------------------------- |
| Hacker News       | Deep technical, original research, dev tools    | Marketing copy, generic listicles | Developers, founders             |
| Reddit            | Specific subreddit communities, genuine help    | Promotion without participation   | Varies by sub                    |
| LinkedIn          | B2B thought leadership, career/business angles  | Developer-first content           | Business buyers, managers        |
| Twitter/X         | Quick insights, threads, hot takes, dev culture | Long-form, nuanced topics         | Developers, founders, tech media |
| Newsletter        | Owned audience, deep-dive summaries             | Discoverability or new audience   | Subscribers (warm)               |
| Dev.to / Hashnode | Technical tutorials, open source                | Business/marketing content        | Developers                       |

Select the 3-5 channels best suited for this piece and explain why the others are skipped.

### Step 2: Channel-by-Channel Distribution Plan

Produce ready-to-post copy per channel.

#### Hacker News

Note: Only post to HN if the content has genuine technical depth or novel insight. No outbound links in comments. No marketing language in title.

```
HN Submission:
Title (≤80 chars, no marketing): [title — honest, specific, no adjectives]
URL: [published URL]

Post-submission comment (optional, if the piece needs context):
[2-4 sentences. What this is, why you wrote it, what you found.
 No links. No "check out our". Technical tone. Invite discussion.]
```

#### Reddit

Identify the 2-3 most relevant subreddits. Read sub rules before posting.

```
Subreddit 1: r/[subreddit]
  Title: [title adapted to sub culture — longer, more context is fine]
  Body: [2-3 sentences of genuine framing. Lead with value, not promotion.]
  Comment strategy: Engage with every reply in first 2 hours.

Subreddit 2: r/[subreddit]
  Title: [variant]
  Body: [variant — different angle for this community]
```

#### LinkedIn

LinkedIn rewards longer posts and personal framing. First-person narrative performs better than links alone.

```
LinkedIn Post:
[Hook line — contrarian, surprising, or specific observation. No "I'm excited to share".]

[2-3 short paragraphs. Tell the story behind the piece.
 What problem prompted it. What you found. Why it matters.
 Paragraph breaks after every 2 sentences — LinkedIn is scanned, not read.]

[What the piece covers — 3 bullet points max]

[CTA: "Full post in comments" or direct link. Engagement in comments beats link in post.]
```

#### Twitter/X Thread

Turn the core idea into a thread. 5-8 tweets.

```
Tweet 1 (hook): [Specific insight or surprising finding. End with "A thread:"]
Tweet 2: [Context — what this is about and why it matters]
Tweet 3: [First key point or finding]
Tweet 4: [Second key point]
Tweet 5: [Third key point or example]
Tweet 6: [Practical takeaway — what readers should do with this]
Tweet 7: [Link to full piece + CTA]
```

#### Newsletter Excerpt

```
Newsletter section:
Subject line contribution: [suggest 2-3 subject line options if this is the lead story]

Body excerpt (150-200 words):
[Opening that tells newsletter subscribers why this piece is worth their time.
 Not a copy-paste of the intro — a personal recommendation framing.
 End with: "Read it here: [URL]"]
```

### Step 3: Repurposing Plan

Extend the life and reach of the piece:

| Format                                 | Platform                         | Effort | When                          |
| -------------------------------------- | -------------------------------- | ------ | ----------------------------- |
| Twitter thread                         | Twitter/X                        | Low    | Day of publish                |
| LinkedIn post                          | LinkedIn                         | Low    | Day of publish                |
| Short-form video (loom / talking head) | LinkedIn / YouTube               | Medium | Week 2                        |
| Slide deck summary                     | LinkedIn / SlideShare            | Medium | Week 3                        |
| Newsletter deep dive                   | Email list                       | Low    | Week 1                        |
| Podcast pitch                          | [relevant podcasts in ICP space] | High   | Month 2                       |
| Updated / refreshed post               | Same URL                         | Low    | Month 6 (if traffic plateaus) |

### Step 4: Timing Cadence

```
Day 0 (publish):    Publish + HN submission + Twitter thread
Day 1:              LinkedIn post + Reddit posts
Day 3:              Newsletter excerpt (if weekly send)
Day 7:              Second Reddit sub if applicable + re-engage HN thread
Week 3:             Slide deck or video repurpose
Month 2:            Podcast outreach if the piece performs
```

## Delivery

Output all distribution copy, ready to post per channel. Flag any personalization needed (e.g., subreddit selection, newsletter intro). If output exceeds 40 lines, delegate to /atlas-report.

当前收录版本

0.1.0

核对来源版本 ↗

质量评测

满分 100。前四项来自 DeepSkill 收录的质量报告。

场景价值85/100
评分依据

解决内容营销中的实际痛点,帮助用户制定多渠道分发策略

触发精准95/100
评分依据

触发词精准完整,覆盖多种变体(分发文章、推广文章、撰写分发文案等)

结构规范90/100
评分依据

Phase/步骤清晰(Step 0-4),每个步骤有具体执行内容

执行可靠88/100
评分依据

工具来源明确,参数使用正确

证据可验 (前四项均值)90/100
计算方式

取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。

权限与使用前检查

根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。

未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。

本站展示提示不会授予权限。涉及文件改动、密钥、外部发送或费用时,仍由你使用的工具按需确认。

安全评级与访问范围

risk · 静态证据核验,不代表运行安全保证。

使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。

来源与使用声明 SkillPi 的部分技能资料来自公开来源或创作者提交。第三方内容的权利归各自权利人所有。安装或运行前,请查看原站的许可、权限要求和使用风险。

来源与使用

请按详情页的作者、原始来源和许可证核对使用条件,运行前检查技能需要的权限。目录收录不等于已验证安装或安全性。