sciwrite-proposals
Write the documents an academic career runs on besides papers: narrative review articles, grant and fellowship applications (specific aims, research plan), letters of recommendation, and personal statements. Based on Stanford's Writing in the Sciences. Use this skill whenever someone mentions writing or reviewing a grant, a fellowship application, a research proposal, a specific aims page, a research plan or strategy, a review article or literature review, a letter of recommendation or reference letter, a personal statement, a motivation letter, or an application essay for a PhD programme, postdoc, scholarship or residency. Also use it when someone asks how to ask for a recommendation letter, how to narrow a review topic, what reviewers of a fellowship are actually scored against, or how to respond to reviewers of a grant or fellowship application. Do NOT use it for research papers (sciwrite-manuscript) or for sentence-level editing alone (sciwrite-prose).
dvdsosa · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add dvdsosa/scientific-writing-skills --skill sciwrite-proposals技能说明
name: sciwrite-proposals description: > Write the documents an academic career runs on besides papers: narrative review articles, grant and fellowship applications (specific aims, research plan), letters of recommendation, and personal statements. Based on Stanford's Writing in the Sciences. Use this skill whenever someone mentions writing or reviewing a grant, a fellowship application, a research proposal, a specific aims page, a research plan or strategy, a review article or literature review, a letter of recommendation or reference letter, a personal statement, a motivation letter, or an application essay for a PhD programme, postdoc, scholarship or residency. Also use it when someone asks how to ask for a recommendation letter, how to narrow a review topic, what reviewers of a fellowship are actually scored against, or how to respond to reviewers of a grant or fellowship application. Do NOT use it for research papers (sciwrite-manuscript) or for sentence-level editing alone (sciwrite-prose).
Proposals, reviews, letters and statements
Four genres that share a property: the reader is deciding something about you or your project, quickly, alongside many others. All the prose rules still apply — use sciwrite-prose — but each has its own structure, and structure is where these are won or lost.
Answer in whatever language the user writes to you in.
Narrative review articles
A good project for a graduate student or early investigator: you read the current literature properly, practise synthesis and organisation, and a well-made review earns citations because it is useful.
The single decision that determines whether this works: a narrow, clear theme. "I will review microarrays" or "I will review breast cancer" is not a review, it is a career. "Microarrays in microbiology", "statistical techniques for microarray data", "the history of microarray technology", "breast cancer and exercise" — those are tractable.
Three kinds, and this skill covers the first. Narrative (non-systematic) — your synthesis of the recent primary literature. Systematic — a rigorous, prespecified search strategy aiming to find every relevant study, including unpublished ones. Meta-analysis — a systematic review that statistically pools data across studies. The latter two carry methodological requirements beyond this skill.
Pre-writing dominates. Reading, note-taking and organising will take far more time than writing. Decide the sections and subsections early, then file notes from each paper directly into the section they belong to. A reference manager (Zotero, Mendeley, EndNote) is not optional at this scale.
Structure:
- Abstract — written last
- Introduction — states the theme and the aim of the review explicitly
- Body — sections with headings, subsections with subheadings. In each: what is known, what remains unknown, and how future studies could do better
- Conclusion — what you found, plus specific recommendations for what the field should do next
- References — a narrative review can easily run to 150+
Write for a broad audience. People read reviews to enter a field. Do not abbreviate heavily and do not assume prior knowledge. Numeric data across studies goes in a summary table; tangential but interesting material goes in a sidebar or box rather than being forced into the flow.
Grants and fellowships
Full detail in references/specific-aims.md and references/research-plan.md.
Start there when someone is actually writing one. The framing that matters most:
Get the information before you write. Compile every opportunity you are eligible for; ask peers and mentors what they applied to; check whether your institution keeps a list. Then, for the one you are targeting, read the funding announcement in its entirety — including linked attachments — and, critically, identify the review criteria, because those are the questions your reviewers will literally be scored against. For an NIH NRSA fellowship, for example, they are: the applicant, the mentor and collaborators, the research training plan, the training potential, and the institutional environment. Also find out your own institution's internal deadlines, which fall before the sponsor's.
Write regularly, not in bursts. Break the application into tasks with a dated timeline. Write daily or every other day, and make the time non-negotiable. Writing becomes a habit and the anxiety drops.
Find the gap, not just the topic. A compelling proposal names a critical knowledge gap or bottleneck — something that, if solved, moves the field more than incrementally. Keep a running list of the problems inherent to your field, updated after every paper and seminar, and narrow it through conversation with colleagues and mentors. Compelling projects often join two threads that nobody had connected.
Get feedback early, often, and widely. Your reviewers will come from mixed backgrounds, so your readers should too — including non-scientists, who are excellent judges of clarity. Tell each reader what kind of feedback you want: concept and feasibility, or grammar and readability. The specific aims page exists partly to make this cheap: it is one page, so people will actually read it.
Tell one consistent story across every document. An application is many files — aims, research plan, biosketch personal statement, training plan. The long-term goal stated in one must be the long-term goal stated in the others. Leave one to two weeks after drafting everything to read the whole package for coherence.
Follow the formatting rules exactly. Page limits, margins, fonts. Applications that do not conform can be administratively rejected before review. And proofread: an application full of errors invites reviewers to wonder how carefully you will run the experiments.
Plan to resubmit. Announcements often have similar requirements, so an application can be
阅读完整来源 ↗