Academic Research
voidful/academic-skills
Complete academic research skill suite covering the full pipeline: paper reading (read/explain papers with storytelling), idea generation (brainstorm research directions), experiment design (plan…
Guides pre-writing planning for academic papers with 4 structured steps: story design (task-challenge-insight-contribution-advantage), experiment planning (comparisons + ablations), figure design…
Install Paper Planning
$ npx skills add EvoScientist/EvoSkills --skill paper-planning -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install EvoScientist/EvoSkills paper-planning --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/EvoScientist/EvoSkills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/paper-planning .claude/skills/paper-planning && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "paper-planning" agent skill from https://github.com/EvoScientist/EvoSkills/tree/main/skills/paper-planning into .claude/skills/paper-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paper-planning", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/EvoScientist/EvoSkills/tree/main/skills/paper-planningType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add EvoScientist/EvoSkills --skill paper-planning -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install EvoScientist/EvoSkills paper-planning --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EvoScientist/EvoSkills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/paper-planning .agents/skills/paper-planning && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "paper-planning" agent skill from https://github.com/EvoScientist/EvoSkills/tree/main/skills/paper-planning into .agents/skills/paper-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paper-planning", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add EvoScientist/EvoSkills --skill paper-planning -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install EvoScientist/EvoSkills paper-planning --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EvoScientist/EvoSkills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/paper-planning .cursor/skills/paper-planning && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "paper-planning" agent skill from https://github.com/EvoScientist/EvoSkills/tree/main/skills/paper-planning into .cursor/skills/paper-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paper-planning", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/EvoScientist/EvoSkills.git --path skills/paper-planning--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add EvoScientist/EvoSkills --skill paper-planning -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install EvoScientist/EvoSkills paper-planning --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EvoScientist/EvoSkills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/paper-planning .gemini/skills/paper-planning && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "paper-planning" agent skill from https://github.com/EvoScientist/EvoSkills/tree/main/skills/paper-planning into .gemini/skills/paper-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paper-planning", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install EvoScientist/EvoSkills paper-planningInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add EvoScientist/EvoSkills --skill paper-planning -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/EvoScientist/EvoSkills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/paper-planning .github/skills/paper-planning && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "paper-planning" agent skill from https://github.com/EvoScientist/EvoSkills/tree/main/skills/paper-planning into .github/skills/paper-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paper-planning", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add EvoScientist/EvoSkills --skill paper-planning -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install EvoScientist/EvoSkills paper-planning --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EvoScientist/EvoSkills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/paper-planning .opencode/skills/paper-planning && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "paper-planning" agent skill from https://github.com/EvoScientist/EvoSkills/tree/main/skills/paper-planning into .opencode/skills/paper-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paper-planning", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
paper-planning- GitHub stars
- 476
- Used in
- 3 other repos
- Token cost
- ~2.4k tokens
- SKILL.md length
- 1,018 words
- Files
- 7 (incl. references, assets)
- Skills in repo
- 16
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Guides pre-writing planning for academic papers with 4 structured steps: story design (task-challenge-insight-contribution-advantage), experiment planning (comparisons + ablations), figure design…
- Works in 4 steps: Story Design → Experiment Planning → Figure Design → …
- : user wants to plan a paper before writing
- SKILL.md covers When to Use This Skill, Planning Overview, Counterintuitive Planning First and Step 1: Story Design, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Paper Planning is an agent skill from EvoScientist/EvoSkills. Guides pre-writing planning for academic papers with 4 structured steps: story design (task-challenge-insight-contribution-advantage), experiment planning (comparisons + ablations), figure design (pipeline + teaser), and 4-week timeline management. Includes counterintuitive planning tactics (write a mock rejection letter to identify weaknesses before writing, narrow before broad claims, design ablations first). Use when: user wants to plan a paper before writing, design story/contributions, plan experiments…
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files and assets (for example `assets/experiment-plan-template.md`, `references/counterintuitive-planning.md` and `references/experiment-planning.md`).
It sits in Research & Science, covering Brainstorming, Scientific writing and Peer review. The repository describes itself as: 🧬 Extend EvoScientist with Installable Skill & Knowledge Packs. The licence is Apache-2.0.
When your agent uses it
- : user wants to plan a paper before writing
- Design story/contributions
- Plan experiments
- Create figure sketches
Example prompts
- “Use the paper-planning skill to guide pre-writing planning for academic papers with 4 structured steps: story design…”
- “/paper-planning”
Requirements
- Pre-approved tools (allowed-tools): write_file, edit_file, read_file, think_tool
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 9a9f8cf. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
write_fileedit_fileread_filethink_tool
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Paper Planning loads about 2.4k tokens when it runs, and up to ~8k if it reads all its reference files. Until then it costs about 211 tokens; SKILL.md has 1,018 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from EvoScientist/EvoSkills at commit 9a9f8cf, republished under its Apache-2.0 licence (© EvoScientist). 1,018 words, ~2,449 tokens.
Download SKILL.mdSave it as
.claude/skills/paper-planning/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- paper-planning
- description
- Guides pre-writing planning for academic papers with 4 structured steps: story design (task-challenge-insight-contribution-advantage), experiment planning (comparisons + ablations), figure design (pipeline + teaser), and 4-week timeline management. Includes counterintuitive planning tactics (write a mock rejection letter to identify weaknesses before writing, narrow before broad claims, design ablations first). Use when: user wants to plan a paper before writing, design story/contributions, plan experiments, create figure sketches, set a writing timeline, or write a pre-emptive rejection letter for planning purposes. Do NOT use for actual writing (use paper-writing), running experiments (use experiment-pipeline), self-reviewing a finished draft (use paper-review), or finding research problems (use research-ideation).
- allowed-tools
- write_file, edit_file, read_file, think_tool
- metadata.author
- EvoScientist
- metadata.version
- 1.0.0
- metadata.tags
- core, research, writing, academic-writing, experiment-design
Paper Planning
A structured approach to planning academic papers before writing begins. Covers four key activities: Story design, Experiment planning, Figure design, and Timeline management.
When to Use This Skill
If you don't yet have an idea, use the
research-ideationskill first to find a problem and design a solution.
- User wants to plan a paper before writing
- User asks about structuring a paper's story or contributions
- User needs to plan experiments (comparisons, ablations)
- User wants to design pipeline figures or teaser figures
- User asks about writing timelines or submission schedules
Planning Overview
Paper planning follows four steps, ideally completed before writing begins:
Step 1: Story Design → What is the narrative? What are the contributions?
Step 2: Experiment Plan → What experiments prove our claims?
Step 3: Figure Design → How do we visually communicate the method?
Step 4: Timeline → When does each section get written?Counterintuitive Planning First
Prioritize these counterintuitive rules before regular planning:
- Write your rejection letter first: Draft the top-5 likely rejection comments ("limited novelty", "missing baseline", "not robust", etc.), then plan experiments that directly preempt each one.
- Narrow claim before broad claim: Define the smallest defensible core claim first. Expand only after evidence is strong. Over-broad claims fail review more often than narrow strong claims.
- Design ablations before polishing method text: If a module cannot be ablated cleanly, its contribution claim is weak.
- Allocate compute to stress tests, not only benchmarks: A single convincing stress-test figure often contributes more than multiple small benchmark gains.
- Plan a fallback narrative now: If SOTA gain is marginal, predefine a secondary value proposition (efficiency, robustness, fewer assumptions, wider applicability).
See references/counterintuitive-planning.md
Step 1: Story Design
The "story" is the logical narrative that connects the problem, insight, method, and results.
Reverse Engineering the Story
Work backwards to build the story:
- What is the technical problem? — The specific challenge that existing methods cannot solve well
- What are our contributions? — The concrete technical novelties
- What are the benefits and new insights? — What advantages does our approach provide?
- How do we lead into the challenge? — How to frame the task and previous methods to naturally arrive at the challenge
Then write forward: Task → Previous methods → Challenge → Our contributions → Advantages
Core Elements to Define
Before writing any section, clearly articulate:
| Element | Question | Example |
|---|---|---|
| Task | What problem does this paper address? | "Real-time 3D scene reconstruction" |
| Challenge | Why can't existing methods solve it well? | "Cannot handle dynamic objects efficiently" |
| Insight | What key observation drives our approach? | "Motion patterns are temporally sparse" |
| Contribution | What do we propose? | "Sparse temporal attention for dynamic regions" |
| Advantage | Why is our approach better? | "Reduces computation while preserving quality" |
Starting Point: Pipeline Figure Sketch
Start by drawing a pipeline figure sketch. This forces you to clarify the overall method before writing.
The pipeline figure sketch serves as the paper's visual backbone:
- Draw it before writing anything
- It reveals whether the method is clear enough to explain
- It identifies the novel modules vs. standard components
- It determines subsection structure for the Method section
See references/story-design.md
Step 2: Experiment Planning
Plan experiments before writing to avoid discovering gaps late.
Two Categories of Experiments
Comparison Experiments — Prove our method is better:
- Which baseline methods to compare against?
- Which datasets and metrics?
- What is the evaluation protocol?
Ablation Studies — Prove each module is effective:
- Part 1: One big table showing impact of core contributions
- Part 2: Several small tables for design choices and hyperparameters
Planning Checklist
- List all comparison baselines (recent, relevant, SOTA)
- Define evaluation metrics (standard for the task)
- Identify datasets (standard benchmarks + challenging demos)
- List ablation configurations (remove each core component)
- Plan design-choice tables (hyperparameters, input quality, alternatives)
- Plan demo scenarios (challenging data to showcase upper limit)
See references/experiment-planning.md
Experiment Plan Template
Use the template at assets/experiment-plan-template.md to organize your experiment plan.
Step 3: Figure Design
The pipeline figure is for highlighting novelty, not for making readers understand. The Method text is what makes readers understand.
Show full SKILL.md (400 more words)Show less
Pipeline Figure Principles
- Highlight novelty: The pipeline figure showcases what is new, not just the workflow
- Differentiate from prior work: The figure must look different from previous methods
- Novel modules stand out: If the overall pipeline is standard, zoom in on novel modules
- Focus on clarity of the novel parts; standard components can be simplified
Teaser Figure
The teaser (usually Figure 1) shows the key result at a glance:
- Place it at the top of the first page
- Should be immediately compelling
- Reference it from the Introduction
Visual Quality Matters
Visual polish directly influences review outcomes. See references/figure-design.md for the full visual quality guide (pipeline figures, tables, typography)
Step 4: Timeline
4-Week Countdown
Start writing at least 1 month before the deadline.
| Week | Tasks |
|---|---|
| 4 weeks before | 1. Organize story (core contribution, module motivations). 2. List comparison experiments and ablation studies. 3. Write Introduction first draft. |
| 3 weeks before | 1. Finalize the pipeline figure sketch. 2. Write Method first draft (use \todo{} for unsettled details). Deadline: give Introduction + Method draft to advisor. |
| 2 weeks before | Write first drafts of Experiments, Abstract, Related Work. |
| Last week | Revise paper, polish pipeline figure and teaser, run demos. |
Critical: By the end of Week 3, you must send the Introduction and Method drafts to your advisor — otherwise the advisor likely will not have enough time to finish reviewing the paper.
See references/timeline-4week.md for the detailed schedule and progress tracking template.
Handoff to Writing
When planning is complete, pass these artifacts to paper-writing:
| Artifact | Source Step | Used By |
|---|---|---|
| Story summary (task → challenge → insight → contribution → advantage) | Step 1 | Introduction |
| Module Motivation Mapping table | Step 1 | Method subsections |
| Experiment plan (comparisons + ablations + demos) | Step 2 | Experiments section |
| Pipeline figure sketch | Step 1 / Step 3 | Method overview + Figure 2 |
| Claim-to-experiment mapping | Step 2 | Abstract, Introduction, Experiments |
| Fallback narrative (if planned) | Counterintuitive Rule 5 | Introduction / Conclusion pivot |
| Rejection-risk table | Counterintuitive Rule 1 | Self-review prioritization |
Reference Navigation
| Topic | Reference File | When to Use |
|---|---|---|
| Story design | story-design.md | Starting a new paper |
| Experiment planning | experiment-planning.md | Before running experiments |
| Timeline | timeline-4week.md | Setting up a writing schedule |
| Figure design | figure-design.md | Designing pipeline/teaser figures |
| Experiment plan template | experiment-plan-template.md | Creating a structured experiment plan |
| Counterintuitive strategy | counterintuitive-planning.md | Increasing acceptance odds with non-obvious planning choices |
Handoff to Presentation
If preparing a conference talk or slide deck, the academic-slides skill guides slide creation from your planning artifacts — including translating your story design and pipeline figure into presentation structure.
© EvoScientist, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 6 other files (references, assets) in skills/paper-planning of EvoScientist/EvoSkills.
- SKILL.md
- assets/experiment-plan-template.md
- references/counterintuitive-planning.md
- references/experiment-planning.md
- references/figure-design.md
- references/story-design.md
- references/timeline-4week.md
Open the folder on GitHubat commit 9a9f8cf
Used in 3 other repositories
We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in EvoScientist/EvoSkills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Paper Planning next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Paper Planning this skillEvoScientist/EvoSkills | 476 | 3 repos | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Academic Researchvoidful/academic-skills | 134 | — | ~887 | Automated safety check: Pass | MIT | |
| Integrity Forensicswanshuiyin/Auto-claude-code-research-in-sleep | 17k | — | ~4.2k | Automated safety check: Notes | MIT | |
| Scholarpeer Econfranklee16/academic-research-skills | 223 | — | ~2k | Automated safety check: Notes | None | |
| Academic Paper Writing PipelineImbad0202/academic-research-skills | 51k | — | ~16k | Automated safety check: Pass | Custom licence | |
| Academic Paper ReviewerImbad0202/academic-research-skills | 51k | — | ~11k | Automated safety check: Pass | Custom licence |
Similar skills
Integrity Forensics
wanshuiyin/Auto-claude-code-research-in-sleep
Run the Anti-Autoresearch integrity-forensics sweep (span-anchored evidence ledger → GPT auditors propose findings → a rules-only reporter that lists every proposal with what the auditor said about…
Scholarpeer Econ
franklee16/academic-research-skills
Multi-agent peer review simulation for finance/economics manuscripts.
Academic Paper Writing Pipeline
Imbad0202/academic-research-skills
Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.
Academic Paper Reviewer
Imbad0202/academic-research-skills
Simulates a journal peer review of a manuscript with a five-seat reviewer panel, an editorial synthesizer and several review modes.
Academic Research Pipeline
Imbad0202/academic-research-skills
Orchestrates a ten-stage academic workflow from research to finished manuscript, including integrity checks, two rounds of peer review and revision.
More from EvoScientist/EvoSkills
All 16 skills in this repoEvomath Tao
EvoScientist/EvoSkills
A skill your agent uses whenever the user submits a non-trivial mathematical claim that needs a rigorous proof or audit.
Paper Figures
EvoScientist/EvoSkills
A skill your agent uses to produce standalone, publication-ready PNG graphics and reproducible matplotlib scripts from tabular data (CSVs or DataFrames).
Experiment Iterative Coder
EvoScientist/EvoSkills
Iterative code refinement through plan → code → evaluate → refine cycles.
Research Survey
EvoScientist/EvoSkills
Generates structured literature survey reports from collected papers using a multi-stage pipeline: outline generation (query-type adaptive) → draft survey → section-by-section expansion → summary…
Paper Navigator
EvoScientist/EvoSkills
Find and read academic papers (S2 + arXiv). An agent skill from EvoScientist/EvoSkills.
Academic Slides
EvoScientist/EvoSkills
A skill your agent uses for creating or refining an academic slide deck and the talk built around it: structuring a conference talk, thesis defense, lab meeting, or paper-to-slides deck; deciding…
Related
Categories
Questions about Paper Planning
What does Paper Planning do?
Guides pre-writing planning for academic papers with 4 structured steps: story design (task-challenge-insight-contribution-advantage), experiment planning (comparisons + ablations), figure design…. Paper Planning is an agent skill from EvoScientist/EvoSkills. Guides pre-writing planning for academic papers with 4 structured steps: story design (task-challenge-insight-contribution-advantage), experiment planning (comparisons + ablations), figure design (pipeline + teaser), and 4-week timeline management.
When should I use Paper Planning?
Paper Planning fits situations like: : user wants to plan a paper before writing; design story/contributions; plan experiments; create figure sketches.
How do I install Paper Planning in Claude Code?
Run `npx skills add EvoScientist/EvoSkills --skill paper-planning -a claude-code`. Or copy the skill folder (skills/paper-planning in EvoScientist/EvoSkills) into .claude/skills/paper-planning in your project. Claude Code loads it when a task matches its description.
How do I install Paper Planning in Codex?
Run `npx skills add EvoScientist/EvoSkills --skill paper-planning -a codex`. Or copy the skill folder (skills/paper-planning in EvoScientist/EvoSkills) into .agents/skills/paper-planning in your project. Codex loads it when a task matches its description.
Can I use Paper Planning in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add EvoScientist/EvoSkills --skill paper-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/paper-planning, .gemini/skills/paper-planning, .github/skills/paper-planning and .opencode/skills/paper-planning in your project.
What does Paper Planning need to run?
SKILL.md names no scripts, command-line tools or credentials: Paper Planning is instructions for the agent only. Its frontmatter pre-approves these tools: write_file, edit_file, read_file, think_tool.
Does Paper Planning access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Paper Planning safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Paper Planning use?
Paper Planning is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Paper Planning use?
About 2.4k tokens (SKILL.md is roughly 9.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.6k tokens, read only when the agent opens those files.
What are the alternatives to Paper Planning?
Skills that share tags, products or a category with Paper Planning: Academic Research (voidful/academic-skills, 134 stars), Integrity Forensics (wanshuiyin/Auto-claude-code-research-in-sleep, 17k stars), Scholarpeer Econ (franklee16/academic-research-skills, 223 stars) and Academic Paper Writing Pipeline (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Paper Planning?
EvoScientist (a GitHub organization) maintains it in EvoScientist/EvoSkills, which has 476 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on September 30, 2026.
Source: EvoScientist/EvoSkills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.