Structured Data
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing metadata, crawlability, structured data, or indexability related to Add structured data markup.
诊断一篇长文/文章/报告的结构性问题——论点承诺是否兑现、论证链条是否完整、 段落功能是否清楚、节奏是否合理，给出按影响力排序的修改建议。Use when 用户说"帮我看看这篇文章逻辑通不通""这篇文章结构上有什么问题""从整体上 诊断一下这篇稿子""哪里需要重新组织"。这是诊断，不是逐句改写——如果用户 要的是具体段落润色，用 line-polish；要多角度读者反馈用…
Apache-2.0Auto-check passed
Install Structural Diagnosis
$ npx skills add open-octo/octo-agent --skill structural-diagnosis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install open-octo/octo-agent structural-diagnosis --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/open-octo/octo-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/internal/skills/experts/structural-diagnosis .claude/skills/structural-diagnosis && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "structural-diagnosis" agent skill from https://github.com/open-octo/octo-agent/tree/main/internal/skills/experts/structural-diagnosis into .claude/skills/structural-diagnosis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "structural-diagnosis", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/open-octo/octo-agent/tree/main/internal/skills/experts/structural-diagnosisType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add open-octo/octo-agent --skill structural-diagnosis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install open-octo/octo-agent structural-diagnosis --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/open-octo/octo-agent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/internal/skills/experts/structural-diagnosis .agents/skills/structural-diagnosis && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "structural-diagnosis" agent skill from https://github.com/open-octo/octo-agent/tree/main/internal/skills/experts/structural-diagnosis into .agents/skills/structural-diagnosis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "structural-diagnosis", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add open-octo/octo-agent --skill structural-diagnosis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install open-octo/octo-agent structural-diagnosis --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/open-octo/octo-agent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/internal/skills/experts/structural-diagnosis .cursor/skills/structural-diagnosis && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "structural-diagnosis" agent skill from https://github.com/open-octo/octo-agent/tree/main/internal/skills/experts/structural-diagnosis into .cursor/skills/structural-diagnosis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "structural-diagnosis", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/open-octo/octo-agent.git --path internal/skills/experts/structural-diagnosis--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add open-octo/octo-agent --skill structural-diagnosis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install open-octo/octo-agent structural-diagnosis --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/open-octo/octo-agent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/internal/skills/experts/structural-diagnosis .gemini/skills/structural-diagnosis && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "structural-diagnosis" agent skill from https://github.com/open-octo/octo-agent/tree/main/internal/skills/experts/structural-diagnosis into .gemini/skills/structural-diagnosis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "structural-diagnosis", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install open-octo/octo-agent structural-diagnosisInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add open-octo/octo-agent --skill structural-diagnosis -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/open-octo/octo-agent.git skills-src && mkdir -p .github/skills && cp -r skills-src/internal/skills/experts/structural-diagnosis .github/skills/structural-diagnosis && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "structural-diagnosis" agent skill from https://github.com/open-octo/octo-agent/tree/main/internal/skills/experts/structural-diagnosis into .github/skills/structural-diagnosis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "structural-diagnosis", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add open-octo/octo-agent --skill structural-diagnosis -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install open-octo/octo-agent structural-diagnosis --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/open-octo/octo-agent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/internal/skills/experts/structural-diagnosis .opencode/skills/structural-diagnosis && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "structural-diagnosis" agent skill from https://github.com/open-octo/octo-agent/tree/main/internal/skills/experts/structural-diagnosis into .opencode/skills/structural-diagnosis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "structural-diagnosis", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
structural-diagnosis- GitHub stars
- 125
- Token cost
- ~880 tokens
- SKILL.md length
- 106 words
- Files
- 3
- Skills in repo
- 40
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
诊断一篇长文/文章/报告的结构性问题——论点承诺是否兑现、论证链条是否完整、 段落功能是否清楚、节奏是否合理，给出按影响力排序的修改建议。Use when 用户说"帮我看看这篇文章逻辑通不通""这篇文章结构上有什么问题""从整体上 诊断一下这篇稿子""哪里需要重新组织"。这是诊断，不是逐句改写——如果用户 要的是具体段落润色，用 line-polish；要多角度读者反馈用…
- Works in 5 steps: 读者承诺：开头几段/引言给读者立下了什么期待——要解决什么问题、 → 论证结构：核心论点、论据之间的因果关系、节奏、每个部分/段落的 → 语气与文风：视角是否稳定、语气是否统一、是否有这篇稿子该有的 → …
- 用户说帮我看看这篇文章逻辑通不通这篇文章结构上有什么问题从整体上 诊断一下这篇稿子哪里需要重新组织。这是诊断，不是逐句改写——如果用户 要的是具体段落润色，用 line-polish；要多角度读者反馈用 reader-simulation
- SKILL.md covers 怎么读, 关注顺序, 先分清：结构问题 vs 执行问题 and 诊断维度, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Structural Diagnosis is an agent skill from open-octo/octo-agent. 诊断一篇长文/文章/报告的结构性问题——论点承诺是否兑现、论证链条是否完整、 段落功能是否清楚、节奏是否合理，给出按影响力排序的修改建议。Use when 用户说"帮我看看这篇文章逻辑通不通""这篇文章结构上有什么问题""从整体上 诊断一下这篇稿子""哪里需要重新组织"。这是诊断，不是逐句改写——如果用户 要的是具体段落润色，用 line-polish；要多角度读者反馈用 reader-simulation。
Its SKILL.md is about 880 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `PROVENANCE.md`).
The repository describes itself as: Open-source, single-binary, self-hosted AI agent — your models and data stay on your machine. A coding agent on par with Claude Code and a personal assistant lighter than… The licence is Apache-2.0.
When your agent uses it
- 用户说帮我看看这篇文章逻辑通不通这篇文章结构上有什么问题从整体上 诊断一下这篇稿子哪里需要重新组织。这是诊断，不是逐句改写——如果用户 要的是具体段落润色，用 line-polish；要多角度读者反馈用 reader-simulation
Example prompts
- “帮我看看这篇文章逻辑通不通”
- “这篇文章结构上有什么问题”
- “从整体上 诊断一下这篇稿子”
- “/structural-diagnosis”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- 读者承诺：开头几段/引言给读者立下了什么期待——要解决什么问题、
- 论证结构：核心论点、论据之间的因果关系、节奏、每个部分/段落的
- 语气与文风：视角是否稳定、语气是否统一、是否有这篇稿子该有的
- 段落层面的执行：清晰度、段落之间的推进、重复、句子结构、过度
- 表层问题：语法、标点、用词一致性、格式。这一层只标"反复出现的
What it can do on your machine
Read from SKILL.md and the folder at commit fc1385f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Structural Diagnosis loads about 880 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 106 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from open-octo/octo-agent at commit fc1385f, republished under its Apache-2.0 licence (© open-octo). 106 words, ~880 tokens.
Download SKILL.mdSave it as
.claude/skills/structural-diagnosis/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- structural-diagnosis
- description
- 诊断一篇长文/文章/报告的结构性问题——论点承诺是否兑现、论证链条是否完整、 段落功能是否清楚、节奏是否合理，给出按影响力排序的修改建议。Use when 用户说"帮我看看这篇文章逻辑通不通""这篇文章结构上有什么问题""从整体上 诊断一下这篇稿子""哪里需要重新组织"。这是诊断，不是逐句改写——如果用户 要的是具体段落润色，用 `line-polish`；要多角度读者反馈用 `reader-simulation`。
- license
- Apache-2.0 (adapted from haowjy/creative-writing-skills, skills/story-review/resources/editorial-review.md + developmental-edit.md; complete terms in…
- metadata.origin
- 编辑评审的"读的顺序"(承诺→结构→语气→段落→表层)、编辑备忘录结构 (总体诊断+优先级队列+具体批注+修订顺序)、"区分结构问题与执行问题"、 "保护作者原声、存疑就问不要替作者拍板、只诊断不代写"这套编辑纪律， 改编自 haowjy/creative-writing-skills 的…
Skill: structural-diagnosis
这是诊断，不是重写。目标是告诉用户"这篇稿子需要哪种修改，先改哪里"，不是 把稿子按自己的风格重写一遍。
怎么读
先通读全文再下笔写任何一条意见。 第一遍读的是"读起来的感受"：哪里 读进去了、哪里注意力开始飘、哪里读着读着突然觉得累或者绕。不要在第一遍 就开始批注——很多看起来有问题的地方，往后读会发现是有意为之；很多真正的 问题，只有读完全文回头看才能看出来。
第二遍带着诊断的眼光读。这时候已经知道这篇稿子想做什么，问题变成了： 哪里做到了，哪里没做到。
关注顺序
按这个顺序读，不要跳着来（除非用户明确要求只看某一层）：
- 读者承诺：开头几段/引言给读者立下了什么期待——要解决什么问题、 给出什么视角、论证到什么结论？后面的内容有没有兑现这个承诺，还是 悄悄漂移到了别的方向？
- 论证结构：核心论点、论据之间的因果关系、节奏、每个部分/段落的 功能。这篇稿子撑得起自己的分量吗，还是结构在向读者要求太多耐心？ （对应虚构写作里"发展性编辑"关心的层面：前提、因果、节奏、场景 必要性。）
- 语气与文风：视角是否稳定、语气是否统一、是否有这篇稿子该有的 "自己的声音"，还是读起来像"正确但没有个性的通用文字"？
- 段落层面的执行：清晰度、段落之间的推进、重复、句子结构、过度 解释、该留白的地方却说破了。有没有反复出现、削弱说服力的模式？
- 表层问题：语法、标点、用词一致性、格式。这一层只标"反复出现的 模式"，不逐条列——单个错字不值得写进结构诊断报告。
除非用户明确要的是表层校对，不要一上来就挑错字。 表层问题确实重要， 但初稿失败的原因通常更大。一份结构诊断报告如果开头就是"这里少了个逗号"， 而这篇稿子的论证结构本身是断的，那是在浪费作者的注意力。
先分清：结构问题 vs 执行问题
一个段落表达的是对的意思、但表达得笨拙——这是执行问题，需要重写，不需要 删掉。一个段落表达的是不该在这里出现的意思，或者这段完全没有起到结构性 作用——这是结构问题，再怎么润色文字都解决不了。
先看能看到的最大单元：整体论证有没有兑现开头立下的承诺？然后往下看到 章节层面、段落层面。高层级的问题会连累低层级的诊断——如果整体结构是断的， 在这个基础上诊断段落层面的问题是不可靠的。
诊断维度
- 承诺与兑现：开头教会读者期待什么？后面的内容有没有对得上？
- 因果链：事件/论点之间是互相推动、互相制约的关系，还是仅仅按顺序 排列？如果段落顺序打乱了也不影响理解，说明这是"罗列"，不是"论证"。
- 段落功能：每个段落结束时，有什么发生了变化——读者的认知、态度， 或者论证向前推进了一步？如果什么都没变，这段是可以删或者合并的候选。
- 节奏：哪里推进太快、哪里拖沓、哪里持续同一强度让人麻木、哪里持续 平淡让人走神。
- 信息设计：什么被保留、什么被揭示、什么被重复、什么被解释了？读者 手里握着的问题是不是在往前拉着读，还是所有悬念都太早被解开了？
- 文体承诺：这篇稿子有没有兑现它承诺的那种阅读体验？一篇科普文章 如果从不让读者跟着推理过程走，就是没兑现科普该有的契约；一篇论辩文章 如果从不给出反方观点的正面处理，也是一样。
诊断报告结构
- 总体诊断：这份稿子需要哪种修改——不是列出所有能改进的地方，而是 找出最主要的问题。一篇需要重新组织结构的稿子，应该听到"结构需要重来"， 而不是收到五十条不会再有意义（因为结构一改这些段落可能都不在了）的 段落级意见。
- 优先级队列：影响力最大的问题排在最前面，附理由。按"对读者体验的 损耗"排序：什么最拖累阅读体验？
- 主要意见：结构性/论证效果层面的问题，每条锚定到具体段落。说清楚 问题是什么、这个问题让读者付出了什么代价、建议往哪个方向改（删、挪动、 展开、重新框定、提前埋伏笔、延后交代结论、调整论证顺序）。不是替作者 开药方，是让作者看到该往哪个方向动。
- 段落/语气层面的模式：跨段落反复出现的模式，不是逐句罗列。说清楚 模式是什么，给两三个代表性例子，说明改了能有什么收获。
- 表层问题：只标反复出现的模式，或者影响理解的地方。单个错别字不 值得写进这份报告。
- 修订顺序：现在改什么、之后再改什么、为什么这么排序。告诉作者从 哪里开始，别在需要重新组织的部分上浪费时间去抛光文字。
编辑纪律
保护作者的原声。 目标是让这篇稿子、这个作者达到它能达到的最好 样子，不是改成"我会怎么写"。当你有冲动想直接把一段改写成自己的风格时， 这个冲动几乎总是错的。指出改动的方向，把执行权留给作者。
存疑就问，不要替作者拍板。 当一个改动会影响原意、语气或读者承诺时， 用提问而不是命令的方式提出："这里是不是想表达X？因为读者可能会读成Y。" 这给作者留出确认或调整方向的空间。"把X改成Y"这种说法，等于假设你比作者 更清楚他想表达什么。
分清"风格"和"错误"。 刻意的粗粝感、非常规用词、独特的行文节奏、 有意的留白，这些不是错误。如果怀疑某处是选择而不是失误，问，不要直接 纠正。一个好的编辑要能分辨"这个作者一直都这么写"和"这个作者这里失手了"。
待在自己的位置上。 结构诊断不是重写。诊断和建议，不产出替代文字—— 除非作者明确要求进入重写阶段。编辑的工作是看到作者从稿子内部看不到的 东西，不是把稿子从作者手里拿走。
也说说做得好的地方，简短即可。 一份只罗列问题的诊断报告教不会作者 认识自己的优点。一两句指出稿子哪里做得好、为什么好，能帮作者知道修改时 该信任哪些直觉。
边界
- 不产出替代性的重写文字——除非用户明确要求进入重写/润色阶段，那时候
切到
line-polish。 - 不用单一"读者反应"代替结构诊断——如果用户要的是"读起来是什么感觉"这种
第一人称的阅读体验反馈，用
reader-simulation。 - 不在结构还没稳定的时候诊断段落级问题——先说清楚"这篇稿子需要哪种修改"， 细节问题等结构定了再看。
© open-octo, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files in internal/skills/experts/structural-diagnosis of open-octo/octo-agent.
- SKILL.md
- LICENSE.txt
- PROVENANCE.md
Open the folder on GitHubat commit fc1385f
Compare with similar skills
Structural Diagnosis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Structural Diagnosis this skillopen-octo/octo-agent | 125 | — | ~880 | Automated safety check: Pass | Apache-2.0 | |
| Structured Datathedaviddias/Front-End-Checklist | 74k | — | ~420 | Automated safety check: Pass | MIT | |
| Bio Structural Biology Modern Structure PredictionFreedomIntelligence/OpenClaw-Medical-Skills | 3.1k | 1 repos | ~2.5k | Automated safety check: Pass | None | |
| List Structurethedaviddias/Front-End-Checklist | 74k | — | ~438 | Automated safety check: Pass | MIT | |
| Bio Structural Biology Structure IoGPTomics/bioSkills | 1.2k | 1 repos | ~4k | Automated safety check: Pass | MIT | |
| Bio Structural Biology Structure NavigationGPTomics/bioSkills | 1.2k | 1 repos | ~3.7k | Automated safety check: Pass | MIT |
Similar skills
Bio Structural Biology Modern Structure Prediction
FreedomIntelligence/OpenClaw-Medical-Skills
Predict protein structures using modern ML models including AlphaFold3, ESMFold, Chai-1, and Boltz-1.
List Structure
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Use correct list structure.
Bio Structural Biology Structure Io
GPTomics/bioSkills
Reads, writes, downloads, and converts macromolecular structures with Biopython Bio.PDB.
Bio Structural Biology Structure Navigation
GPTomics/bioSkills
Navigate the Bio.PDB SMCRA hierarchy (Structure-Model-Chain-Residue-Atom) safely, surfacing the heterogeneity it hides by default.
Bio Structural Biology Structure Preparation
GPTomics/bioSkills
Prepares a deposited or predicted structure for docking, molecular dynamics, or electrostatics by adding hydrogens, assigning protonation and tautomer states, and filling missing atoms and short…
More from open-octo/octo-agent
All 40 skills in this repoImage Gen
open-octo/octo-agent
Acquire images as files — generate them with an AI image model (14 providers: OpenAI/gpt-image, Gemini, Qwen, Zhipu, Volcengine, Stability, FLUX, Ideogram, MiniMax, and more), search openly-licensed…
Office XLSX
open-octo/octo-agent
Create, read, and edit Excel (.xlsx) spreadsheets programmatically with openpyxl — cell values, formulas, styling (fonts/fills/borders/alignment/number formats), merged cells, multiple sheets…
Artifact Design
open-octo/octo-agent
Design guidance for any HTML/Markdown file shown in octo's Artifacts panel — reports, dashboards, architecture/system diagrams, generated UIs, slide-style pages, 3D scenes.
Code Review
open-octo/octo-agent
Review local code changes. An agent skill from open-octo/octo-agent.
Ppt Master
open-octo/octo-agent
AI-driven multi-format SVG content generation system. An agent skill from open-octo/octo-agent.
Config Setup
open-octo/octo-agent
Configure octo's global settings through guided conversation — set up AI model endpoints (providers, API keys, models), adjust agent defaults (reasoning effort, permission mode, coauthor, workspace…
Questions about Structural Diagnosis
What does Structural Diagnosis do?
诊断一篇长文/文章/报告的结构性问题——论点承诺是否兑现、论证链条是否完整、 段落功能是否清楚、节奏是否合理，给出按影响力排序的修改建议。Use when 用户说"帮我看看这篇文章逻辑通不通""这篇文章结构上有什么问题""从整体上 诊断一下这篇稿子""哪里需要重新组织"。这是诊断，不是逐句改写——如果用户 要的是具体段落润色，用 line-polish；要多角度读者反馈用…. Structural Diagnosis is an agent skill from open-octo/octo-agent.
When should I use Structural Diagnosis?
Structural Diagnosis fits situations like: 用户说帮我看看这篇文章逻辑通不通这篇文章结构上有什么问题从整体上 诊断一下这篇稿子哪里需要重新组织。这是诊断，不是逐句改写——如果用户 要的是具体段落润色，用 line-polish；要多角度读者反馈用 reader-simulation.
How do I install Structural Diagnosis in Claude Code?
Run `npx skills add open-octo/octo-agent --skill structural-diagnosis -a claude-code`. Or copy the skill folder (internal/skills/experts/structural-diagnosis in open-octo/octo-agent) into .claude/skills/structural-diagnosis in your project. Claude Code loads it when a task matches its description.
How do I install Structural Diagnosis in Codex?
Run `npx skills add open-octo/octo-agent --skill structural-diagnosis -a codex`. Or copy the skill folder (internal/skills/experts/structural-diagnosis in open-octo/octo-agent) into .agents/skills/structural-diagnosis in your project. Codex loads it when a task matches its description.
Can I use Structural Diagnosis in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add open-octo/octo-agent --skill structural-diagnosis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/structural-diagnosis, .gemini/skills/structural-diagnosis, .github/skills/structural-diagnosis and .opencode/skills/structural-diagnosis in your project.
What does Structural Diagnosis need to run?
SKILL.md names no scripts, command-line tools or credentials: Structural Diagnosis is instructions for the agent only.
Does Structural Diagnosis access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Structural Diagnosis safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Structural Diagnosis use?
Structural Diagnosis is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Structural Diagnosis use?
About 880 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Structural Diagnosis?
Skills that share tags, products or a category with Structural Diagnosis: Structured Data (thedaviddias/Front-End-Checklist, 74k stars), Bio Structural Biology Modern Structure Prediction (FreedomIntelligence/OpenClaw-Medical-Skills, 3.1k stars), List Structure (thedaviddias/Front-End-Checklist, 74k stars) and Bio Structural Biology Structure Io (GPTomics/bioSkills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Structural Diagnosis?
open-octo (a GitHub organization) maintains it in open-octo/octo-agent, which has 125 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on October 8, 2026.
Source: open-octo/octo-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.