Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计提醒

article-writer文章作者

Agent Skill

article-writer 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

214

周安装

9

GitHub Stars

5,096

下载量

75
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:article-writer(文章作者)
来源仓库:https://github.com/netease-youdao/lobsterai
仓库路径:skills/article-writer
安装命令:
npx skills add https://github.com/netease-youdao/lobsterai --skill article-writer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/netease-youdao/lobsterai --skill article-writer

简介

用于查找、检索和筛选相关信息。article-writer 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

  • 适合根据关键词或任务场景快速定位候选结果。
  • 通过 GitHub 安装,可结合项目上下文使用。
  • 需确认权限范围和维护状态,避免触发不必要操作。
  • 建议参考原始 README 了解具体用法和输出格式。

SKILL.md

Multi-Style Article Creation

Use Cases

  • User says "写一篇关于XX的文章"
  • User says "帮我写一篇公众号文章"
  • User selects a topic from the content calendar to start writing
  • User specifies a writing style (e.g., "深度分析风格", "写个教程")

5 Writing Styles

Style IDNameCharacteristicsWord CountUse Cases
deep-analysis深度分析Rigorous structure, data-backed2000-4000 wordsTrend analysis, in-depth reporting
practical-guide实用指南Clear steps, highly actionable1500-3000 wordsTool tutorials, how-to guides
story-driven故事驱动Conversational, emotional resonance1500-2500 wordsPersonal stories, case reviews
opinion观点评论Sharp opening, pros/cons argumentation1000-2000 wordsHot takes, controversial topics
news-brief新闻简报Inverted pyramid, fact-focused500-1000 wordsBreaking news, information roundups

Workflow

Step 1: Read the Brief

Obtain topic information from:

  1. Entries with status planned in content_calendar.json
  2. Topic description directly provided by the user

Extract key information:

  • Topic direction / title
  • Target audience
  • Writing style (if not specified, recommend based on topic content)
  • Reference material URLs

Step 2: Determine Writing Style

If user hasn't specified, recommend based on topic:

Topic CharacteristicsRecommended Style
Involves data, trends, underlying causesdeep-analysis
"How to", "tutorial", "steps"practical-guide
Involves people, experiences, insightsstory-driven
Involves controversy, hot topic commentaryopinion
Breaking events, quick informationnews-brief

Confirm the style choice with the user.

Step 3: Material Collection

Use content-planner's search script to collect reference materials:

node "$SKILLS_ROOT/content-planner/scripts/wechat_search.js" "topic keywords" -n 10

Also use web-search skill for additional materials.

Organize material list:

  • Citable data/statistics
  • Reference cases/stories
  • Facts that need verification

Step 4: Generate Outline

Generate an outline based on the selected style using the corresponding structure template.

deep-analysis Template

## 引入 (200-300字) — 反直觉数据/现象开头
## 背景 (300-500字) — 事件/现象的来龙去脉
## 分析维度1 (400-600字) — 核心论点 + 数据支撑
## 分析维度2 (400-600字) — 对比/反面论证
## 分析维度3 (400-600字) — 深层原因 + 影响预测
## 总结与展望 (200-300字) — 核心观点 + CTA

practical-guide Template

## 开头 (100-200字) — 痛点共鸣 + 承诺
## 前置准备 (200-300字)
## 步骤1 (300-500字) — 具体操作 + 常见坑
## 步骤2 (300-500字) — 具体操作 + 关键参数
## 步骤3 (300-500字) — 具体操作 + 验证方法
## 进阶技巧 (200-300字)
## 总结 (100-200字) — FAQ + CTA

story-driven Template

## 开头 (150-200字) — 场景切入 + 悬念
## 背景铺垫 (200-300字) — 人物/背景/冲突
## 转折1 (300-400字) — 关键事件 + 感受
## 转折2 (300-400字) — 新尝试 + 结果
## 高潮 (200-300字) — 核心洞察
## 结尾 (150-200字) — 启发 + CTA

opinion Template

## 锐利开头 (100-150字) — 直接亮观点
## 现象描述 (200-300字) — 主流观点
## 正面论证 (300-400字) — 我的论点 + 数据
## 反面回应 (200-300字) — 预设反驳 + 反驳
## 深度思考 (200-300字) — 本质 + 影响
## 总结 (100-150字) — 重申观点 + CTA

