Token导航 LogoToken导航TokenDH.com
研究检索只读clawhub未标认证来源可访问clear审计通过

article-rewriter文章重写者

Agent Skill

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

总安装

8,753

周安装

376

GitHub Stars

公开资料未说明

下载量

3,068
OpenClaw

安装说明

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

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install article-rewriter

简介

重写文章、通讯稿等内容以提升表达清晰度。

  • 重组逻辑结构并增强说服力与吸引力。article-rewriter 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 适用于营销文案、产品介绍等对外传播材料。
  • 安装命令:openclaw skills install article-rewriter。
  • 改写后应保留原意,避免过度偏离原始意图。

SKILL.md

name
article-rewriter
description
Rewrite and restructure articles, newsletters, threads, scripts, landing pages, and rough notes into clearer, more engaging, more persuasive writing. Use when the user asks to 改写文章、重写草稿、重构结构、增强标题或开头、提升说服力、把笔记整理成文章、把长文压缩成短帖、或把现有内容适配到公众号、邮件、视频脚本、销售页等场景。 Default framework: APAG (Attention, Perspective, Advantage, Gamify).

Article Rewriter

Overview

Use APAG as the default operating system for rewriting. Optimize for curiosity, clarity, transformation, and action without changing the author's core facts or intent.

Keep the rewrite itself as the primary deliverable. Explain the framework only when the user asks for analysis or rationale.

Workflow

  1. Identify the rewrite target.

- Determine audience, desired action, target format, target length, tone, and whether the user's original voice should be preserved closely. - If the user does not specify a format, keep the original format and length class by default.

  1. Confirm the source material.

- If the user has not supplied the article, draft, transcript, or notes to rewrite, ask for it before drafting. - If the source is fragmentary, state key assumptions briefly instead of pretending the missing context is known.

  1. Diagnose the source before rewriting.

- Extract the central promise, reader problem, current/common viewpoint, better viewpoint, proof, and desired next action. - Mark factual gaps mentally and avoid inventing testimonials, research, metrics, or customer stories.

  1. Choose the structure.

- Long-form default: Attention -> Perspective -> Advantage -> Gamify -> concise ending or CTA. - Short-form default: A+P, A+A, or A+G. Keep one core idea per piece. - If the user explicitly requests AIDA, PAS, PASTOR, or another framework, use that framework while preserving APAG-level curiosity and payoff.

  1. Rewrite.

- Preserve thesis and non-negotiable facts. - Rebuild the opening, strengthen sequencing, cut repetition, replace abstractions with concrete scenes or contrasts, and surface a real next step.

  1. Deliver.

- Unless the user asks otherwise, provide 3 headline or hook options plus the rewritten piece. - Add short rewrite notes only when they help the user evaluate choices.

Rewrite Decision Rules

  • If the draft is weak mainly at the opening, spend more effort on Attention than on line-level polishing.
  • If the draft is informative but flat, strengthen Perspective and Advantage.
  • If the piece is inspiring but not actionable, strengthen Gamify.
  • If the user asks for "润色" or "polish", keep the structure mostly intact and apply APAG lightly.
  • If the user asks for "重写" or "rewrite from scratch", rebuild the structure more aggressively.
  • If the facts are thin, improve framing and clarity instead of faking authority.

APAG Rewrite Standard

Attention

Build a hook that earns attention through relevance, comprehension, and speed of payoff.

Prioritize some of these building blocks:

  • Big problem
  • Big benefit
  • Big idea
  • Transformation process
  • Time frame or effort
  • Personal low point or tension

Create an honest information gap. Avoid empty clickbait.

Perspective

Show the reader's current problem and the flawed or default way of seeing it.

Useful devices:

  • Common belief to challenge
  • Personal anecdote
  • Sharp contrast
  • Example or case
  • Metaphor
  • Specific pain caused by the wrong view

Make the reader feel understood before redirecting them.

Advantage

Show the better frame, mechanism, or method.

Useful materials:

  • Novel concept or naming
  • Explanation of why the better view works
  • Proof, experience, quote, or observation
  • Before/after contrast
  • Clear benefit chain

Sell the idea, not just the style.

Gamify

Translate the better view into a sequence the reader can act on.

Prefer:

  • Numbered steps
  • Checklists
  • Challenge ladders
  • Operating rules
  • A direct CTA or next move

Make the path feel achievable and concrete.

Story Logic

Use curiosity plus payoff:

  • Introduce or imply a problem.
  • Create a gap around cause, consequence, or solution.
  • Pay off the gap with proof, sequence, and a believable next step.

Treat story broadly. Anecdotes, research, examples, metaphors, comparisons, quotes, and observations all count if they improve understanding.

Output Patterns

Existing article to stronger article

  • Keep the thesis and evidence.
  • Rebuild the hook, section order, transitions, and CTA.

Notes or voice dump to article

  • Infer the thesis first.
  • Build a clean APAG arc around the strongest insight.

Long article to short post

  • Collapse to one promise, one tension, one shift, and one action.

Generic article to sales or persuasive page

  • Make the problem more concrete, proof more visible, and CTA explicit without sounding like spam.

Constraints

  • Do not fabricate facts, testimonials, research, or outcomes.
  • Do not overwrite the author's viewpoint unless the user asks for repositioning.
  • Do not turn every rewrite into hype. Keep claims proportional to the evidence.
  • Do not preserve weak repetition just because it existed in the draft.
  • Prefer natural modern Chinese over translationese when writing Chinese.
  • Simplify jargon unless the target audience clearly needs it.

Reference

Read references/apag-playbook.md when you need the detailed hook checklist, APAG prompts, or long-form vs short-form mapping.

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

补充不同宿主或平台的使用分布数据

能力 5

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

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

平台分布

OpenClaw

97.08%
按下载量换算2,978

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills