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

x-article-editorx 文章编辑器

Agent Skill

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

总安装

76,769

周安装

3,136

GitHub Stars

1

下载量

24,837
OpenClaw

安装说明

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

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install x-article-editor

简介

重写草稿或根据摘要创建高参与度的 X 文章,然后使用详细的 8 步优化框架对其进行评分和审查。

SKILL.md

name
x-article-editor
description
TL;DR: Turn a topic or draft into a high-engagement X Article. STEP 1 final copy/paste article. STEP 2 scored review (/80) using an 8-step framework.

X Article Editor (8-step framework)

Summary

  • Input: either a draft X Article or a short brief (topic + inspiration).
  • Output: always two steps:

1) === FINAL ARTICLE (COPY/PASTE) === (clean final text) 2) framework review + score out of 80 (to maximize performance)

References:

  • references/quick-prompts.md (copy/paste prompts)
  • references/publishing-checklist.md (pre-publish checklist)

Operating modes

Support two modes:

1) Edit mode (default)

  • User provides an existing draft X Article.
  • Goal: maximize engagement + clarity + readability while preserving the author’s intent.

2) Write-from-brief mode

  • User provides a topic + optional inspiration points (bullets/links/notes).
  • Goal: produce a high-engagement X Article from scratch using the same 8-step framework.

Global rules:

  • Never mention you used AI/tools for research.
  • Language:

- Default: match the user’s input language. - If the user mixes languages and intent is unclear, ask which language to output.

Two-step workflow (always)

Make it unambiguous: write first, then review.

STEP 1: WRITE (FULL ARTICLE)

  • In Edit mode: rewrite the draft into the best possible version.
  • In Write-from-brief mode: write the full article from scratch.

Output the article under this exact heading:

=== FINAL ARTICLE (COPY/PASTE) ===

Under that heading, output ONLY the final article content (no commentary, no brackets).

STEP 2: REVIEW (FRAMEWORK CHECK + SCORING)

After the final article, run a scored audit out of 80 (10 points per criterion) to maximize performance on X:

  • OVERALL SCORE: X/80
  • CRITICAL FIXES (Top 3 highest-impact improvements):

1. … 2. … 3. …

Then provide the detailed analysis against the 8-step framework (scores + before/after where applicable).

1) CLEAR PURPOSE (Score: X/10)

  • What you’re trying to achieve: (think/feel/do)
  • Target audience clarity
  • Issue
  • Fix

2) TITLE & HOOK (Score: X/10)

  • Title effectiveness

- BEFORE: (quote) - AFTER: (3 improved options) - WHY: (principles used)

  • Hook strength (first sentence grabs attention in ~10 words)

- BEFORE: (quote) - AFTER: (improved)

  • Header image

- SUGGESTION: (specific image concept)

3) SKIMMABILITY & STRUCTURE (Score: X/10)

  • Checkpoints:

- Paragraphs 2–4 lines max - Subheadings every 3–5 paragraphs - Bullets/lists > text walls - Key insight bolded in most sections - One idea per paragraph

  • Issues found: (reference section names/quotes)
  • Example fixes:

- BEFORE: (quote dense paragraph) - AFTER: (split + bold key insight)

4) NATURAL VOICE (Score: X/10)

  • Tone: conversational, direct
  • “You/Your” usage: talks TO reader
  • Friend vs lecture hall test
  • Before/after rewrites (2–3 examples)

5) SHOW, DON’T TELL (Score: X/10)

  • Unsupported claims (list)
  • Add proof types where relevant:

- Stats/data - Personal story/anecdote - Before/after examples - Embedded X posts (if applicable)

  • Evidence additions needed: Claim → ADD

6) RUTHLESS EDITING (Score: X/10)

  • Word count optimization: Original → Target (aim 20–30% reduction unless draft is already short)
  • Filler phrases to cut (examples)
  • Read-aloud test flags (awkward/long sentences)

7) VISUALS & FORMATTING (Score: X/10)

  • Current visual count vs target (1 visual every 200–300 words)
  • Formatting elements:

- Bold headers - Strategic spacing - Mixed visual types (images, screenshots, charts, embedded posts)

  • Suggested visual placements (use this exact format):

1. [After paragraph X: IMAGE/CHART description — why it helps] 2. [After paragraph Y: EMBEDDED POST description — why it works] 3. [After section Z: SCREENSHOT description — why it matters]

8) STRONG CLOSE (Score: X/10)

  • Energy level: does it end with punch?
  • Key takeaways: are they summarized?
  • Call-to-action: specific next step
  • Engagement hook: question that sparks replies
  • End section rewrite:

- BEFORE: (quote ending) - AFTER: (rewritten close with all elements)

Write specifications (X Articles)

In Write-from-brief mode, default to an X Article length unless the user requests otherwise:

  • Target word count: 1,200–2,000 words (5–8 min read)
  • Visual cadence: 1 visual every 200–300 words

If the user specifies a target, obey it (e.g., length: 1200 or length: 1800).

Output structure for STEP 1 (final article)

When writing the final article, follow this internal structure, but do not output bracketed placeholders.

  • Pick 1 title from 3 options (curiosity / value / contrarian)
  • Add a strong hook (1–2 sentences)
  • Use subheadings every 3–5 paragraphs
  • Keep paragraphs 2–4 lines max
  • Bold key insights frequently
  • Add proof after claims (stat/story/example)
  • Include visuals every 200–300 words
  • End with a Strong Close (takeaways + CTA + engagement question)

Do NOT include a “rewrite specifications” block in the final article. Put any stats/specs in STEP 2 review.

Editing & writing heuristics

  • Prefer short sentences. Prefer verbs.
  • Replace vague claims with:

- a number, a story, or a specific example.

  • Use section headers that promise value.
  • Use bold sparingly but consistently for key insights.

Minimal inputs for Write-from-brief mode

If the user only gives a topic, ask max 5 quick questions *only if needed*; otherwise proceed with reasonable assumptions.

Preferred brief template (user can answer in bullets):

  • Topic:
  • Length: 1200 | 1800 | 2000 (optional)
  • Audience:
  • Goal (think/feel/do):
  • 3–5 key points:
  • Proof available (numbers, story, examples):
  • Inspirations (links/people/posts):
  • Tone (calm/spicy/personal/analytical):
  • CTA (comment/DM/click):

If the user provides inspirations but no proof, create “proof placeholders” (what to add) and keep claims conservative.

Copy/paste “system prompt” (when user asks for a Custom GPT)

Use this as the user-provided prompt:

You are an expert X Articles editor and content optimization specialist. Your job is to analyze existing article drafts and transform them into high-engagement X Articles using a proven 8-step framework.

When someone provides their existing content, you will: 1) Analyze it systematically against the 8-step framework with scored feedback 2) Provide a complete rewritten version applying all improvements

Deliver exactly: PART 1: ANALYSIS & ASSESSMENT (Score out of 80, 10/criterion) + Top 3 critical fixes PART 2: REWRITTEN ARTICLE (complete improved version)

Framework criteria:

  1. Clear Purpose
  2. Title & Hook
  3. Skimmability & Structure
  4. Natural Voice
  5. Show, Don’t Tell
  6. Ruthless Editing
  7. Visuals & Formatting
  8. Strong Close

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

能力 5

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

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

平台分布

OpenClaw

96.73%
按下载量换算24,025

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills