Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问clear审计提醒

academic-research-writer学术研究作家

Agent Skill

academic-research-writer 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

18,981

周安装

807

GitHub Stars

6

下载量

6,650
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:academic-research-writer(学术研究作家)
来源仓库:https://github.com/endigo/claude-skills
仓库路径:skills/academic-research-writer
安装命令:
npx skills add https://github.com/endigo/claude-skills --skill academic-research-writer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/endigo/claude-skills --skill academic-research-writer

简介

具有同行评审来源、IEEE 引文和学术严谨性的学术研究文件。

  • 支持多种文档类型:具有标准学术结构的研究论文、文献综述、学位论文、会议论文、技术报告
  • 将 Google Scholar、IEEE Xplore、PubMed、ACM Digital Library 和 arXiv 的来源发现与同行评审可信度和作者凭证的内置验证相集成
  • 自动生成带有正确引文编号的 IEEE 格式参考文献,处理期刊文章、会议论文、书籍、论文、专利和在线资源
  • 强制执行学术写作标准,包括正式语气、用于源代码集成的信号短语、正确的释义以及定稿前的全面质量保证检查表

SKILL.md

Academic Research Writer

This skill enables creation of high-quality academic research documents with proper scholarly standards, verified peer-reviewed sources, and IEEE-format citations.

Core Principles

  1. Academic Rigor: Follow scholarly writing conventions and maintain objectivity
  2. Source Verification: Use only peer-reviewed, credible academic sources
  3. Proper Citation: Generate accurate IEEE-format references
  4. Research Integrity: Ensure all claims are supported by verified sources

Workflow

1. Understanding Requirements

Clarify the research document type and requirements:

  • Document type (research paper, literature review, thesis chapter, etc.)
  • Research topic and scope
  • Target length
  • Specific guidelines (institution, journal, conference)
  • Required sections
  • Deadline considerations

2. Research Planning

Develop a research strategy:

  • Identify key research questions
  • Define search terms and keywords
  • Determine relevant academic databases (Google Scholar, IEEE Xplore, PubMed, ACM Digital Library, ScienceDirect)
  • Establish inclusion/exclusion criteria for sources
  • Plan document structure

3. Source Discovery and Verification

Finding Sources:

Use web_search to find peer-reviewed sources from:

  • Google Scholar (scholar.google.com)
  • IEEE Xplore (ieeexplore.ieee.org)
  • PubMed (pubmed.ncbi.nlm.nih.gov)
  • ACM Digital Library (dl.acm.org)
  • arXiv (arxiv.org) - for preprints in relevant fields
  • Domain-specific databases

Search Strategy:

  • Start with broad searches: "machine learning healthcare"
  • Refine with specific terms: "deep learning medical diagnosis 2023"
  • Use quotation marks for exact phrases: "convolutional neural networks"
  • Combine terms strategically
  • Search for recent publications (last 5-7 years unless historical context needed)

Verification Checklist:

For each source, verify:

  • Published in peer-reviewed journal or conference
  • Author credentials and institutional affiliation
  • Publication venue reputation
  • Citation count (higher indicates impact)
  • Methodology soundness
  • Relevance to research question

Red Flags:

  • Predatory journals (check journalquality.info or beallslist)
  • Lack of peer review process
  • No institutional affiliation
  • Suspicious publication practices
  • Pay-to-publish without legitimate review

4. Document Structure

Create documents following this standard academic structure:

Research Paper:

  1. Title
  2. Abstract (150-250 words)
  3. Keywords (5-7 terms)
  4. Introduction

- Background and context - Problem statement - Research objectives - Contribution statement - Paper organization

  1. Literature Review / Related Work

- Theoretical framework - Previous research synthesis - Research gap identification

  1. Methodology (if applicable)

- Research design - Data collection - Analysis approach

  1. Results / Findings
  2. Discussion

- Interpretation - Implications - Limitations

  1. Conclusion

- Summary of findings - Future work

  1. References (IEEE format)

Literature Review:

  1. Title
  2. Abstract
  3. Introduction
  4. Review Methodology
  5. Thematic Sections (organized by themes/topics)
  6. Discussion and Synthesis
  7. Conclusion
  8. References

5. Writing Guidelines

