nsfc-budget_skill

Overview

This skill generates a submission-ready NSFC budget justification as an editable LaTeX project and a compiled budget.pdf. It uses the proposal text and supporting materials to produce a budget_spec.json, render LaTeX sections, validate amounts and paths, and compile a final PDF placed under the specified work directory.

How this skill works

First it requires a work directory and proposal materials; it then initializes a hidden run area and builds a budget_spec.json skeleton. The tool maps each expense to concrete research tasks, fills five structured sections with explanations and evidence, validates numeric relations and path safety, renders the LaTeX project into an output directory, and compiles budget.pdf while saving logs and validation reports in the hidden run folder.

When to use it

• When you explicitly ask: “write/generate NSFC budget justification” or “generate budget.tex / budget.pdf”.
• When you want a budget explanation tied to specific proposal text and supporting materials.
• When you need a LaTeX project and compiled PDF ready for submission.
• When you require strict validation of amount consistency and path safety before delivery.
• Not for general questions about budgeting principles or only numeric budget tables.

Best practices

• Always provide the work directory before any run; the skill will pause until given.
• Supply complete proposal text and supporting docs per the provided info_form structure.
• Specify project type (general | local | youth) and the budget scope (application total or direct-cost basis).
• If evidence is missing, answer queries rather than inventing assumptions; prefer conservative omissions.
• Review the validation_report and logs in the hidden run folder and correct budget_spec.json as needed before re-rendering.

Example use cases

• You have a draft proposal and ask: “Generate NSFC budget justification and budget.pdf in /home/alex/proj1”.
• Convert proposal sections and cost calculations into a five-part LaTeX budget justification with traceable evidence.
• Enforce that equipment + business + labor match declared direct costs and render final PDF for submission.
• Iteratively refine amounts: run init -> edit budget_spec.json -> re-render until validation passes.
• Produce a conservative justification when some partnership or pricing evidence is pending, marking items as ‘to confirm’.