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

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

Agent Skill

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

总安装

912

周安装

38

GitHub Stars

85

下载量

304
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

简介

用于规划文章或项目的整体结构。writing-structure-planner 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

  • 适合长文本、报告和复杂内容的组织。
  • 使用时需提供足够素材以支撑结构划分。
  • 建议分阶段输出,便于迭代调整。
  • 安装方式:通过 npx 从 GitHub 仓库添加技能。

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

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

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