Generate high-quality academic research proposals for PhD applications following Nature Reviews-style academic writing conventions.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionresearch-proposalExecute the skills CLI command in your project's root directory to begin installation:
Fetches research-proposal from luwill/research-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate research-proposal. Access via /research-proposal in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
4
total installs
4
this week
435
GitHub stars
0
upvotes
Run in your terminal
4
installs
4
this week
435
stars
Generate high-quality academic research proposals for PhD applications following Nature Reviews-style academic writing conventions.
This skill guides the generation of research proposals through a structured 5-phase workflow:
Target Output: 2,000-4,000 words (default ~3,000 words) for PhD applications.
Use AskUserQuestion to collect the following information:
Research Topic/Direction
Academic Domain
Output Language
Target Word Count
Target Institution(s)
Existing Materials
Questions to ask the user:
1. "What is your research topic or direction? Please describe the core question or problem you want to investigate."
2. "Which academic domain does your research belong to?"
- STEM (Science, Technology, Engineering, Mathematics)
- Humanities (History, Philosophy, Literature)
- Social Sciences (Sociology, Psychology, Economics)
3. "What language should the proposal be written in?"
- English
- 中文 (Chinese)
4. "Do you have a target word count? (Default: ~3,000 words)"
5. "Are you applying to specific institutions or working with particular faculty?"
6. "Have you uploaded relevant literature to your Zotero library that I should reference?"
┌─────────────────────────────────────────────────────────┐
│ Literature Sources │
├─────────────────────────────────────────────────────────┤
│ General Info → WebSearch (trends, news, reviews) │
│ Open Access → arXiv, PubMed (preprints, OA papers)│
│ Closed Access → Zotero MCP (user's uploaded papers) │
└─────────────────────────────────────────────────────────┘
Search for:
Example searches:
"{topic} systematic review 2024 2025"
"{topic} research trends future directions"
"{topic} methodology recent advances"
IMPORTANT: Remind users to upload relevant closed-access literature to Zotero before starting.
# Search by topic keywords
Use: mcp__zotero__zotero_search_items
Parameters: query = "{research topic keywords}"
# Advanced search with filters
Use: mcp__zotero__zotero_advanced_search
Parameters: conditions based on author, title, year, tags
# Semantic search for related papers
Use: mcp__zotero__zotero_semantic_search
Parameters: query = "{research question}"
# Get full text content
Use: mcp__zotero__zotero_get_item_fulltext
Parameters: item_key = "{item key from search}"
# Get user's annotations and highlights
Use: mcp__zotero__zotero_get_annotations
Parameters: item_key = "{item key}"
# Get user's notes
Use: mcp__zotero__zotero_get_notes
Parameters: item_key = "{item key}"
Organize collected literature into categories:
Read the reference file for domain-specific guidance:
references/STRUCTURE_GUIDE.md - Detailed section guidelinesreferences/DOMAIN_TEMPLATES.md - STEM vs Humanities differences# [Research Title]
## Abstract (150-300 words, 5-10%)
- Research problem summary
- Research questions/objectives
- Methodology overview
- Expected significance
## 1. Introduction (500-800 words, 15-20%)
### 1.1 Background and Context
### 1.2 Problem Statement
### 1.3 Research Questions/Objectives
### 1.4 Scope and Delimitations
## 2. Literature Review (500-1000 words, 20-25%)
### 2.1 Theoretical Framework
### 2.2 Current State of Research
### 2.3 Research Gap Analysis
### 2.4 Positioning of This Study
## 3. Methodology (500-800 words, 20-25%)
### 3.1 Research Design
### 3.2 Data Collection Methods
### 3.3 Data Analysis Approach
### 3.4 Validity and Limitations
## 4. Timeline (200-300 words, 5-10%)
### 4.1 Research Phases
### 4.2 Key Milestones
### 4.3 Gantt Chart (optional)
## 5. Significance and Expected Contributions (200-400 words, 10-15%)
### 5.1 Theoretical Contributions
### 5.2 Practical Implications
### 5.3 Broader Impact
## References (minimum 40 references)
Note: Do NOT include Appendix sections. All essential content should be integrated into the main body.
CRITICAL: Present the outline to the user and wait for confirmation before proceeding to content generation.
Present the generated outline and ask:
"Here is the proposed outline for your research proposal:
[Display outline with section titles and estimated word counts]
Please review and let me know:
1. Is the overall structure acceptable?
2. Would you like to add, remove, or modify any sections?
3. Should any section receive more/less emphasis?
I will proceed with content generation once you approve the outline."
Read and apply: references/WRITING_STYLE_GUIDE.md
Academic Register
Prose-Based Writing Style (CRITICAL)
AVOID point-by-point enumeration. Academic proposals should read as flowing, connected prose rather than bulleted lists or numbered items. Use transitional phrases and coherent paragraphs to present ideas.
| Avoid | Use Instead |
|---|---|
| Bullet points listing objectives | Integrated paragraph describing objectives with transitions |
| Numbered lists of contributions | Narrative prose explaining contributions in context |
| Tables for methodology steps | Flowing description of research design |
When lists ARE appropriate (use sparingly):
Example transformation:
❌ Poor (point-by-point):
The contributions include:
- Novel segmentation algorithm
- Multi-modal fusion framework
- Clinical validation study
✓ Good (prose-based):
This research is expected to advance the field through several interconnected
contributions. First, the development of a novel segmentation algorithm will
enable automated plaque detection with accuracy surpassing current methods.
Building on this foundation, a multi-modal fusion framework will integrate
complementary imaging data to capture plaque characteristics inaccessible to
any single modality. Finally, rigorous clinical validation will establish
the prognostic value of these computational biomarkers for predicting
cardiovascular events.
Hedging Language (Academic Caution)
| Avoid | Use Instead |
|---|---|
| "will prove" | "aims to demonstrate" |
| "definitely" | "likely", "potentially" |
| "is obvious" | "evidence suggests" |
| "proves" | "indicates", "demonstrates" |
Sentence Templates
Introducing Background:
Identifying Gaps:
Stating Objectives:
Methodology Justification:
Expected Contributions:
Transitions and Connectors
Paragraph Structure
Topic Sentence → Supporting Evidence (with citations) → Synthesis/Implications
Based on domain:
First mention of abbreviations: "coronary CT angiography (CCTA)"
Integrate citations into text: "Recent studies (Smith et al., 2023; Jones, 2024) have demonstrated..."
IMPORTANT: Include suggestions for figures at appropriate locations throughout the proposal. Figures significantly enhance readability and demonstrate the applicant's ability to communicate complex ideas visually.
Insert figure suggestions using the following format:
> **[Figure 1 Suggestion]** *Title: Overview of the proposed research framework*
> Content: A flowchart or schematic diagram illustrating the three-phase research
> design, showing data flow from imaging modalities through AI processing to
> clinical outcomes. Include icons for CCTA/IVUS/OCT inputs, deep learning
> modules, and output predictions.
> Recommended style: Clean vector graphics with consistent color scheme.
| Section | Suggested Figure Type |
|---|---|
| Introduction | Conceptual diagram showing research scope and positioning |
| Literature Review | Timeline of key developments; Taxonomy/classification of existing methods |
| Methodology | Research framework flowchart; Network architecture diagram; Data processing pipeline |
| Timeline | Gantt chart showing research phases and milestones |
| Significance | Impact diagram showing theoretical and practical contributions |
Generate the proposal as a Markdown file:
proposal_{topic_slug}_{YYYY-MM-DD}.md
Save to user's working directory or specified location.
Read and apply: references/QUALITY_CHECKLIST.md
Verify:
Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
research-proposal is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
research-proposal reduced setup friction for our internal harness; good balance of opinion and flexibility.
research-proposal has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: research-proposal is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend research-proposal for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: research-proposal is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added research-proposal from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
research-proposal reduced setup friction for our internal harness; good balance of opinion and flexibility.
research-proposal is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend research-proposal for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 33