Report Outline
v1.0.0在有了研究大纲后使用。将研究大纲转化为详细的报告结构和执行计划，明确每个章节的内容、数据来源、分析方法。
⭐ 0· 76·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description match the SKILL.md: it transforms a research outline into a report structure and execution plan. It requests no binaries, credentials, or config paths — all proportional to an instruction-only outlining tool.
Instruction Scope
Instructions stay focused on report structure, chapter-level breakdown, dependencies, and checks. The SKILL.md asks the agent to 'save the report structure' with a filename pattern and to announce when the skill is used; these are reasonable but implementation-dependent (the agent runtime will determine where the file is written). It references a separate 'research skill' for splitting multi-topic outlines — composition is expected but means full behavior depends on other skills present. The instructions do not ask to read arbitrary system files, access environment variables, or transmit data to external endpoints.
Install Mechanism
No install spec (instruction-only). Nothing is downloaded or written to disk by the skill itself beyond the expectation that the agent may save an output file; this is low-risk.
Credentials
No environment variables, credentials, or config paths are requested. The skill does not ask for secrets or unrelated service tokens.
Persistence & Privilege
always is false and the skill does not request persistent elevation or alter other skills' configurations. Autonomous invocation is allowed by platform default but the skill itself does not request extra privileges.
Assessment
This skill appears coherent and low-risk: it contains only instructions for producing a detailed report plan and requests no credentials or installs. Before installing/using, consider: 1) Confirm where the agent will save the generated file (the SKILL.md asks to 'save to an appropriate location' but doesn't specify a path or storage policy). Make sure that destination is acceptable and access-controlled. 2) If your agent composes this with a separate 'research skill', verify that skill's permissions and behavior. 3) Review outputs for accidental inclusion of sensitive data from your prompt or environment before distributing. 4) If you enable autonomous agent runs, remember that the skill may cause the agent to spawn follow-up tasks (e.g., parallel research agents) — review those agents' scopes. If you want a stricter assessment, provide the agent runtime's save-path behavior and any linked 'research' skill definitions; with that I can reassess any additional risks.Like a lobster shell, security has layers — review code before you run it.
latestvk975e3mw8gwrjm1cs87vqa1c0n83prvr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.