Token导航 LogoToken导航

Agent Skill · 研究检索

manuscript(manuscript 搜索)

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

manuscript 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 44,194。

总安装 930周安装 38GitHub Stars 76下载 298核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/htlin222/dotfiles --skill manuscript

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

manuscript 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于文稿检索、学术写作或内容素材收集场景。通过 npx skills add 命令从指定 GitHub 仓库安装并使用。

安装前建议确认权限范围、维护状态及是否触发联网或文件操作。具体用法可结合原始 README 和仓库内容进一步核验。

来源仓库内路径:skills/manuscript

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/htlin222/dotfiles --skill manuscript;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

manuscript 怎么安装?

在终端执行 npx skills add https://github.com/htlin222/dotfiles --skill manuscript。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

manuscript 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

manuscript 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

manuscript 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

manuscript 用的人多吗?

公开数据是累计安装 930 次,近一周安装 38 次,下载 298 次,GitHub 76 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

manuscript 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
manuscript

manuscript 搜索 · 本页

93076只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Medical Manuscript Writing

Transform manuscripts from data reports into persuasive scientific arguments.

The Core Shift

Stop reporting. Start arguing.

Report ThinkingArgumentation Thinking
"I did X, found Y, concluded Z""There's a problem, current answers fall short, here's a better one"
Paragraphs present dataEvery paragraph advances the argument
Reader sees your lab notebookReader sees your insight

Before writing any paragraph, ask: What role does this play in my argument? If you can't answer, the paragraph doesn't belong — or needs repositioning.

When to Use

  • Writing a new original research manuscript
  • Revising a draft that reads "flat" or "boring"
  • Reviewing a colleague's manuscript for structural issues
  • Preparing a response to reviewer comments
  • Transitioning from thesis/report style to journal style

Master Checklist

Copy and track progress through each section:

Pre-Writing

  • Define your nugget: the single insight that makes your problem solvable
  • Define your one-sentence argument (what gap you fill and why it matters)
  • Write a 3-sentence elevator pitch (problem → insight → result)
  • Identify your target journal and its conventions
  • Outline the logical chain: Gap → Approach → Key Finding → Implication
  • Draft placeholder figures — they are the paper's skeleton
  • Identify your audience (clinicians, methodologists, policy makers?)
  • Write a shitty first draft early — perfection comes in revision

Detailed guidance: references/process.md

Title

  • Condenses the key insight (not just the topic)
  • Searchable — contains main variables, population, and study design
  • Under journal character limit
  • No abbreviations (unless universally recognized like ICU, HIV)

Abstract

  • Follows journal's required structured format (Background/Methods/Results/Conclusions)
  • Background uses Goal → Problem → Solution rhythm
  • Results state primary outcome with effect size and 95% CI
  • Conclusions state the clinical implication, not just the statistical finding
  • No claims absent from the main text
  • Word count within journal limit

Detailed guidance: references/abstract.md

Introduction

  • Opens with a specific clinical dilemma, not a textbook sentence
  • Literature builds a logical chain toward your gap (not a stack of citations)
  • Gap statement is crisp and specific
  • Final paragraph states exact study strategy (data, method, outcome)
  • Every citation serves a purpose (importance, prior limitation, or theoretical basis)

Detailed guidance: references/introduction.md

Methods

  • Organized by research logic, not by tool category
  • Key methodological decisions include justification ("why this method")
  • Sensitivity analyses target your biggest threats to validity
  • Reporting follows a guideline (STROBE, CONSORT, PRISMA, etc.)

Detailed guidance: references/methods.md

Results

  • Opens with a bird's-eye view before any details
  • Baseline characteristics in text limited to clinically relevant differences
  • Presentation order follows research questions, not analysis chronology
  • No interpretation or speculation (no "This suggests..." or "This may be because...")
  • Tables and figures referenced by finding, not narrated line-by-line

Detailed guidance: references/results.md

Discussion

  • First paragraph is a conceptual elevator pitch (finding + clinical picture + significance)
  • Interpretation organized in layers (biological → methodological → clinical)
  • Inconsistent results honestly engaged, not ignored
  • Literature comparison builds your explanatory framework, not a citation list
  • Limitations are balanced: acknowledge → mitigate → contextualize
  • Conclusion states clinical implication, not just statistical summary

Detailed guidance: references/discussion.md

Sentence-Level Polish

  • Subjects are study variables or actions, not passive constructions
  • Each paragraph's first and last sentences carry the main message
  • No hedge stacking ("may possibly potentially suggest...")
  • Eliminated empty adjectives ("interesting", "important", "noteworthy")
  • Read aloud — every sentence flows naturally

Detailed guidance: references/sentence-craft.md

Figures & Tables

  • Every figure has a single take-home message
  • Figure legends are self-contained (method, sample, key stats, abbreviations)
  • Tables show only study-relevant variables (extras go to supplement)
  • Large-sample comparisons use SMD instead of p-values where appropriate

Detailed guidance: references/figures-tables.md

Overall Rhythm

  • Information-dense paragraphs followed by interpretive breathing room
  • No three consecutive paragraphs with the same "found A, p=B, consistent with C" pattern
  • Transitions between sections feel guided, not mechanical
  • Read aloud — if it sounds dull or stilted to you, it reads worse to others

Section Quick Reference

