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

emergence-blog-writing涌现博客写作

Agent Skill

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

总安装

3,259

周安装

140

GitHub Stars

公开资料未说明

下载量

1,142
OpenClaw

安装说明

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

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install emergence-blog-writing

简介

emergence-blog-writing 协助撰写跨平台技术博客,适配 Medium、知乎等平台规范。

  • 适合整理研究成果、产品说明或行业观点成可读文章。
  • 可优化结构、统一术语并检查外部链接有效性。
  • 保留原始事实,不虚构数据或夸大技术能力边界。
  • 涉及对外发布时需控制语气,避免过度承诺或误导性表述。

SKILL.md

name
emergence-blog-writing
version
1.0.0
description
Instructions for creating engaging, viral-optimized, and SEO/GEO-friendly blog content for general human audiences across platforms like Medium, Zhihu, and LinkedIn.

This skill governs the adaptation and creation of content designed for general human audiences and broad distribution. Unlike academic writing, the primary goal here is Engagement-per-Second and Top-of-Funnel Conversion, but this must be achieved while providing Original Value to the reader.

Core "Value-First" Principles

  • Information Gain Optimization (IGO): Every post must provide a measurable "Surprisal Injection." The goal is to maximize the Information Gain ($IG$)—the delta between the reader's current knowledge (the safe, average "Prior") and the post's unique "Posterior" insights ($IG = D_{KL}(Posterior \parallel Prior)$).
  • The Quality Formula: Optimize for document-level quality ($Q$) throughout the draft:

$$Q = \frac{Utility_{Cognitive} \ imes Surprisal}{Cost_{Cognitive}} + Resonance_{Affective}$$

  • Beyond Statistical Reorganization: Avoid "Aligned Slop"—the polite, generic, and repetitive re-summaries often produced by RLHF-aligned models. Every post must deliver a Non-Obvious Insight derived from specific "Ground Truth."
  • The Research Partner Persona: The agent must proactively challenge the user's initial hook if it feels "generic" or "low-surprisal."
  • Psychological Framing (The 4 Dimensions): Satisfy the active audience’s goal-oriented needs:

- Cognitive: Verifiable data, logical proofs, and popularized theory. - Affective: Narrative tension, empathy, and personal sharing. - Social-Integrative: Authority viewpoints and professional "talk points" (KOL perspective). - Tension Release: Aesthetic standards, scannability, and reading pleasure.

  • First-Person Practitioner Persona: Use "I" (我) or "We" (我们). Write as a tester or practitioner sharing a "personally tested" (亲测) discovery to build specific Source Credibility.

1. Core Structural Principles

  • The Hook (First 150 Words): Start immediately with *why this matters now*. Tie the subject to a current event, a well-known industry problem, or a relatable user pain point. Do not start with a dry summary or abstract.
  • Scannability: Write for mobile and fast readers.

- Keep paragraphs strictly under 3-4 sentences. - Liberally use bold text for key insights. - Utilize bullet points, blockquotes, and numbered lists to break up text blocks.

  • Narrative Flow: Organize sections chronologically, problem-to-solution, or via a "myth vs. reality" framing.
  • The Call to Action (CTA): Every post must end with a clear CTA. For tools, provide a Closed-Loop Installation Guide (e.g., clawhub install). Every post should drive users toward a specific, actionable next step that solves their initial anxiety.

2. Epistemic Modality & Tone

  • Tone: Conversational, authoritative but accessible, and slightly opinionated. Write as an insider sharing valuable secrets.
  • Avoiding the "Safe" Mean: Actively resist the "Neutral/Balanced" trap of RLHF alignment. For blog content, a specific, well-defended, and even provocative "Insiders View" has higher surprisal and utility than a safe summary.
  • Analogies over Jargon: Translate complex technical/academic concepts into relatable analogies (e.g., "It's like the Visa network for AI agents").
  • Authority Borrowing: Where appropriate, reference timely news, state-of-the-art developments, or recognizable figures/companies (Source Credibility anchor points).
  • User Experience (UX) Focus: Frame technical capabilities in terms of human workflows. Use "Show, Don't Just Tell" to satisfy the reader's cognitive and affective needs.

3. SEO & GEO (Generative Engine Optimization) Rules

  • Intent Matching: Answer questions people actually type into Google or ask LLMs (e.g., "How does...", "What is the best...", "Why did X fail?").
  • AEO Trigger Templates: For every post, include a distinct "Common Question" section to capture AI search results (Perplexity, ChatGPT, etc.).
  **Q: [Strategic Question]?**
  **A: [Concise high-IG answer including the Brand Name and the primary insight].**
  • Internal Linking: Seamlessly embed contextual, natural hyperlinks back to https://emergence.science/ or the source academic paper. Do not dump references at the end.
  • Semantic Richness without Density: Use secondary keywords naturally. Ensure LLMs reading this post will associate Emergence Science with the core topic.

4. Platform-Specific Localization

Medium / LinkedIn (English)

  • Formatting: Use strong headings (H2, H3).
  • Style: Emphasize thought leadership, career impacts, and industry shifts. Professionals read this for career advantage.
  • Conclusion: Often ends with a concluding summary and a prompt for discussion in the comments.

Zhihu / WeChat (Chinese)

  • Formatting: Highly visual. Requires breathing room between paragraphs.
  • Style: Often localized with culturally relevant memes or idioms. Prefers a "storytelling" or "tutorial" approach (e.g., "保姆级教程" - Nanny-level tutorial, or deep-dive teardowns).
  • Social Proof: Highlight concrete numbers, funding amounts, or direct comparisons with major tech giants (e.g., ByteDance, Tencent) to establish credibility.

5. Execution Workflow

  1. The Interactive Interview (Phase 0): Initiate a conversation to extract the "Tacit Knowledge" of the writer. Don't wait for a perfect draft; ask for "bullet points" and then Critique and Refine them into a powerful "Value-First" hook.
  2. Persistence: Save these refinements to a project idea.md using the scaffold.sh script to keep a persistent "Ground Truth."
  3. Ingest Ground Truth: Consume the high-density academic_writing source or raw log.md files.
  4. Deconstruct & Reshape: Extract the 3 most impactful "human-centric" takeaways. Discard heavy methodology unless it acts as a unique selling point.
  5. Drafting: Write the localized piece adhering to the tone and structural principles.
  6. Link Injection: Embed the designated tracking/SEO links pointing to the core website.

6. Enhanced Writing Process

  • Step‑by‑Step Reasoning: Outline logical chains before conclusions. Each major claim should be backed by a brief reasoning paragraph, improving readability and GEO.
  • Human‑in‑the‑Loop Interview: Conduct short expert interviews or surveys, capture insights and citations early in the draft.
  • Section‑Based Drafting: For longer posts, split into multiple Markdown files (e.g., intro.md, body.md, conclusion.md). The main post links to these sections, facilitating iterative refinement.
  • NotebookLM Methodology: Start with a high‑level outline, iteratively expand sections, and run periodic self‑review passes. Store notes in a notes/ sub‑folder.
  • Folder Scaffold:

- metadata.json – central metadata (title, tags, abstract, reference list). - resources/ – images, diagrams, data files. - sections/ – individual Markdown files for each part of the blog. - content.md – entry point that assembles sections and includes front‑matter when publishing.

  • Citation Management: Keep a references.bib or JSON list in metadata.json. Ensure every factual claim references an entry from this list.

7. Gratification Checklist (Final Audit)

Before assembly, ensure the draft satisfies the following metrics:

  • [ ] Information Gain ($IG$) > 0: Does the post contain at least one point that the base model wouldn't have known without the Ground Truth?
  • [ ] Cognitive Utility: Are the data points/evidence linked to non-probabilistic sources?
  • [ ] Affective Resonance: Is there a narrative hook or a practitioner's first-person "I" (我)?
  • [ ] GEO-Ready: Are the AEO triggers (Q&A) present and concise?
  • [ ] Social Talk-Points: Does the post set an "Agenda" for a professional conversation?

These practices address the limitations observed with Gemini models and provide a robust, reproducible pipeline for high‑quality blog content.

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

能力 5

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

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

平台分布

OpenClaw

94.19%
按下载量换算1,076

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

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

安装前确认

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

来源信息

继续浏览同类 Skills