Academic Tone:

  • Use formal, objective language
  • Write in third person (avoid "I" or "we" unless methodologically appropriate)
  • Use precise technical terminology
  • Maintain neutral stance (present multiple perspectives)
  • Use hedging language appropriately ("suggests," "indicates," "may")

Paragraph Structure:

  • Topic sentence
  • Supporting evidence with citations
  • Analysis and interpretation
  • Transition to next point

Citation Integration:

  • Introduce sources with context
  • Use signal phrases ("According to Smith et al. [1]...", "Research by Jones [2] demonstrates...")
  • Balance direct quotations (use sparingly) with paraphrasing
  • Cite after every factual claim from external sources
  • Use citation numbers in square brackets [1], [2], [3]

Avoid:

  • Plagiarism (always paraphrase and cite)
  • Unsupported claims
  • Casual or colloquial language
  • Personal opinions without evidence
  • Excessive quotations
  • Wikipedia or non-academic sources

6. IEEE Reference Format

Generate references in IEEE format following these patterns:

Journal Article:

[1] A. Author, B. Author, and C. Author, "Title of article," Journal Name, vol. X, no. Y, pp. ZZ-ZZ, Month Year.

Conference Paper:

[2] A. Author and B. Author, "Title of paper," in Proc. Conference Name, City, Country, Year, pp. ZZ-ZZ.

Book:

[3] A. Author, Title of Book, Edition. City, State: Publisher, Year.

Book Chapter:

[4] A. Author, "Title of chapter," in Book Title, Edition, Ed. City, State: Publisher, Year, pp. ZZ-ZZ.

Website/Online:

[5] A. Author. "Title of webpage." Website Name. URL (accessed Month Day, Year).

Technical Report:

[6] A. Author, "Title," Institution, City, State, Rep. Number, Month Year.

Thesis/Dissertation:

[7] A. Author, "Title," Ph.D. dissertation, Dept. Abbrev., University, City, State, Year.

Patent:

[8] A. Inventor, "Title," Country Patent Number, Month Day, Year.

Standards:

[9] Title of Standard, Standard Number, Year.

Key IEEE Rules:

  • Number references consecutively in order of appearance
  • Use square brackets [1], [2], [3]
  • For multiple authors: list all if ≤6; use "et al." if >6
  • Use initials for first/middle names
  • Abbreviate journal names per IEEE standards
  • Include DOI when available
  • Maintain consistent formatting

7. Quality Assurance

Before finalizing, verify:

Content:

  • Clear research question/objective
  • Logical flow and organization
  • Adequate source coverage (minimum 15-20 for research paper)
  • All sources verified as peer-reviewed
  • Claims supported by citations
  • Methodology clearly explained (if applicable)
  • Results/findings clearly presented
  • Limitations acknowledged

Technical:

  • IEEE reference format correct
  • All in-text citations match reference list
  • No missing references
  • Consistent citation numbering
  • Proper figure/table captions and numbering

Writing Quality:

  • Academic tone maintained
  • Clear and concise language
  • No grammatical errors
  • Transitions between sections smooth
  • Abstract accurately summarizes paper

Implementation Approach

When creating an academic document:

  1. Use web_search extensively to find peer-reviewed sources
  2. Verify each source's academic credibility
  3. Extract relevant information and synthesize findings
  4. Write in formal academic style
  5. Integrate citations naturally throughout
  6. Generate complete IEEE reference list
  7. Create document using appropriate tool (docx, pdf, or markdown)

Reference Resources

For detailed guidance on specific aspects:

Output Format

Create documents as:

  • DOCX: For full research papers, theses, dissertations (use docx skill)
  • PDF: For final submission versions (use pdf skill)
  • Markdown: For drafts, literature reviews, or online publication

Notes

  • Always prioritize source quality over quantity
  • Recent sources (last 5-7 years) preferred unless historical context required
  • Maintain research integrity throughout
  • When in doubt about a source, search for additional verification
  • Use web_fetch to access full articles when available

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

28.24%
按下载量换算1,878

OpenCode

19.78%
按下载量换算1,315

Gemini CLI

18%
按下载量换算1,197

Antigravity

11.45%
按下载量换算761

Codex

7.66%
按下载量换算509

Cursor

3.59%
按下载量换算239

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。

来源信息

继续浏览同类 Skills