Token导航 LogoToken导航TokenDH.com
研究检索操作浏览器clawhub未标认证来源可访问clear审计通过

re-blog-writer重新博客作家

Agent Skill

re-blog-writer 用于处理浏览器自动化、网页检查和页面信息提取,适合在 OpenClaw 中需要让 Agent 打开页面、读取网页或验证前端流程时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

6,291

周安装

257

GitHub Stars

公开资料未说明

下载量

2,035
OpenClaw

安装说明

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

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install re-blog-writer

简介

自动化浏览器研究主题并撰写完整博客文章,保存为 Markdown 文件至 ~/blogs。

  • 适合在 OpenClaw 中快速产出带背景调研的内容,支持嗡嗡声风格写作。
  • 集成网页抓取与信息提取,辅助生成结构清晰的文章初稿。
  • 使用前需确保浏览器环境可用,并注意遵守目标网站爬取政策。
  • 建议检查输出文件路径权限及最终内容是否符合版权与事实准确性要求。

SKILL.md

name
blog-writer
description
Research a topic using the browser then write a complete blog post saved as a .md file in ~/blogs. Use when the user provides a subject and wants a full, human-sounding blog post researched from Google, Reddit, and other sources, written in a specific casual-direct style with a 5-part structure, no clichés, no em dashes, and a target of 1200-1500 words.

Blog Writer

Use this skill to research and write one complete blog post per run. It assumes browser access for research and writes the final post to ~/blogs/<slug>.md.

If the user did not provide a subject, ask for one before proceeding.

Inputs to infer

  • SUBJECT: the topic or angle to write about
  • Optional: specific angle, contrarian take, or audience focus
  • Optional: any sources the user already has

Workflow

  1. Run openclaw browser start to open the openclaw managed browser. CRITICAL NON-NEGOTIABLE: always use this command. Never open a browser any other way.
  2. Research the subject thoroughly using that same browser window before writing a single word.

- Search Google, Reddit, and Hacker News directly in that browser window. - Do not close the browser between research and writing. - Read references/research.md for the exact search order and what to collect.

  1. Take notes offline. Pull concrete facts, reactions, one surprising detail, one honest critique.
  2. Write the blog post following the 5-part structure exactly.

- Read references/structure.md for every part's requirements. - Read references/writing-style.md for style rules. Every rule applies to every sentence.

  1. Run the self-editing checklist in references/writing-style.md before saving.
  2. Save the final post to ~/blogs/<subject-slug>.md.

- Use a lowercase hyphenated slug. Example: vector-databases.md. - Create the ~/blogs/ directory if it does not exist. - CRITICAL NON-NEGOTIABLE: do NOT include an # H1 title at the top of the file. The post starts directly with the first sentence of Part 1. Title metadata is handled separately by the re-blog-meta skill.

  1. Close all browser tabs opened during research.

Quality bar

  • CRITICAL NON-NEGOTIABLE: do NOT add an # H1 title at the top of the post. Start the file directly with the first sentence of Part 1. Title is handled by the re-blog-meta skill.
  • CRITICAL NON-NEGOTIABLE: target 1200-1500 words. If short, add a mini-story. If long, cut any paragraph that feels like a list.
  • CRITICAL NON-NEGOTIABLE: no em dashes anywhere in the post.
  • CRITICAL NON-NEGOTIABLE: no clichés. See the banned words list in writing-style.md.
  • CRITICAL NON-NEGOTIABLE: never start with a day or time reference like "last Sunday," "today morning," or "this week."
  • CRITICAL NON-NEGOTIABLE: start Part 1 with a real-world example, fact, or documented reaction found during research.
  • CRITICAL NON-NEGOTIABLE: apply every writing style rule without exception. Do not relax any rule unless the user explicitly asks.

Completion report

At the end, report:

  • Subject covered
  • File saved to
  • Word count
  • Sources used during research
  • Confirmation that all browser tabs are closed

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

能力 5

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

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

平台分布

OpenClaw

87.72%
按下载量换算1,785

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

操作浏览器

该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

安装前确认

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

来源信息

继续浏览同类 Skills