SectionGoalFatal MistakeFix
TitleCondense key insightGeneric topic label ("A Study of X and Y")Include variables + finding direction
AbstractStandalone argumentMissing structured rhythmGoal → Problem → Solution in each sub-section
IntroductionBuild logical case for your studyStarting with "X is a leading cause of death"Open with a specific clinical dilemma
MethodsEarn reader trustListing tools without justificationExplain *why* for key decisions
ResultsPresent facts that advance the argumentSmuggling interpretation ("suggests...")Facts only; interpretation in Discussion
DiscussionProvide conceptual significanceRestating results with p-valuesLead with meaning, not numbers
FiguresDeliver one message per figureCluttered figures without clear takeawayDesign around the take-home message

Common Anti-Patterns

Anti-PatternExampleBetter Approach
Textbook opening"Cancer is a leading cause of death worldwide"Specific clinical dilemma your study addresses
Citation stacking"Smith (2020) found X. Jones (2021) found Y."Synthesize into a logical chain with inline citations
Vague study aim"We aimed to explore the relationship between X and Y""We used [database] with [method] to test [specific hypothesis]"
Lab-notebook ResultsNarrating every row of Table 1Highlight only clinically meaningful differences
Statistical Discussion"HR was 2.4 (95% CI 1.8–3.2, p<0.001)" as Discussion openerLead with conceptual significance, not numbers
Self-destructive LimitationsListing every weakness until the study sounds worthlessAcknowledge → mitigate → contextualize
Hedge stacking"It is possible that this may potentially suggest..."One hedge per claim: "This suggests..."
Empty adjectives"Interestingly, we found..."Show the contrast or surprise directly
Afterthought title"A Study of LDH Levels in ICU Patients"Condense the nugget: "Serial LDH Trajectories Predict 90-Day Mortality in Critically Ill Patients"
No defined nuggetStarting to write without a core argumentDefine the one insight that makes your problem solvable before writing
Rough draft to senior authorSending a messy draft expecting rescuePolish first; let them focus on argument, not grammar

Reviewer Psychology

Reviewers must: (1) summarize your paper, (2) identify strengths, (3) evaluate validity, (4) find weaknesses. Support them:

Reviewer NeedHow to Help
SummarizeCrystal-clear abstract + Discussion opener = easy summary
Identify strengthsExplicit contribution statements in Introduction's final paragraph
Evaluate validitySensitivity analyses with clear reporting in Results
Find weaknessesHonest limitations section (they will find them regardless)

If a reviewer cannot quickly summarize your paper, your structure has failed — not the reviewer.

Detailed guidance: references/process.md

Proofreading Protocol

  • Read for argument flow — does the logic build from Introduction through Conclusion?
  • Read every word, caption, and abbreviation — detail pass
  • Read as a naïve reader — where do you get confused?
  • Read as a hostile reviewer — what would you attack?
  • Verify all numbers in text match their corresponding tables and figures
  • Have at least two co-authors proofread independently
  • Assume your bibliography has errors — verify every citation

Detailed guidance: references/process.md

Quick Scan

Run the built-in scanner to catch mechanical anti-patterns (31 checks, section-aware):

# Full scan
python3 ~/.claude/skills/manuscript/scan-manuscript.py manuscript.md

# Errors only (high confidence)
python3 ~/.claude/skills/manuscript/scan-manuscript.py --severity error manuscript.md

# Check a single section from stdin
cat results.md | python3 ~/.claude/skills/manuscript/scan-manuscript.py --section Results

# JSON output / markdown checklist
python3 ~/.claude/skills/manuscript/scan-manuscript.py --json manuscript.md
python3 ~/.claude/skills/manuscript/scan-manuscript.py --checklist manuscript.md

# List all checks
python3 ~/.claude/skills/manuscript/scan-manuscript.py --list-checks

What it catches (~57% of this skill's scriptable guidance): hedge stacking, empty adjectives, interpretation in Results, textbook openings, vague aims, p-values without CIs, citation stacking (Introduction + Discussion), contractions, duplicate words, tautological acronyms (HIV virus), passive voice ratio, sentence monotony, table/figure narration, statistical Discussion openers, statistical conclusions, mechanical transitions, overclaiming, anthropomorphism, informal language, British/American spelling mix, nominalizations, wordy phrases, redundant modifiers, self-referential filler, sentence sprawl, double negatives, missing reporting guidelines, p-value ordering, monotonous results patterns.

What it cannot catch (~43%): argumentation quality, logical chains, gap specificity, interpretive framework depth, limitation balance. These require human judgment or AI-assisted review.

Related Skills

  • /human-write — Scan for AI-flavored vocabulary
  • /meta-manuscript-assembly — Assemble tables, figures, references for meta-analyses
  • /scientific-figure-assembly — Create multi-panel publication figures
  • /vale — Lint prose for style and grammar
  • /strobe-check — Audit observational studies (cohort, case-control, cross-sectional) against STROBE
  • /prisma-check — Audit systematic reviews and meta-analyses against PRISMA 2020
  • /care-check — Audit case reports against CARE checklist
  • /consort-check — Audit RCTs against CONSORT 2010
  • /tripod-check — Audit prediction models and clinical AI against TRIPOD+AI

平台分布

Codex

34.86%
按下载量换算104

Claude

26.71%
按下载量换算80

Cursor

19.54%
按下载量换算58

Gemini CLI

9.13%
按下载量换算27

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills