Token导航 LogoToken导航

Agent Skill · 研究检索

writing-structure-planner(写作结构规划师)

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

writing-structure-planner 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 44,490。

总安装 912周安装 38GitHub Stars 85下载 304核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:writing-structure-planner(写作结构规划师)
来源仓库:https://github.com/lyndonkl/claude
仓库路径:skills/writing-structure-planner
安装命令:
npx skills add https://github.com/lyndonkl/claude --skill writing-structure-planner
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/lyndonkl/claude --skill writing-structure-planner

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于规划文章或项目的整体结构。writing-structure-planner 属于研究检索类 Skill,可作为该场景下的辅助能力补充。适合长文本、报告和复杂内容的组织。使用时需提供足够素材以支撑结构划分。建议分阶段输出,便于迭代调整。安装方式:通过 npx 从 GitHub 仓库添加技能。

来源仓库内路径:skills/writing-structure-planner

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/lyndonkl/claude --skill writing-structure-plan…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

writing-structure-planner 怎么安装?

在终端执行 npx skills add https://github.com/lyndonkl/claude --skill writing-structure-planner。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

writing-structure-planner 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

writing-structure-planner 需要什么权限?

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

writing-structure-planner 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

writing-structure-planner 用的人多吗?

公开数据是累计安装 912 次,近一周安装 38 次,下载 304 次,GitHub 85 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

writing-structure-planner 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
writing-structure-planner

写作结构规划师 · 本页

91285只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Writing Structure Planner

Table of Contents

Related skills: Use writing-revision for revising existing prose, writing-stickiness for memorable messaging, writing-pre-publish-checklist for final quality checks.

Core Principles

  1. Structure arises from material: Don't impose a structure - let the content suggest its natural organization
  2. Blueprint before building: Always plan structure before drafting
  3. Invisible architecture: Good structure is invisible to readers - they just experience flow
  4. Three options minimum: Always sketch at least 3 structural options before choosing
  5. Gold-coin distribution: Place reader rewards throughout, especially in the middle

Workflow

Copy this checklist and track your progress:

Structure Planning:
- [ ] Step 1: Analyze material thoroughly
- [ ] Step 2: Explore structure options
- [ ] Step 3: Select and refine structure

Before starting: Review resources/structure-types.md for the 8 structure types, diagramming method, and selection criteria.

For analysis steps, output findings to analysis files in the current directory to ensure thorough coverage of all material. These analysis files remain in the project for your review.

Step 1: Analyze material thoroughly

Step 1.1: Gather and understand all material completely. Read everything the user has provided.

Step 1.2: Create analysis file writer-structure-material-analysis.md and output: all key points, anecdotes, data, quotes, and examples found in the material. Identify themes and patterns. Determine what's most important vs. supporting detail. Identify the natural organizing principle (time, space, importance, comparison). Note reader considerations (busy? engaged? unfamiliar? expert?).

Step 1.3: Present the material analysis to the user and confirm understanding is complete. Ask: "Did I miss any important material or themes?"

See resources/structure-types.md - Gather Your Material for detailed guidance.

Step 2: Explore structure options

Step 2.1: Read the analysis file. Review all 8 Structure Types with examples.

Step 2.2: Create analysis file writer-structure-options.md and sketch 3 different structure options. For each option include: structure type name, diagram sketch, how user's material maps to it, pros and cons.

Step 2.3: Test each option against Structure Selection Criteria. Present all 3 options to the user with your recommendation.

See resources/structure-types.md - Sketch 3 Options for detailed process.

Step 3: Select and refine structure

Step 3.1: Read the options file. Based on user's choice (or your recommendation if they defer), select the structure that best serves the material.

Step 3.2: Create the final annotated structure diagram. Map key moments and transitions. Identify where to place gold-coin moments throughout (especially middle sections). Annotate with pacing and transition notes.

Step 3.3: Verify structure supports the through-line (promise -> delivery -> resonance). Test: Does this feel inevitable or forced? Present final annotated structure diagram for user review before drafting.

See resources/structure-types.md - Select and Refine for detailed guidance.

How to know if structure is working:

If working: Readers won't notice it, they'll just experience flow and feel the piece is "well-organized."

If not working: Readers will feel lost, wonder "where is this going?", or abandon before the end.

Validate using resources/evaluators/rubric_structure.json. Minimum standard: Average score >= 3.5.

Structure Types Overview

The 8 structure types available (see resources/structure-types.md for full details):

TypeBest For
ListMultiple independent points, how-to guides
ChronologicalNarratives, historical accounts, processes
Circular/CyclicalHooking readers with drama, then providing context
Dual ProfileCharacter profiles, examining topic from multiple angles
Triple ProfileComplex characters in multiple contexts
Pyramid (Inverted)News, executive summaries, busy readers
Parallel NarrativesComparing/contrasting, multi-threaded stories
Custom DiagramsUnique material that doesn't fit standard types

Guardrails

Requirements:

  1. Material-first: Always understand the material before suggesting structure. Never impose a structure without understanding content.
  2. Three options: Always generate at least 3 structural options. The second or third is often best.
  3. User collaboration: Present options and let the user choose. Don't dictate structure.
  4. Gold-coin placement: Every structure must include strategic placement of reader rewards, especially in the middle.
  5. Test the structure: Ask "does this feel inevitable or forced?" before finalizing.

Common pitfalls:

  • Defaulting to chronological when another structure serves better
  • Front-loading all strong material in the opening
  • Ignoring the "saggy middle" problem
  • Imposing structure without understanding material
  • Skipping the 3-option comparison step

Quick Reference

Key resources:

Inputs required:

  • User's material, ideas, or topic description
  • Target audience (if known)
  • Any constraints (length, format, publication)

Outputs produced:

  • Material analysis document
  • 3 structure options with pros/cons
  • Final annotated structure diagram with gold-coin placement
  • Recommended writing order

平台分布

Codex

36.77%
按下载量换算112

Claude

27.44%
按下载量换算83

Cursor

20.31%
按下载量换算62

Gemini CLI

9.31%
按下载量换算28

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills