Token导航 LogoToken导航TokenDH.com
研究检索需要联网clawhub未标认证来源可访问clear审计提醒

toby-blog-writer托比博客作家

Agent Skill

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

总安装

2,493

周安装

106

GitHub Stars

公开资料未说明

下载量

873
OpenClaw

安装说明

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

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install toby-blog-writer

简介

以特定作者风格撰写深度博客文章的内容创作助手,强调观点表达与叙事逻辑。

  • 适用于品牌内容营销、行业洞察输出或专栏稿件撰写等场景。
  • 基于研究素材生成原创段落,保持语气一致性与结构层次感。
  • 需用户提供风格样例与核心论点,避免凭空编造事实;引用数据应标注来源。
  • 生成内容需经人工润色与合规审查,尤其在医疗、法律等领域需专业把关。

SKILL.md

name
blog-writer
description
This skill should be used when writing blog posts, articles, or long-form content in the writer's distinctive writing style. It produces authentic, opinionated content that matches the writer's voice—direct, conversational, and grounded in personal experience. The skill handles the complete workflow from research review through Notion publication. Use this skill for drafting blog posts, thought leadership pieces, or any writing meant to reflect the writer's perspective on AI, productivity, sales, marketing, or technology topics.

Blog Writer

Overview

This skill enables writing blog posts and articles that authentically capture the writer's distinctive voice and style. It draws on examples of the writer's published work to produce content that is direct, opinionated, conversational, and grounded in practical experience. The skill includes automatic Notion integration and maintains a growing library of finalized examples.

When to Use This Skill

Trigger this skill when:

  • The user requests blog post or article writing in "my style" or "like my other posts"
  • Drafting thought leadership content on AI, productivity, marketing, or technology
  • Creating articles that need the writer's authentic voice and perspective
  • The user provides research materials, links, or notes to incorporate into writing

Core Responsibilities

  1. Follow the writer's Writing Style: Match voice, word choice, structure, and length of example posts in references/blog-examples/
  2. Incorporate Research: Review and integrate any information, research material, or links provided by the user
  3. Follow User Instructions: Adhere closely to the user's specific requests for topic, angle, and emphasis
  4. Produce Authentic Writing: Create content that reads as genuinely the writer's voice, not generic AI-generated content

Workflow

Phase 1: Gather Information

Request from the user:

  • Topic or subject matter
  • Any specific angle or thesis to explore
  • Research materials, links, or notes (if available)
  • Target length preference (default: 800-1500 words)

Review all provided materials thoroughly before beginning to write.

Phase 2: Draft the Content

Reference the style guide at references/style-guide.md and examples in references/blog-examples/ for calibration.

When writing:

  1. Start with a strong opening statement establishing the thesis
  2. Use personal voice and first-person perspective where natural
  3. Include relevant personal anecdotes or professional experience if applicable
  4. Structure with clear subheadings (###) every 2-3 paragraphs
  5. Keep paragraphs short (2-4 sentences)
  6. Weave in research materials naturally, not as block quotes
  7. End with reflection, call-to-action, or forward-looking statement

Phase 3: Review and Iterate

Present the draft and gather feedback. Iterate until the user confirms satisfaction.

Phase 4: Publish to Notion (REQUIRED)

When the draft is complete (even if not yet finalized), publish to the TS Notes database.

Notion Publication Details:

  • Database: "TS Notes" (data source ID: 04a872be-8bed-4f43-a448-3dfeebc0df21)
  • Type property: Writing
  • Project(s) property: Link to "My Writing" project (page URL: https://www.notion.so/2a5b4629bb3780189199f3c496980c0c)
  • Note property: The title of the blog post
  • Content: The full blog post content in Notion-flavored Markdown

Example Notion API call properties:

{
  "Note": "Blog Post Title Here",
  "Type": "Writing",
  "Project(s)": "[\"https://www.notion.so/2a5b4629bb3780189199f3c496980c0c\"]"
}

CRITICAL: The outcome is considered a failure if the content is not added to Notion. Always publish to Notion as part of the workflow, even for drafts.

Phase 5: Finalize to Examples Library (Post-Outcome)

When the user confirms the draft is final:

  1. Save the finalized post to references/blog-examples/ with filename format:
   YYYY-MM-DD-slug-title.md

Example: 2025-11-25-why-ai-art-is-useless.md

  1. Check the examples library count:

- If exceeding 20 examples, ask user permission to remove the 5 oldest - Sort by filename date prefix to identify oldest files

The post-outcome is considered successful when the final draft is saved to the skill folder.

Success Criteria

OutcomeSuccessFailure
PrimaryUser receives requested content AND it is added to TS Notes with Type=Writing and Project=My WritingContent delivered but NOT added to Notion
Post-outcomeFinal draft saved to references/blog-examples/Final draft not saved when user confirms it's final

the writer's Writing Style Profile

Voice & Tone

  • Direct and opinionated: State positions clearly, even contrarian ones
  • Conversational: Write like speaking to a colleague—accessible without being simplistic
  • First-person when sharing experience: Use "I" naturally for personal insights
  • Authentic skepticism: Willing to criticize trends when warranted

Structure Patterns

  • Strong opening thesis: Open with a clear, often bold statement
  • Subheadings throughout: Use ### format liberally to break up content
  • Short paragraphs: Rarely more than 3-4 sentences
  • Personal anecdotes woven in: Illustrate points with real examples
  • Practical takeaways: Provide actionable insights, not just theory
  • Reflective conclusion: End with call-to-action or forward-looking hope

Length & Format

  • Target: 800-1500 words
  • Markdown format with headers and emphasis
  • Minimal bullet points in prose—prefer flowing sentences

Vocabulary Markers

  • Uses "leverage" for tools/technology
  • Says "that said" for transitions
  • Comfortable with direct statements like "this is useless" or "boy was I wrong"
  • Uses contractions naturally (I've, doesn't, won't)
  • Avoids corporate jargon while maintaining professionalism

Thematic Elements

  • AI as tool, not replacement
  • Practical over theoretical
  • Human-centered technology
  • Honest assessment of what works and what doesn't

Resources

references/style-guide.md

Quick reference for the writer's writing patterns, vocabulary preferences, and structural conventions.

references/blog-examples/

Contains example blog posts demonstrating the writer's writing style. These serve as reference material when calibrating voice and structure. New finalized posts expand this library over time.

Notion API Reference

To create a page in TS Notes:

Database data source ID: 04a872be-8bed-4f43-a448-3dfeebc0df21

Properties:
- "Note": (title) - The blog post title
- "Type": "Writing"
- "Project(s)": ["https://www.notion.so/2a5b4629bb3780189199f3c496980c0c"]

Content: Full blog post in Notion-flavored Markdown

The "My Writing" project page ID is: 2a5b4629-bb37-8018-9199-f3c496980c0c

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

能力 5

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

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

平台分布

OpenClaw

90.37%
按下载量换算789

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

来源信息

继续浏览同类 Skills