agentleFS
lengrufeng2008lengrufeng2008/dsh-skill-library/skills/grant-writing/SKILL.md

grant-writing

Skill0 starsChanged 15 days agoMITView on GitHub

Align the question, gap, approach, feasibility, and impact.

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use scientific-writing.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ZanderRussSkill

    scientific-writing

    Core skill for the deep research and writing tool. Write scientific manuscripts in full paragraphs (never bullet points). Use two-stage process: (1) create section outlines with key points using research-lookup, (2) convert to flowing prose. IMRAD structure, citations (APA/AMA/Vancouver), figures/tables, reporting guidelines (CONSORT/STROBE/PRISMA), for research papers and journal submissions.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every citation resolves and supports the claim.

    line 24
  2. Distinctive:

    No fabricated sources, data, or test results.

    line 31
  3. Distinctive:

    If the task falls outside the method, say so and stop.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Grant writing

Use

Apply this when the task matches the description. Keep the output decision-useful and mark unknowns.

Method

  1. State the question and prior work.
  2. Separate source, observation, and inference.
  3. Record uncertainty and method limits.
  4. Make the result reproducible.

Focus: Grant writing.

Verification

  • Every citation resolves and supports the claim.
  • Commands/data are sufficient to rerun.
  • State clearly what was not verified.

Boundaries

  • This is a checklist, not proof of correctness.
  • No fabricated sources, data, or test results.
  • If the task falls outside the method, say so and stop.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.