Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add HuiyuLi-2000/Chinese-Grant-Writer-Skills --skill fund-literature-review-writergit clone --depth 1 https://github.com/HuiyuLi-2000/Chinese-Grant-Writer-SkillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/huiyuli-2000/chinese-grant-writer-skills/fund-literature-review-writer)<a href="https://agentmods.dev/skills/huiyuli-2000/chinese-grant-writer-skills/fund-literature-review-writer"><img src="https://agentmods.dev/badge/skills/huiyuli-2000/chinese-grant-writer-skills/fund-literature-review-writer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/huiyuli-2000/chinese-grant-writer-skills/fund-literature-review-writer"><img src="https://agentmods.dev/badge/skills/huiyuli-2000/chinese-grant-writer-skills/fund-literature-review-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 77 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 101 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00068 | $0.02966 |
| Opus 5 | $0.00034 | $0.01483 |
| Sonnet 5 | $0.00014 | $0.00593 |
| Haiku 4.5 | $0.00007 | $0.00297 |
Grade A, and why
fund-literature-review-writer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NSFC 文献综述与文献评述写作技能
核心定位
本技能不是"写文献"，而是将文献转化为"NSFC研究论证结构的一部分"。
在用户已有研究构想基础上，学习NSFC成功项目中的"文献综述—文献评述"组织方式，对文献部分进行学术化重构、逻辑组织优化、批判性归纳、面向NSFC表达体系的规范化输出。
触发条件
当用户需要撰写以下内容时触发：
- NSFC申请书的"1.2 国内外研究现状及发展动态分析"
- NSFC申请书的"文献综述"部分
- NSFC申请书的"文献评述"部分
- 用户明确要求"写文献综述"、"写文献评述"、"写研究现状"
核心原则
- 不预设固定结构：文献综述的结构从16本NSFC成功本子中"学习出来"，不是"写死出来"
- 不文献摘要堆叠：禁止文献摘要式输出，文献必须融入论证
- 不脱离NSFC语境：文献服务NSFC研究论证结构
- 强调结构归纳能力：从本子中归纳组织逻辑，不固化模板
- 强调批判性评述能力：文献评述是结构性判断，不是总结
- 强调文献服务研究问题能力：文献→研究问题/方法/创新的完整论证链
技能范围
本技能只负责 NSFC 申请书中立项依据的 1.2 国内外研究现状及发展动态分析 + 文献评述 部分。需读取用户研究构想以确保文献服务研究论证。
知识库引用
执行本技能前，必须读取以下知识库文件：
knowledge_base/
-
literature_review_style_guide.md：文献综述写作风格指南- 文献综述的整体叙事逻辑
- 主题划分策略（4种方式）
- 段落组织规范（论证功能，非固定句式）
- 文献引用格式
- 文献间连接词使用规律
- 表格使用规范
- 综述→评述的过渡方式
- 批判性表达规律
- 字数规范
-
literature_review_patterns.md：文献综述组织逻辑范式- 五种项目类型的典型文献综述组织
- 方法型/机制型/系统型文献组织差异
- 文献群的构建逻辑
- 文献→研究问题/方法/创新映射模式
- 文献评述的4种批判性判断类型
- 文献组织的选择决策树
-
literature_mapping_rules.md：文献→研究问题/方法/创新映射规则- 文献→研究问题映射规则
- 文献→方法合理性映射规则
- 文献→创新合理性映射规则
- 与用户研究构想的对齐机制
references/
info_form.md：用户输入信息表output_skeletons.md：输出骨架（论证功能，非固定模板）validation_menu.md：验证菜单anti_patterns.md：反模式清单literature_search_strategy.md：文献检索策略fund-search-workflow.md：完整搜索工作流（脚本调用链、降级策略）
search/（内化搜索包）
search/scripts/：搜索脚本（search_all.py, citation_finder.py, rank_and_filter.py, format_bibtex.py, dedup.py，另有 tier_utils/exa_search/search_google_scholar 等内部依赖，无需直接调用）search/references/：搜索参考文档（search-strategy.md, api-reference.md, data-schema.md, journal-tiers.md）search/data/：期刊数据（priority_journals.csv, blacklist_journals.csv）search/.env.example：API 密钥模板（需复制为 .env 并填写）search/requirements.txt：Python 依赖（requests, exa-py, scholarly）
工作流程
Step 1: 理解研究目标
- 读取用户研究构想（研究主题、研究目标）
- 确定文献综述的总体方向
Step 2: 解析研究内容
- 读取用户研究内容（通常3-5个）
- 确定文献综述的主题划分
Step 3: 识别关键科学问题
- 读取用户关键科学问题（通常1-3个）
- 确定文献评述的研究空白方向
What ships with it
25 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- config.yaml 7.9 KB
- knowledge_base/literature_mapping_rules.md 8.5 KB
- knowledge_base/literature_review_patterns.md 11 KB
- knowledge_base/literature_review_style_guide.md 10 KB
- references/anti_patterns.md 6.1 KB
- references/fund-search-workflow.md 6.0 KB
- references/info_form.md 4.4 KB
- references/literature_search_strategy.md 1.2 KB
- references/output_skeletons.md 10 KB
- references/validation_menu.md 9.7 KB
- requirements.txt 42 B
- search/data/blacklist_journals.csv 2.3 KB
- search/data/priority_journals.csv 3.1 KB
- search/references/api-reference.md 3.7 KB
- search/references/data-schema.md 3.6 KB
- search/references/journal-tiers.md 3.4 KB
- search/references/search-strategy.md 11 KB
- search/scripts/citation_finder.py 19 KB runs code
- search/scripts/dedup.py 2.9 KB runs code
- search/scripts/exa_search.py 7.4 KB runs code
- search/scripts/format_bibtex.py 4.9 KB runs code
- search/scripts/rank_and_filter.py 2.2 KB runs code
- search/scripts/search_all.py 10 KB runs code
- search/scripts/search_google_scholar.py 5.2 KB runs code
- search/scripts/tier_utils.py 7.9 KB runs code
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 13d ago First seen · 260 lines · 68 tokens per session scan A fc2a06d690ef
fund-literature-review-writer is a skill published in the GitHub repository HuiyuLi-2000/Chinese-Grant-Writer-Skills (383 stars, last pushed 2mo ago), licensed MIT. It adds 68 tokens to every session and 2,966 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…