Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
Guide to writing effective research paper introductions. An agent skill from wentorai/research-plugins.
Install Introduction Writing Guide
$ npx skills add wentorai/research-plugins --skill introduction-writing-guide -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install wentorai/research-plugins introduction-writing-guide --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/wentorai/research-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/writing/composition/introduction-writing-guide .claude/skills/introduction-writing-guide && 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 "introduction-writing-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/composition/introduction-writing-guide into .claude/skills/introduction-writing-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "introduction-writing-guide", 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/wentorai/research-plugins/tree/main/skills/writing/composition/introduction-writing-guideType 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 wentorai/research-plugins --skill introduction-writing-guide -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install wentorai/research-plugins introduction-writing-guide --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/writing/composition/introduction-writing-guide .agents/skills/introduction-writing-guide && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "introduction-writing-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/composition/introduction-writing-guide into .agents/skills/introduction-writing-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "introduction-writing-guide", 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 wentorai/research-plugins --skill introduction-writing-guide -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install wentorai/research-plugins introduction-writing-guide --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/writing/composition/introduction-writing-guide .cursor/skills/introduction-writing-guide && 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 "introduction-writing-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/composition/introduction-writing-guide into .cursor/skills/introduction-writing-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "introduction-writing-guide", 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/wentorai/research-plugins.git --path skills/writing/composition/introduction-writing-guide--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 wentorai/research-plugins --skill introduction-writing-guide -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install wentorai/research-plugins introduction-writing-guide --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/writing/composition/introduction-writing-guide .gemini/skills/introduction-writing-guide && 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 "introduction-writing-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/composition/introduction-writing-guide into .gemini/skills/introduction-writing-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "introduction-writing-guide", 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 wentorai/research-plugins introduction-writing-guideInstalls 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 wentorai/research-plugins --skill introduction-writing-guide -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/writing/composition/introduction-writing-guide .github/skills/introduction-writing-guide && 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 "introduction-writing-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/composition/introduction-writing-guide into .github/skills/introduction-writing-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "introduction-writing-guide", 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 wentorai/research-plugins --skill introduction-writing-guide -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install wentorai/research-plugins introduction-writing-guide --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/writing/composition/introduction-writing-guide .opencode/skills/introduction-writing-guide && 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 "introduction-writing-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/composition/introduction-writing-guide into .opencode/skills/introduction-writing-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "introduction-writing-guide", 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
introduction-writing-guide- GitHub stars
- 298
- Used in
- 1 other repo
- Token cost
- ~1.7k tokens
- SKILL.md length
- 451 words
- Files
- 1
- Skills in repo
- 405
- Repo updated
- First seen
- Licence
- MIT
At a glance
Guide to writing effective research paper introductions. An agent skill from wentorai/research-plugins.
- Research & Science work in your project
- SKILL.md covers The CARS Model, Move 1: Establishing a Territory, Move 2: Establishing a Niche and Move 3: Occupying the Niche, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Introduction Writing Guide is an agent skill from wentorai/research-plugins. Guide to writing effective research paper introductions
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science. The repository describes itself as: 350+ academic research skills, MCP configs, and plugins for Research-Claw and AI agents. The licence is MIT.
When your agent uses it
- Research & Science work in your project
Example prompts
- “/introduction-writing-guide”
What it can do on your machine
Read from SKILL.md and the folder at commit bf44b3c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
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
Introduction Writing Guide loads about 1.7k tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 451 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 wentorai/research-plugins at commit bf44b3c, republished under its MIT licence (© wentorai). 451 words, ~1,709 tokens.
Download SKILL.mdSave it as
.claude/skills/introduction-writing-guide/SKILL.md (or your agent's skills folder).- name
- introduction-writing-guide
- description
- Guide to writing effective research paper introductions
Introduction Writing Guide
Write compelling research paper introductions using the CARS (Create A Research Space) model with structured approaches for establishing context, identifying gaps, and motivating your study.
The CARS Model
John Swales' Create A Research Space (CARS) model is the most widely used framework for structuring academic introductions. It consists of three rhetorical "moves":
| Move | Purpose | Typical Length |
|---|---|---|
| Move 1: Establishing a territory | Show the research area is important and active | 2-4 paragraphs |
| Move 2: Establishing a niche | Identify a gap, question, or problem | 1-2 paragraphs |
| Move 3: Occupying the niche | State what your paper does to address the gap | 1-2 paragraphs |
Move 1: Establishing a Territory
Strategy 1A: Claiming Centrality
Signal that the topic is important, interesting, or well-established:
Pattern phrases:
- "X has attracted considerable attention in recent years..."
- "The role of X in Y is well established..."
- "X is a fundamental aspect of..."
- "Understanding X is critical for..."
- "Recent advances in X have transformed..."Strategy 1B: Making Topic Generalizations
Summarize the current state of knowledge:
Pattern phrases:
- "Previous studies have demonstrated that..."
- "It is widely accepted that X leads to Y..."
- "Several approaches have been proposed to address X, including..."
- "Research in this area has traditionally focused on..."Strategy 1C: Reviewing Previous Research
Cite specific studies to build the scholarly context:
Example paragraph:
"Smith et al. (2020) demonstrated that X improves Y by 30%.
Building on this finding, Jones (2021) extended the approach to Z domain,
reporting similar gains. Meanwhile, Chen and Lee (2022) proposed an
alternative framework that addresses the scalability limitations of
earlier methods."Tips for Move 1:
- Funnel from broad to narrow: start with the general field, then narrow to your specific topic
- Cite 10-20 papers across Move 1 (varies by field)
- Balance classic/foundational references with recent work
- Use present tense for established knowledge, past tense for specific findings
Move 2: Establishing a Niche
This is the most critical move. You must convince the reader that there is a problem worth solving.
Strategy 2A: Counter-Claiming (Challenging Previous Work)
Pattern phrases:
- "However, these approaches suffer from..."
- "Despite these advances, X remains poorly understood..."
- "A major limitation of existing methods is..."
- "These findings have been contradicted by..."Strategy 2B: Indicating a Gap
Pattern phrases:
- "To date, no study has examined..."
- "Little attention has been paid to..."
- "The relationship between X and Y has not been explored..."
- "A comprehensive analysis of X is still lacking..."Strategy 2C: Raising a Question
Pattern phrases:
- "An open question is whether X can be applied to..."
- "It remains unclear how X affects Y under conditions Z..."
- "This raises the question of..."Strategy 2D: Continuing a Tradition
Pattern phrases:
- "Following the approach of Smith (2020), we extend..."
- "Building on recent advances in X, this paper..."Tips for Move 2:
- The gap must be clearly linked to the context established in Move 1
- Do not criticize previous work too harshly; use hedging language
- The gap must be specific enough that your paper can plausibly fill it
Show full SKILL.md (176 more words)Show less
Move 3: Occupying the Niche
Strategy 3A: Outlining Purposes
Pattern phrases:
- "In this paper, we propose..."
- "The present study aims to..."
- "This work introduces a novel approach to..."
- "We address this gap by..."Strategy 3B: Announcing Principal Findings
Pattern phrases:
- "Our results demonstrate that..."
- "We show that X outperforms Y by Z%..."
- "The key finding is that..."Strategy 3C: Indicating Article Structure
Example:
"The remainder of this paper is organized as follows. Section 2
reviews related work. Section 3 describes our methodology. Section 4
presents experimental results. Section 5 discusses implications and
limitations. Section 6 concludes."Complete Introduction Template
[Move 1A: Centrality claim - 1-2 sentences]
[Topic] is a critical challenge in [field], with applications
in [area 1], [area 2], and [area 3].
[Move 1B-1C: Background and review - 2-3 paragraphs]
Previous work has established that [known fact]. Smith et al. (2020)
showed [finding 1]. Jones (2021) extended this to [finding 2].
More recently, Chen (2022) demonstrated [finding 3].
[Move 2: Gap identification - 1 paragraph]
However, existing approaches have several limitations. First, [limitation 1].
Second, [limitation 2]. To date, no work has addressed [specific gap].
[Move 3A: Purpose statement - 1-2 sentences]
In this paper, we propose [method/framework] to address [gap].
Our approach differs from prior work in [key difference].
[Move 3B: Key findings - 1-2 sentences]
Our experiments on [benchmark] demonstrate that [main result],
achieving [quantitative improvement] over the state of the art.
[Move 3C: Structure outline - optional, 1-2 sentences]
The rest of this paper is organized as follows...Common Mistakes to Avoid
| Mistake | Problem | Fix |
|---|---|---|
| Too broad opening | "Since the dawn of time..." | Start at the field level, not civilization level |
| No clear gap | Reader does not understand why the paper is needed | State the gap explicitly in 1-2 sentences |
| Overpromising | Claims too broad relative to actual contribution | Use hedging: "we investigate" not "we solve" |
| Citing too few papers | Appears unaware of related work | Cite 15-25 papers in a typical introduction |
| Too long | Buries the contribution | Aim for 1-2 pages (conference) or 2-4 pages (journal) |
| Jargon overload | Inaccessible to non-specialist reviewers | Define key terms on first use |
Discipline-Specific Variations
- STEM: Move 3B (findings preview) is common; quantitative results often stated in the introduction
- Social Sciences: More extensive literature review in Move 1; theoretical framing is expected
- Humanities: Move 2 often involves interpretive questions rather than empirical gaps; longer introductions are acceptable
- Medical/Clinical: Often follows IMRAD strictly; hypothesis stated explicitly in Move 3
© wentorai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/writing/composition/introduction-writing-guide of wentorai/research-plugins.
Open the folder on GitHubat commit bf44b3c
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in wentorai/research-plugins, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Introduction Writing Guide 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 |
|---|---|---|---|---|---|---|
| Introduction Writing Guide this skillwentorai/research-plugins | 298 | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Last30daysmvanhorn/last30days-skill | 64k | — | ~7.9k | Automated safety check: Notes | MIT |
Similar skills
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
More from wentorai/research-plugins
All 405 skills in this repoAbstract Writing Guide
wentorai/research-plugins
Craft structured research abstracts that maximize clarity and journal acceptance
Academic Citation Manager
wentorai/research-plugins
Manage academic citations across BibTeX, APA, MLA, and Chicago formats
Academic Paper Summarizer
wentorai/research-plugins
Summarize academic papers with structured extraction of key elements
Academic Study Methods
wentorai/research-plugins
Evidence-based study techniques for academic learning and retention
Academic Tone Guide
wentorai/research-plugins
Adjust writing tone and register for academic audiences and venues
Academic Translation Guide
wentorai/research-plugins
Academic translation, post-editing, and Chinglish correction guide
Related
Categories
Questions about Introduction Writing Guide
What does Introduction Writing Guide do?
Guide to writing effective research paper introductions. An agent skill from wentorai/research-plugins. Introduction Writing Guide is an agent skill from wentorai/research-plugins.
When should I use Introduction Writing Guide?
Introduction Writing Guide fits situations like: research & Science work in your project.
How do I install Introduction Writing Guide in Claude Code?
Run `npx skills add wentorai/research-plugins --skill introduction-writing-guide -a claude-code`. Or copy the skill folder (skills/writing/composition/introduction-writing-guide in wentorai/research-plugins) into .claude/skills/introduction-writing-guide in your project. Claude Code loads it when a task matches its description.
How do I install Introduction Writing Guide in Codex?
Run `npx skills add wentorai/research-plugins --skill introduction-writing-guide -a codex`. Or copy the skill folder (skills/writing/composition/introduction-writing-guide in wentorai/research-plugins) into .agents/skills/introduction-writing-guide in your project. Codex loads it when a task matches its description.
Can I use Introduction Writing Guide 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 wentorai/research-plugins --skill introduction-writing-guide -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/introduction-writing-guide, .gemini/skills/introduction-writing-guide, .github/skills/introduction-writing-guide and .opencode/skills/introduction-writing-guide in your project.
What does Introduction Writing Guide need to run?
SKILL.md names no scripts, command-line tools or credentials: Introduction Writing Guide is instructions for the agent only.
Does Introduction Writing Guide 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 Introduction Writing Guide 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 Introduction Writing Guide use?
Introduction Writing Guide is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Introduction Writing Guide use?
About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Introduction Writing Guide?
Skills that share tags, products or a category with Introduction Writing Guide: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Introduction Writing Guide?
wentorai (a GitHub user) maintains it in wentorai/research-plugins, which has 298 GitHub stars. The repository holds 405 skills in this directory. The repository was last updated on June 19, 2026.
Source: wentorai/research-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.