kakenhi_writing

Writes and revises JSPS KAKENHI research grant proposals against official review criteria.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/sayonari/claude-skills --skill kakenhi-writing-sayonari
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kakenhi_writing
Source: https://github.com/sayonari/claude-skills/tree/main/kakenhi_writing
Command: npx skills add https://github.com/sayonari/claude-skills --skill kakenhi-writing-sayonari

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a competitive KAKENHI (Japanese JSPS research grant) proposal requires deep knowledge of the review system, evaluation criteria, and unwritten conventions. Most rejections come from preventable issues: unclear research questions, missing responses to evaluation sub-criteria, poor figure design, and layouts that fail under monochrome review. This Skill encodes the full body of practical knowledge needed to avoid those failure modes. ## Core Features & Use Cases - Defense against deduction: Maps every official evaluation sub-criterion (JSPS原文) to specific sections of the proposal so reviewers cannot find a reason to mark items as insufficient, including the commonly missed budget-plan consistency statement. - Category-specific guidance: Covers Kiban B/C and Challenging Research (Hattatsu/Hoga) with distinct strategies, title conventions, page budgets, and the pre-screening reality that the summary version is the real first gate for Hoga. - Evaluation simulation workflow: Provides a self-review procedure that reproduces the actual review process—scoring each sub-criterion 4/3/2/1 with persona-based mock reviews (specialist, adjacent-field, statistics-strict, practitioner, administrative). - Production practicalities: Figure design rules (grayscale-first, 10cm canvas, font-size math), LaTeX fixed-frame page adjustment, Word-format handling for JSPS bilateral programs, and parallel draft management. - Use Case: When revising a rejected Kiban B proposal, use the Skill to map disclosure feedback (* marks) to weak sections, run the evaluation simulation, and restructure only the flagged criteria while preserving highly rated sections. ## Quick Start Ask the AI to review your KAKENHI proposal draft against the evaluation criteria using the kakenhi_writing skill and produce a criterion-by-criterion response table.

Frequently Asked Questions about kakenhi_writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a KAKENHI proposal that passes review?

Map every official evaluation sub-criterion to a visible section of your proposal so reviewers cannot select it as a deficiency. Write the summary last in about 10 lines, state the research question as a single verifiable question, and show preliminary results as evidence the work is already underway.

What makes a good academic research question for KAKENHI?

A clear question satisfies four requirements: it expresses something unknown whose answer is wanted, an academic community wants that answer, it is narrowed to one question, and you can imagine what answering it looks like. Questions like 'what elements are needed' or 'how far can we go' fail the fourth requirement.

How is the KAKENHI review process structured for Kiban B?

Kiban B uses two-stage document review with about five reviewers per proposal and forced score distribution (4=10%, 3=20%, 2=40%, 1=30%). A score of 3 corresponds to roughly 5% adoption, so the strategy is eliminating reasons for 2-or-below while giving at least one reviewer a reason to score 4 or 5.

Why must KAKENHI figures be designed in grayscale?

All categories except Kiban A are converted to grayscale before reviewers see them, so color-coded figures lose their meaning. Design figures from the start using only white, light gray, dark gray, and black, distinguishing elements by line style, fill density, and border weight.

How should I revise a rejected KAKENHI proposal?

Start from the disclosure results: sections with high ratings should be preserved structurally, while *-marked criteria get concentrated revision. If the same theme keeps declining, rebuild at the question level rather than repeating minor edits, and always save disclosure results for future analysis.

What are common reasons KAKENHI proposals get rejected?

The most frequent causes are an unclear research question, vague methods lacking concrete numbers and timelines, excessive jargon, mismatch between track record and plan, and budget items not tied to research activities. Proposals with over one page of blank space have a measured 0% adoption rate.