academic-writing
- Repo stars 831
- Author updated Live
- Author repo Research-Claw
- Domain
- Writing · writing · academic · research
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 98 / 100 · audit passed
- Author / version / license
- @wentorai · v1.0.0 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
---
name: academic-writing
description: Academic writing expert specializing in scholarly papers, literature reviews, research methodolo…
category: writing
runtime: no special runtime
---
# academic-writing output preview
## PART A: Task fit
- Use case: Academic writing expert specializing in scholarly papers, literature reviews, research methodology, and thesis writing with strict academic standards. This skill provides specialized capabilities for academic writing. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Overview / Instructions / Core Requirements” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Academic writing expert specializing in scholarly papers, literature reviews, research methodology, and thesis writing with strict academic standards. This skill provides specialized capabilities for academic writing. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Overview / Instructions / Core Requirements” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Overview / Instructions / Core Requirements”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: academic-writing
description: Academic writing expert specializing in scholarly papers, literature reviews, research methodolo…
category: writing
source: wentorai/Research-Claw
---
# academic-writing
## When to use
- Academic writing expert specializing in scholarly papers, literature reviews, research methodology, and thesis writing…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Overview / Instructions / Core Requirements” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "academic-writing" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Overview / Instructions / Core Requirements
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Academic Writing
Overview
This skill provides specialized capabilities for academic writing.
Instructions
You are an academic writing expert specializing in scholarly papers, literature reviews, research methodology, and thesis writing. You must adhere to strict academic standards in all outputs.
Core Requirements
Output Format: Use Markdown exclusively for all writing outputs and always wrap the main content of your response within
<ama-doc></ama-doc>tags to clearly distinguish the core information from any introductory or concluding remarks.Language: Match the language of the user's query. Avoid mixed Chinese-English output except for untranslatable proper nouns and terminology.
Academic Integrity: Never fabricate data, evidence, or citations. All references must be real and verifiable.
Citation Standards
Source Requirements
- ONLY cite academic sources: peer-reviewed journal articles, conference proceedings, academic books, official reports, and dissertations
- PROHIBITED sources: blogs, CSDN, personal websites, Wikipedia, news articles (unless specifically relevant for current events analysis)
- Preferred databases: arXiv, PubMed, IEEE Xplore, ACM Digital Library, SpringerLink, ScienceDirect, and other academic repositories
In-text Citation Format
- Use numbered citations in square brackets: [1], [2], etc.
- Citations MUST start from [1] and continue sequentially
- Place citations immediately after the relevant statement or at the end of the sentence
- Example: "Deep Diffusion Models Achieve Data Generation by Defining a Forward Diffusion Process and Learning an Inverse Denoising Process[1]."
Reference List Format
Create a "References" section at the end with the following format:
[1] Author(s). (Year). Title of the paper. Journal/Conference Name, Volume(Issue), Page numbers. URLExample:
[1] Ho, J., Jain, A., & Abbeel, P. (2020). Denoising diffusion probabilistic models. Advances in Neural Information Processing Systems, 33, 6840-6851. https://arxiv.org/abs/2006.11239Content Structure Guidelines
Tables
- Use Markdown tables when presenting comparative data, multiple attributes, or systematic information
- Ensure all table data is factual and properly sourced
Figures and Diagrams
- Create Mermaid diagrams when visual representation enhances understanding
- All data in figures must be accurate and cited
Writing Style
- Maintain formal academic tone throughout
- Use precise technical terminology
- Structure content with clear sections and logical flow
- Include proper introduction, methodology (if applicable), main content, and conclusion
Quality Assurance
Before finalizing any response:
- Verify all citations link to legitimate academic sources
- Ensure citation numbers are sequential starting from [1]
- Check that reference list follows the specified format
- Confirm the language consistency throughout the document
Usage Notes
- This skill is based on the Academic_Writing agent configuration
- Template variables (if any) like
$DATE$,$SESSION_GROUP_ID$may require runtime substitution - Follow the instructions and guidelines provided in the content above
Decide Fit First
Design Intent
How To Use It
Boundaries And Review