explainx.ainewsletter3.4k
Productivity

nsfc-justification-writer▌

huangwb8/chineseresearchlatex · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/huangwb8/chineseresearchlatex --skill nsfc-justification-writer
0 commentsdiscussion
summary

nsfc-justification-writer

skill.md

科研立项依据写作器

与 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.md
    • references/scientific_hypothesis_guidelines.md
  • 推荐用 scripts/run.py init 帮用户快速生成和补全信息表

硬规则

  • 只编辑 extraTex/1.1.立项依据.tex
  • 优先保留现有 \subsubsection 骨架，只替换正文
  • 不写无法核验的“国际领先/国内首次”等表述
  • 引用外部工作前先要求用户提供 DOI/链接或可核验题录信息
  • 若 AI 不可用，必须回退到硬编码能力，不得直接停工

推荐工作流

  1. 定位项目与目标文件。
  2. 抽取现有小标题骨架与正文范围。
  3. 用 scripts/run.py coach --stage auto 判断当前处于 skeleton / draft / revise / polish 哪一阶段。
  4. 围绕 4 段闭环组织内容：
    • 价值与必要性
    • 现状与不足
    • 科学问题 / 科学假设
    • 本项目切入点与贡献
  5. 做可核验性与引用守护，避免吹牛式表述。
  6. 检查与 2.1 研究内容 的术语、缩写、指标一致性。
  7. 解析目标字数；无显式要求时再用配置兜底。
  8. 输出诊断、评审建议或安全写回结果。

关键能力

  • Tier1 硬编码诊断：结构、字数、引用键、危险命令、高风险表述提示
  • AI 语义能力：内容维度覆盖、吹牛式表述识别、术语一致性、阶段判断、示例推荐
  • 安全写入：按 \subsubsection{...} 精确替换正文并自动备份
  • 可视化报告、diff、rollback、review 建议

常用脚本

  • scripts/run.py init
  • scripts/run.py coach --stage auto
  • scripts/run.py diagnose
  • scripts/run.py review
  • scripts/run.py apply-section
  • scripts/run.py diff
  • scripts/run.py rollback

只读集成

  • 支持只读访问 systematic-literature-review 的结果目录，用于提取研究现状和验证引用一致性
  • 集成逻辑见 scripts/core/review_integration.py
  • 该集成是只读的，不得修改综述目录内容

重点参考

  • references/theoretical_innovation_guidelines.md
  • references/methodology_term_examples.md
  • references/boastful_expression_guidelines.md
  • references/dimension_coverage_design.md
  • references/dod_checklist.md
  • scripts/README.md
how to use nsfc-justification-writer

How to use nsfc-justification-writer on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • ›Cursor installed and configured on your development machine
  • ›Node.js version 16.0+ with npm package manager (verify with node --version)
  • ›Active project directory or workspace where you want to add nsfc-justification-writer
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/huangwb8/chineseresearchlatex --skill nsfc-justification-writer

The skills CLI fetches nsfc-justification-writer from GitHub repository huangwb8/chineseresearchlatex and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/nsfc-justification-writer

Reload or restart Cursor to activate nsfc-justification-writer. Access the skill through slash commands (e.g., /nsfc-justification-writer) or your agent's skill management interface.

⚠

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

Additional Resources

›View source code on GitHub›Skills CLI documentation›Learn more about Cursor›What are agent skills?

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases▌

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

✓

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

✓

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

✓

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

✓

Save 3-5 hours/week on communication overhead

Implementation Guide▌

Prerequisites

  • ›Claude Desktop or compatible AI client
  • ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • ›Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • ⚠Not validating competitive research—verify facts before sharing
  • ⚠Accepting user stories without involving engineering team
  • ⚠Over-relying on frameworks without qualitative judgment
  • ⚠Not customizing outputs to company culture and communication style
  • ⚠Skipping stakeholder validation of generated requirements

Best Practices▌

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • −Don't publish competitive analysis without fact-checking
  • −Don't finalize user stories without engineering review
  • −Don't make prioritization decisions solely on AI scoring
  • −Don't skip customer validation of generated requirements
  • −Don't ignore company-specific context and culture

💡 Pro Tips

  • ★Provide context: company goals, constraints, customer feedback
  • ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • ★Use skill for 70% generation + 30% customization to company needs

When to Use This▌

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path▌

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.6★★★★★43 reviews
  • ★★★★★Zara Jain· Dec 24, 2024

    Useful defaults in nsfc-justification-writer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • ★★★★★Chinedu Robinson· Dec 20, 2024

    nsfc-justification-writer has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • ★★★★★Naina Gonzalez· Dec 12, 2024

    Solid pick for teams standardizing on skills: nsfc-justification-writer is focused, and the summary matches what you get after install.

  • ★★★★★Olivia Johnson· Dec 4, 2024

    I recommend nsfc-justification-writer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • ★★★★★Chen Smith· Nov 23, 2024

    Solid pick for teams standardizing on skills: nsfc-justification-writer is focused, and the summary matches what you get after install.

  • ★★★★★Xiao Thompson· Nov 15, 2024

    nsfc-justification-writer has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • ★★★★★Chen Malhotra· Nov 11, 2024

    Useful defaults in nsfc-justification-writer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • ★★★★★Nikhil Ghosh· Nov 3, 2024

    I recommend nsfc-justification-writer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • ★★★★★Xiao Martin· Oct 22, 2024

    Useful defaults in nsfc-justification-writer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • ★★★★★Chen Reddy· Oct 14, 2024

    nsfc-justification-writer has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 43

1 / 5