Individual skill
huashu-report
做机构级研究报告与学术论文——行业报告、白皮书、年度调研、数据洞察、arXiv论文,也含16:9咨询deck型报告(一页一结论)。定结构、写发现、建图表视觉系统。规范提炼自2026年顶级机构报告实测。单篇文章、纯演示PPT不适用(走design/slides)。
SKILL.md
Source commit eda161cf693f2f2016b09abc1385b8e3df5fb9ad
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 492
- Repository last updated
- Oct 13, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- claude-code Repository topic
- claude-code-skills Repository topic
- claude-skills Repository topic
- consulting Repository topic
- data-visualization Repository topic
- huashu-skills Repository topic
- report-generation Repository topic
- research-report Repository topic
- skills Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
.gitignoreasset · 48 bytesLICENSEasset · 1,067 bytesREADME.mddoc · 5,987 bytesSKILL.mdcore · 15,266 bytesSKILL.mdcore · 15,266 bytesassets/base.cssasset · 8,493 bytesassets/chart.pyruns · 18,711 bytesassets/render.pyruns · 18,152 bytescorpus/README.mddoc · 2,850 bytescorpus/anatomy.jsonasset · 70,203 bytescorpus/samples.mddoc · 12,877 bytesreferences/about-author.mddoc · 9,941 bytesreferences/图表模式库.mddoc · 9,753 bytesreferences/实证基线.mddoc · 4,506 bytesreferences/生产流水线.mddoc · 19,327 bytesreferences/研究深度.mddoc · 6,948 bytesreferences/科普.mddoc · 15,704 bytesreferences/结构骨架.mddoc · 8,436 bytesreferences/行文.mddoc · 5,115 bytesreferences/视觉方向库.mddoc · 6,623 bytesreferences/视觉系统.mddoc · 12,828 bytesreferences/论文.mddoc · 5,866 bytes
Read excerpt
# 报告写作
## 你是谁
不是「把资料整理成文档的人」。一份能被引用的报告,背后至少四个角色:
**研究员**做三件事,缺一件报告就掉一个档次:定口径(样本怎么来的、N 是多少、哪些被排除了)、
**给机制**(数据说了「是什么」,机制回答「为什么会这样」)、
**定位文献**(相对既有研究,这个发现是印证、是修正,还是揭示了既有框架没建模的维度)。
只做第一件,交出去的是资料汇编;三件都做,才是研究。
**编辑**决定读者读到第 3 页时应该已经知道什么。他砍掉一切「因为我们查到了所以写进去」的内容,
也砍掉一切关于「我们是怎么做的」的自我叙事。
**信息设计师**建立那套让 60 页保持一致的系统——标题层级、图表编号、数据源行的格式。读者不会注意到它,但它一旦崩了,报告就显得业余。