nsfc-justification-writer
This tool generates scientific content for research proposals and updates LaTeX files without altering document structure.
Install
mkdir -p .claude/skills/nsfc-justification-writer && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5613" && unzip -o skill.zip -d .claude/skills/nsfc-justification-writer && rm skill.zipInstalls to .claude/skills/nsfc-justification-writer
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
当用户明确要求"写/改 NSFC 立项依据""立项依据写作/重构"时使用。基于最小信息表输出价值与必要性、现状不足、科学问题/假说与项目切入点，并保持模板结构不被破坏。适用于 NSFC 及各类科研基金申请书的立项依据写作场景。Key capabilities
- →Generate scientific justification content
- →Refactor research background text
- →Structure scientific hypotheses for grant applications
- →Perform diagnostic checks on LaTeX document structure
- →Automate section replacement with backup creation
How it works
The skill uses a structured workflow to organize research justification into four segments: value, status, hypothesis, and project contribution, while protecting the existing LaTeX document structure.
Inputs & outputs
When to use nsfc-justification-writer
- →Writing the project justification section
- →Refactoring research background text
- →Structuring scientific hypotheses for grants
- →Drafting project significance
About this skill
科研立项依据写作器
BenszAPI 任务工作区
本 Skill 的新任务中间文件统一写入 ./.bensz-api/task-{yyyymmdd-hhmm}-{简短描述}/{skill名}/input|output|log/。同一任务复用一个任务根目录；多 Skill 协作才创建 shared/。正式交付物不写入该目录，历史隐藏目录只允许显式兼容读取、迁移或清理。
与 bensz-collect-bugs 的协作约定
- 当用户环境中出现因本 skill 设计缺陷导致的 bug 时，优先使用
bensz-collect-bugs按规范记录到~/.bensz-skills/bugs/，严禁直接修改用户本地 Claude Code / Codex 中已安装的 skill 源码。 - 若 AI 仍可通过 workaround 继续完成用户任务，应先记录 bug，再继续完成当前任务。
- 当用户明确要求“report bensz skills bugs”等公开上报动作时，调用本地
gh与bensz-collect-bugs，仅上传新增 bug 到huangwb8/bensz-bugs；不要 pull / clone 整个 bug 仓库。
输出契约
- 唯一默认写入落点：
extraTex/1.1.立项依据.tex - 禁止改动：
main.tex、extraTex/@config.tex、任何.cls/.sty - 目标：把“为什么要做、现状为什么不够、科学问题是什么、项目如何切入”写清楚
- 默认写作导向是
theoretical，可在config.yaml:style.mode切为mixed或engineering
输入
- 最小信息表优先使用
references/info_form.md - 科学问题与假说口径统一看：
references/scientific_question_guidelines.mdreferences/scientific_hypothesis_guidelines.md
- 推荐用
scripts/run.py init帮用户快速生成和补全信息表
硬规则
- 只编辑
extraTex/1.1.立项依据.tex - 优先保留现有
\subsubsection骨架，只替换正文 - 不写无法核验的“国际领先/国内首次”等表述
- 引用外部工作前先要求用户提供 DOI/链接或可核验题录信息
- 若 AI 不可用，必须回退到硬编码能力，不得直接停工
推荐工作流
- 定位项目与目标文件。
- 抽取现有小标题骨架与正文范围。
- 用
scripts/run.py coach --stage auto判断当前处于 skeleton / draft / revise / polish 哪一阶段。 - 围绕 4 段闭环组织内容：
- 价值与必要性
- 现状与不足
- 科学问题 / 科学假设
- 本项目切入点与贡献
- 做可核验性与引用守护，避免吹牛式表述。
- 检查与
2.1 研究内容的术语、缩写、指标一致性。 - 解析目标字数；无显式要求时再用配置兜底。
- 输出诊断、评审建议或安全写回结果。
关键能力
- Tier1 硬编码诊断：结构、字数、引用键、危险命令、高风险表述提示
- AI 语义能力：内容维度覆盖、吹牛式表述识别、术语一致性、阶段判断、示例推荐
- 安全写入：按
\subsubsection{...}精确替换正文并自动备份 - 可视化报告、diff、rollback、review 建议
常用脚本
scripts/run.py initscripts/run.py coach --stage autoscripts/run.py diagnosescripts/run.py reviewscripts/run.py apply-sectionscripts/run.py diffscripts/run.py rollback
只读集成
- 支持只读访问
research-literature-review的结果目录，用于提取研究现状和验证引用一致性；历史工作区目录名仍为.systematic-literature-review/ - 集成逻辑见
scripts/core/review_integration.py - 该集成是只读的，不得修改综述目录内容
重点参考
references/theoretical_innovation_guidelines.mdreferences/methodology_term_examples.mdreferences/boastful_expression_guidelines.mdreferences/dimension_coverage_design.mdreferences/dod_checklist.mdscripts/README.md
When not to use it
- →When editing files outside of extraTex/1.1.立项依据.tex
- →When writing unverified claims like international leadership
Limitations
- →Only edits extraTex/1.1.立项依据.tex
- →Cannot modify main.tex or class/style files
How it compares
It automates the drafting process while enforcing strict structural constraints and preventing the inclusion of unverifiable boastful expressions common in manual writing.
Compared to similar skills
nsfc-justification-writer side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| nsfc-justification-writer (this skill) | 1 | 4mo | Review | Intermediate |
| docs-write | 22 | 6mo | No flags | Beginner |
| content-research-writer | 15 | 9mo | No flags | Beginner |
| doc-coauthoring | 16 | 8mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by huangwb8
View all by huangwb8 →You might also like
docs-write
metabase
Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).
content-research-writer
ComposioHQ
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
doc-coauthoring
anthropics
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
research-grants
davila7
Write competitive research proposals for NSF, NIH, DOE, and DARPA. Agency-specific formatting, review criteria, budget preparation, broader impacts, significance statements, innovation narratives, and compliance with submission requirements.
teams-channel-post-writer
daymade
Creates educational Teams channel posts for internal knowledge sharing about Claude Code features, tools, and best practices. Applies when writing posts, announcements, or documentation to teach colleagues effective Claude Code usage, announce new features, share productivity tips, or document lessons learned. Provides templates, writing guidelines, and structured approaches emphasizing concrete examples, underlying principles, and connections to best practices like context engineering. Activates for content involving Teams posts, channel announcements, feature documentation, or tip sharing.
write-docs
tldraw
Writing SDK documentation for tldraw. Use when creating new documentation articles, updating existing docs, or when documentation writing guidance is needed. Applies to docs in apps/docs/content/.