DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to map a paper's chapter structure through guided dialogue with Academic Research Skills

Use the /ars-plan skill to turn a rough paper idea into a chapter outline through Socratic questions.

  • Top pick
  • Research
  • Intermediate
  • 30 minutes
  • From the README
  • Claude Code

Who it is forA researcher who has a paper idea or data but no clear section plan yet and wants questions that force clear thinking about the argument.

The problemStarting a paper from a blank page is slow, and an unstructured outline often hides gaps in the argument.

The outcomeA chapter-by-chapter paper structure that you have reviewed and confirmed, built from your own answers.

What you need first

  • Claude Code CLI, VS Code, or JetBrains with the plugin marketplace available (plugin install needs v3.7.0+ of this repo)
  • An Anthropic API key set up as described in docs/SETUP.md
  • Optional: Pandoc or tectonic for DOCX or PDF output, per docs/SETUP.md
  • For the Claude Science path: a Claude Science account and this repo at v3.14.0+

Steps

  1. Run /plugin marketplace add Imbad0202/academic-research-skills
  2. Run /plugin install academic-research-skills
  3. Run /ars-plan in Claude Code.
  4. Describe the paper you are working on and answer the Socratic questions as they come.
  5. Review the chapter structure ARS proposes and change anything that does not match your argument.

Prompt for your agent

Using the repo Imbad0202/academic-research-skills installed as a Claude Code plugin, run /ars-plan on this paper description: <paper description>. Expected output: a chapter-level paper structure reached through Socratic questions. Verify that each chapter maps to a point in my own answers before accepting it.

Caveat. The README says AI is a copilot and the author decides the question, method and claims, so treat the proposed structure as a draft to revise.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page