news-brief Template

## 核心信息 (100-200字) — What/When/Where/Who
## 事件详情 (200-300字)
## 背景 (100-200字)
## 反应 (100-200字)
## 编者按 (50-100字)

Step 5: User Approval of Outline

This is a mandatory approval gate and cannot be skipped.

Present the outline to the user and ask for confirmation or modification requests.

Step 6: Write the Content

After approval, write content paragraph by paragraph following the outline.

Universal Writing Rules:

  1. Use stories instead of preaching

- ❌ "风险管理很重要,应该做应急预案" - ✅ "去年,我的创业团队差点因为一个核心员工离职而崩溃,因为我们没有任何备选方案。"

  1. Use analogies and metaphors

- ❌ "分布式系统很复杂" - ✅ "分布式系统就像连锁餐厅——每个分店需要协作,同时又要独立运营。"

  1. Support with data but don't pile it on

- ❌ "据IDC报告,全球AI市场2023年增长45%,预计2025年达1000亿美元..." - ✅ "AI市场疯狂增长——每年翻一番。但在增长背后,真正赚钱的公司不到5家。"

  1. State opinions directly, avoid ambiguity

- ❌ "有人认为...也有人认为...各有道理" - ✅ "说实话,我认为XX的做法是错的,因为..."

  1. Use short sentences and line breaks

Data integrity rules:

  • If specific data is needed but uncertain, mark [数据待确认] and confirm with user
  • Use search tools to verify key facts
  • Can tell fictional stories using "我见过..." or "一个朋友...", but don't fabricate data

Step 7: Formatting Optimization

WeChat Formatting Hard Rules:

  1. Paragraphs no more than 4 lines (mobile screen visible range)
  2. Insert a subheading or bold sentence every 3-4 paragraphs
  3. Must have a hook within the first 3 lines (question, data, story, counter-intuitive viewpoint)
  4. Must have a clear CTA at the end (follow/share/comment prompt)

Markdown Formatting Standards:

  • No first-line indentation, use blank lines to separate paragraphs
  • Maximum 2 heading levels (##), no deep nesting
  • Bold only the 1-2 most important words per paragraph
  • Use quotes for data, golden sentences, or important viewpoints
  • Lists maximum 5 items

Step 8: Output Draft

Save the article as Markdown:

Filename format: drafts/YYYYMMDD_[topic-slug].md

---
title: Article Title
date: YYYY-MM-DD
style: deep-analysis
summary: Article summary (within 100 words)
---

## Opening

Content...

Step 9: Quality Checklist

✅ Title — Sparks curiosity or resonance
✅ Opening — First 100 words are engaging
✅ Body — Has 2-3 clear viewpoints
✅ Cases — Uses stories not preaching
✅ Formatting — Easy to read (short paragraphs, bold, subheadings)
✅ Word Count — Within style-specified range
✅ CTA — Ending has action prompt

Title Optimization Process

Step 1: Generate 10 Candidate Titles

Use these psychological strategies:

StrategyDescriptionExample
SuspenseSpark curiosity"为什么我放弃了年薪50万的工作"
BenefitClarify reader gains"掌握这3个技巧,效率提升200%"
Pain PointHit reader anxiety"别让这个习惯毁了你的职业生涯"
NumbersSpecific and tangible"50%的人都误解了这个真相"
RhetoricalStimulate thinking"你真的了解AI吗?"
ContrastCreate contrast"BAT vs 创业公司:差别在哪"

Step 2: Score and Filter

Score on 3 dimensions (Attractiveness 40%, Shareability 30%, SEO 30%) and present top 3 to user.

Integration with Other Skills

  • Upstream: content-planner's content_calendar.json provides topic input
  • Downstream: Markdown files in drafts/ can be further processed

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.95%
按下载量换算27

Claude

31.83%
按下载量换算24

Cursor

19.31%
按下载量换算14

Gemini CLI

10.75%
按下载量换算8

安全审计

Gen Agent Trust Hub

可疑

Socket

通过

Snyk

可疑

权限和风险

只读

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills