Manuscript Writing logo

Manuscript Writing

Community
neuromechanist
manuscript-writing

Use this skill for "write a paper", "draft manuscript", "write introduction", "write methods section", "write results", "write discussion", "write abstract", "structure a paper", "academic writing", "write for journal", or when the user wants to draft or revise sections of an academic manuscript.

Overview

Publisherneuromechanist
Repositoryresearch-skills
Skill namemanuscript-writing
Stars
51
Forks
9
Bundled files
2
LicenseBSD-3-Clause
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by neuromechanist on GitHub. Read the source before you install it.

Installation

Install the Manuscript Writing AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/neuromechanist/research-skills/tree/main/plugins/manuscript/skills/manuscript-writing
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/neuromechanist/research-skills.git /tmp/research-skills
mkdir -p .claude/skills
cp -r /tmp/research-skills/plugins/manuscript/skills/manuscript-writing .claude/skills/manuscript-writing
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Manuscript Writing in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Manuscript Writing on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Manuscript Writing is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Academic Manuscript Writing

Guide the drafting and revision of academic manuscripts following journal conventions and scientific writing best practices.

When to Use

  • Drafting a new manuscript from scratch
  • Writing or revising specific sections (Introduction, Methods, Results, Discussion)
  • Structuring a paper from experimental results
  • Converting a conference paper to a journal submission
  • Responding to reviewer comments with revised text

Manuscript Structure

Standard IMRAD Format

SectionPurposeTenseLength Guide
TitleConvey main findingN/A10-15 words
AbstractSelf-contained summaryPast (methods/results), Present (conclusions)150-300 words
IntroductionContext, gap, hypothesisPresent (known facts), Past (prior work)3-5 paragraphs
MethodsReproducibilityPastAs needed
ResultsReport findingsPastParallel to Methods
DiscussionInterpret findingsPresent (interpretation), Past (what was found)4-6 paragraphs
ConclusionKey takeawaysPresent1-2 paragraphs

Section-by-Section Guidance

Introduction

Structure as a funnel:

  1. Broad context - Establish the field and importance (1-2 paragraphs)
  2. Narrow focus - What is known about the specific topic (1-2 paragraphs)
  3. Gap statement - What remains unknown or problematic
  4. Objective/hypothesis - What this paper addresses and how
Methods
  • Enough detail for replication
  • Subsections mirror Results sections
  • Include: participants/subjects, materials, procedures, analysis
  • Statistical methods: specify tests, software, significance thresholds
  • Ethics: IRB/IACUC approval statement
Results
  • Present findings without interpretation
  • Start each subsection with the analysis performed, then the outcome
  • Report effect sizes, confidence intervals (not just p-values)
  • Reference figures and tables in order
  • Use "significant" only for statistical significance
Discussion

Structure:

  1. Summary of key findings (1 paragraph)
  2. Interpretation in context of prior literature (2-3 paragraphs)
  3. Limitations (1 paragraph, honest but not self-defeating)
  4. Future directions (1 paragraph)
  5. Conclusion (1 paragraph)

Writing Principles

Clarity

  • Active voice with the authors as the actor and the named noun instead of a pronoun ("We measured..." not "Measurements were taken..."; see Habits to avoid while drafting); follow the journal where it prefers passive Methods
  • Define abbreviations on first use
  • Avoid jargon unless writing for a specialist audience

Precision

  • Quantify claims ("increased by 23%" not "significantly increased")
  • Cite sources for factual claims
  • Distinguish correlation from causation
  • Use hedging appropriately ("suggests" vs "proves")

Flow

  • Each paragraph: topic sentence, evidence, interpretation
  • Transitions between paragraphs connect ideas
  • Logical progression within and across sections
  • Consistent terminology (don't alternate between synonyms for key concepts)

Habits to avoid while drafting

These habits make research prose read as machine-written, and reviewers and editors notice them. Avoid them while drafting; the humanizer pass (patterns 30 to 45) then catches what slips through. The quoted phrases are examples of each habit, not the full list; a sentence that does the same job in other words breaks the same rule.

  • Show, do not announce. State the limitation or the result and let it stand. Do not certify your own honesty or rigor ("and we say so", "we say it first", "to be transparent", "we are careful to").
  • Say it once. Each sentence adds a fact. Drop tails that restate the purpose (", so a gain must come from what the tags say"), closing sentences that only repeat the paragraph (a sentence that links to an aim or states the gap stays), and a second gloss of a defined term (define it again only in each separately read document). Lead with a purpose ("To separate X from Y, ...") only where a reader would ask why.
  • Name who acts. Write "We registered the test before seeing any fMRI value", not "The test was registered" or "Hypothesis 1B tests ..."; results predict, differ, or agree, and do not "say", "tell", or "decide". An aim can still be the topic of a sentence ("Aim 2 has two hypotheses"). Follow the journal where it prefers passive Methods.
  • Name the noun. When the referent is a sentence back or two nouns could fit, repeat the noun ("CLIP's prediction", not "its prediction"); "this" needs a noun that names something in the sentence just before ("this test"). A pronoun is fine when its referent is the subject of the same clause.
  • Literal claims, not slogans. No mirrored contrasts ("fMRI shows where, EEG shows when"), contest metaphors ("beat the null"), colon reveals ("The answer is simple: ..."), or verbs of standing ("rests on", "reads as").
  • Answer an objection where it arises. Do not concede and rebut in every paragraph ("X is not the only limit, but ...").
  • Plain time and scope. Use "now" or "currently" only to contrast with a stated earlier version or where literal ("currently recruiting"), and state a real constraint ("only", "never") once.
  • One idea per sentence. Split chains of "and"; list results strongest first, each with its label.

Citations

  • Cite primary sources, not reviews (when possible)
  • Recent citations show awareness of current literature
  • Cite competing or contradictory findings
  • Self-citation should be relevant, not gratuitous

Revision Checklist

After drafting, check:

  • Abstract accurately reflects the paper content
  • Introduction gap statement matches the study objective
  • Methods are sufficient for replication
  • Results match Methods (parallel structure)
  • Discussion addresses all major findings
  • Figures are referenced in text in order
  • All abbreviations defined on first use
  • References complete and consistently formatted
  • Word/page count within journal limits
  • Run manuscript:humanizer as a final natural-writing pass (strips AI tells like significance inflation, em-dashes, "evolving landscape" filler, rule-of-three padding) before review

Additional Resources

  • Reference: references/section-templates.md - Templates for each manuscript section
  • Reference: references/revision-response.md - How to write point-by-point responses to reviewers
  • Sister skill: manuscript:humanizer (invoke through the host's skill-invocation mechanism) - Removes 45 categories of AI-writing tells, including sentence-shape tells, hidden actors, and unanchored pronouns in research prose, while respecting academic conventions (e.g., passive voice in Methods, hedging in Discussion). Run after drafting and before peer review.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Manuscript Writing AI skill do?

Use this skill for "write a paper", "draft manuscript", "write introduction", "write methods section", "write results", "write discussion", "write abstract", "structure a paper", "academic writing", "write for journal", or when the user wants to draft or revise sections of an academic manuscript.

Why use Manuscript Writing on TypingMind?

Because you install it once and use it with any model. Manuscript Writing is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Manuscript Writing in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/neuromechanist/research-skills/tree/main/plugins/manuscript/skills/manuscript-writing. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Manuscript Writing?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Manuscript Writing?

As many as you like. As long as a model supports skills, you can use Manuscript Writing with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Manuscript Writing AI skill free?

Yes. It is published on GitHub by neuromechanist under the BSD-3-Clause license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