OpenClaw/clawhub-security-signals huggingface dataset:
Skill: brad-sl/reference-maintainer (version 1.0.0)

--- name: reference-maintainer description: Professional system documentation generator that prevents AI agents from sounding like 'new hires' every session. Automatically extracts schemas, parameters, and configs from code/systems, generating living reference docs (overview, phases, architecture, file index, repo, credentials, tools, best practices) to ensure accurate, up-to-date knowledge across compactions/sessions. Triggers on 'document system', 'generate references', 'maintain docs', 'prevent new hire syndrome', 'package as skill', 'create expert memory'.

path: assets/examples/system-docs.md
content: # Example System Docs
Schema: YAML config
Overview: Purpose
Phases: 1-5 breakdown


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: zmz209/docx-compare (version 1.0.2)

--- name: DOCX Compare / Duplicate Check slug: docx-compare version: 1.0.2 homepage: https://clawhub.com/skills/docx-compare description: "Compare two Word documents (DOCX) to find duplicate text paragraphs and duplicate images. Supports exact string matching, fuzzy matching (difflib), and image MD5 hash comparison. Outputs highlighted DOCX files and a detailed text report. Use when: (1) a user asks to check or compare duplicate content between two Word documents; (2) review for content overlap, version comparison, or plagiarism detection; (3) need to locate duplicated images across documents." changelog: | v1.0.2 — Fix crash on `pars2` typo (should be `paras2`) + escape sequence cleanups v1.0.1 — Fix image comment injection: double XML declaration from etree.tostring(standalone=True), and skip of new comments.xml in ZIP output. Add SyntaxWarning fix for invalid escape sequence. v1.0.0 — Initial release — text exact/fuzzy dedup, image duplicate detection via MD5 hash, annotated DOCX output and report. metadata: {"clawdbot":{"emoji":"📑","os":["win32"]}} --- # DOCX 文档查重工具 比较两个 Word 文档（.docx），找出重复的文本段落和重复的图片。 ## 什么时候用 - 用户说"帮我查一下这两个 Word 文档内容有没有重复" - 比较同一文档的不同版本，找出新增/重复内容 - 需要定位跨文档的重复图片 ## 快速开始 ```bash # 最基本用法：比较两个 docx python scripts/compare_docx.py --file1 文档A.docx --file2 文档B.docx # 指定输出目录 python scripts/compare_docx.py --file1 文档A.docx --file2 文档B.docx --output ./对比结果 ``` ## 功能说明 | 模式 | 说明 | 阈值 | |---|---|---| | **精确匹配** | 标准化后完全相同的段落 | 100% | | **模糊匹配** | 相似度超过阈值的段落 | ≥95% | | **图片查重** | 通过 MD5 哈希值比较图片 | 100% | ## 输出 - `*_标记重复.docx` — 高亮标记了重复文字的原始文档 - `*_标记图片重复.docx` — 标注了重复图片的原始文档 - `*_重复报告.txt` — 纯文本详细对比报告 ## 脚本参数 ``` python scripts/compare_docx.py \ --file1 <路径> # 必需：第一个文档 --file2 <路径> # 必需：第二个文档 --output <目录> # 可选：输出目录（默认同目录） --mode all|text|image # 可选：检查模式（默认 all） --threshold 0.95 # 可选：模糊匹配相似度阈值（默认 0.95） ``` ## 依赖 - `python-docx` 用于读写 DOCX 文件 - `difflib`（标准库）用于模糊匹配 - `hashlib`（标准库）用于图片 MD5 计算 安装依赖： ```bash pip install python-docx ``` ## 常见陷阱 - 仅支持 `.docx` 格式，不支持旧版 `.doc`（需要先转换） - 图片重复检测基于文件内容（MD5），同一张图被不同文件名存储会被判定为重复 - 段落模糊匹配使用 `difflib.SequenceMatcher`，CPU 开销随段落数平方增长 - 输出 DOCX 使用黄色高亮标记，不会修改原始文档 - 中文段落含混合标点时，模糊匹配效果可能低于预期 ## 相关 Skill - `word-docx` — 通用 Word 文档创建、编辑、格式调整 ## Feedback - 如果觉得有用：`clawhub star docx-compare` - 保持更新：`clawhub sync`


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: dizhu/chinese-copywriting-guidelines (version 0.1.0)

--- name: chinese-copywriting-guidelines description: Chinese copywriting typesetting guidelines. Standardize Chinese writing spacing, punctuation, fullwidth/halfwidth usage. Triggers when need Chinese writing standards help, review Chinese copywriting, check typesetting. --- # 中文文案排版指北 统一中文文案、排版的相关用法，降低团队沟通成本，提升网站阅读气质。 ## Core Rules ### 空格 **中英文之间需要增加空格** 正确： > 在 LeanCloud 上，数据存储是围绕 `AVObject` 进行的。 错误： > 在LeanCloud上，数据存储是围绕AVObject进行的。 例外：`豆瓣FM` 这种产品名，按官方原格式写。 **中文与数字之间需要增加空格** 正确： > 今天出去买菜花了 5000 元。 错误： > 今天出去买菜花了 5000元。 **数字与单位之间**不需要增加空格 正确： > 我家的光纤入户宽带有 10Gbps，SSD 一共有 10TB。 > 今天是 233° 的高温。 > 新 MacBook Pro 有 15% 的 CPU 性能提升。 错误： > 我家的光纤入户宽带有 10 Gbps，SSD 一共有 20 TB。 **全角标点与其他字符之间**不加空格 正确： > 刚刚买了一部 iPhone，好开心！ 错误： > 刚刚买了一部 iPhone ，好开心！ ### 标点符号 **不重复使用标点** 正确： > 德国队竟然战胜了巴西队！ > 她竟然对你说「喵」？！ 错误： > 德国队竟然战胜了巴西队！！ > 德国队竟然战胜了巴西队！！！！！！！！ > 她竟然对你说「喵」？！！ ### 全角和半角 **中文使用全角标点** 正确： > 嗨！你知道嘛？今天前台的小妹跟我说「喵」了哎！ > 核磁共振成像（NMRI）是什么原理都不知道？JFGI！ 错误： > 嗨! 你知道嘛? 今天前台的小妹跟我说 "喵" 了哎! **数字使用半角字符** 正确： > 这件蛋糕只卖 1000 元。 错误： > 这件蛋糕只卖 １０００ 元。 例外：设计稿/海报要用全角数字可以用。 **完整英文句子/专有名词**用半角标点 正确： > 乔布斯那句话是怎么说的？「Stay hungry, stay foolish.」 > 推荐你阅读《Hackers & Painters: Big Ideas from the Computer Age》，非常有趣。 错误： > 乔布斯那句话是怎么说的？「Stay hungry，stay foolish。」 ### 名词 **专有名词正确大小写** 正确： > 使用 GitHub 登录 > 我们的客户有 GitHub、Foursquare、Microsoft Corporation、Google、Facebook, Inc.。 错误： > 使用 github 登录 > 使用 GITHUB 登录 **不要使用不地道缩写** 正确： > 我们需要一位熟悉 JavaScript、HTML5，至少理解一种框架（如 Backbone.js、AngularJS、React 等）的前端开发者。 错误： > 我们需要一位熟悉 Js、h5，至少理解一种框架（如 backbone、angular、RJS 等）的 FED。 ### 争议 **链接之间增加空格** 正确： > 请 [提交一个 issue](#) 并分配给相关同事。\ > 访问我们网站的最新动态，请 [点击这里](#) 进行订阅！ 对比： > 请[提交一个 issue](#) 并分配给相关同事。\ > 访问我们网站的最新动态，请[点击这里](#)进行订阅！ **简体中文使用直角引号** 正确： > 「老师，『有条不紊』的『紊』是什么意思？」 对比： > “老师，‘有条不紊’的‘紊’是什么意思？” ## Tools - [mzlogin/chinese-copywriting-guidelines](https://github.com/mzlogin/chinese-copywriting-guidelines) - Source repo of this guidelines - [vinta/paranoid-auto-spacing](https://github.com/vinta/pangu.js) - JavaScript auto-spacing - [huacnlee/auto-correct](https://github.com/huacnlee/auto-correct) - Ruby auto-correction ## Who is using this? - Apple 中国/香港/台湾 - Microsoft 中国/香港/台湾 - V2EX - 知乎 - Ruby China


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: jorgermp/gitlab-manager (version 1.0.0)

--- name: gitlab-manager description: Manage GitLab repositories, merge requests, and issues via API. Use for tasks like creating repos, reviewing code in MRs, or tracking issues. --- # GitLab Manager This skill allows interaction with GitLab.com via the API. ## Prerequisites - **GITLAB_TOKEN**: A Personal Access Token with `api` scope must be set in the environment. ## Usage Use the provided Node.js script to interact with GitLab. ### Script Location `scripts/gitlab_api.js` ### Commands #### 1. Create Repository Create a new project in GitLab. ```bash ./scripts/gitlab_api.js create_repo "<name>" "<description>" "<visibility>" # Visibility: private (default), public, internal ``` #### 2. List Merge Requests List MRs for a specific project. ```bash ./scripts/gitlab_api.js list_mrs "<project_path>" "[state]" # Project path: e.g., "jorgermp/my-repo" (will be URL encoded automatically) # State: opened (default), closed, merged, all ``` #### 3. Comment on Merge Request Add a comment (note) to a specific MR. Useful for code review. ```bash ./scripts/gitlab_api.js comment_mr "<project_path>" <mr_iid> "<comment_body>" ``` #### 4. Create Issue Open a new issue. ```bash ./scripts/gitlab_api.js create_issue "<project_path>" "<title>" "<description>" ``` ## Examples **Create a private repo:** ```bash GITLAB_TOKEN=... ./scripts/gitlab_api.js create_repo "new-tool" "A cool new tool" "private" ``` **Review an MR:** ```bash # First list to find ID GITLAB_TOKEN=... ./scripts/gitlab_api.js list_mrs "jorgermp/my-tool" "opened" # Then comment GITLAB_TOKEN=... ./scripts/gitlab_api.js comment_mr "jorgermp/my-tool" 1 "Great work, but check indentation." ```


Security scan verdicts — ClawScan: clean | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: rubenfb23/whatsapp-styler (version 1.0.0)

--- name: whatsapp-styler description: Skill to ensure all messages sent to WhatsApp follow the platform's specific formatting syntax. It prevents markdown bloat and ensures a clean, mobile-first reading experience. --- # WhatsApp Styler This skill defines the strict formatting rules for WhatsApp to ensure the user sees clean, styled text without raw markdown symbols. ## Core Syntax Rules 1. *Bold*: Use single asterisks around text: `*texto*`. NEVER use double asterisks `**`. 2. _Italic_: Use single underscores around text: `_texto_`. 3. ~Strikethrough~: Use tildes around text: `~texto~`. 4. `Monospace`: Use triple backticks: ``` texto ``` (good for code or technical IDs). 5. *Bullet Lists*: Use a single asterisk followed by a space: `* Item`. 6. *Numbered Lists*: Use standard numbers: `1. Item`. 7. *Quotes*: Use the angle bracket: `> texto`. ## Prohibited Patterns (Do NOT use) - No headers (`#`, `##`, `###`). Use *BOLD CAPS* instead. - No markdown tables. Use bullet lists for structured data. - No horizontal rules (`---`). Use a line of underscores if needed `__________`. - No nested bold/italic symbols if it risks showing raw characters. ## Goal The goal is a "Human-to-Human" look. Technical but clean.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: xbmchina/baby-planner (version 1.0.0)

# Baby Planner 备孕孕期全程助手 全方位生娃助手，覆盖备孕指导、孕期管理、待产准备、宝宝起名、育儿知识库、孕期记录，以及公众号/朋友圈内容生成。 ## 功能模块 ### 1. 备孕指导 - 排卵期计算（末次月经→排卵日→最佳受孕窗口） - 备孕检查清单（女性/男性/双方） - 营养指南（叶酸/DHA/铁/饮食禁忌） - 公众号备孕文案结构（3套模板） ### 2. 孕期全程指南 - 孕早期（1-12周）：B超确认胎心、NT/早唐、孕吐缓解、营养禁忌 - 孕中期（13-27周）：大排畸、糖耐、胎动观察、营养强化 - 孕晚期（28-40周）：胎监、分娩信号识别、待产准备 - 产检时间表：6周B超→12周NT→20-24周四维→24-28周糖耐→36周GBS筛查 - 孕期不适缓解：孕吐/便秘/抽筋/水肿/失眠/妊娠纹 ### 3. 待产清单 - 妈妈物品：证件、衣物（开衫睡衣/一次性内裤）、护理（产褥垫/产妇卫生巾）、哺乳（吸奶器/储奶袋） - 宝宝物品：衣物、喂养（奶瓶/奶粉）、护理（NB纸尿裤/护臀膏）、出院（安全座椅） - 家中提前备好：婴儿床/消毒柜/温奶器/耳温枪/婴儿洗衣机 - 公众号待产清单文案结构（2套模板） ### 4. 宝宝起名 - 起名流程：收集信息→八字分析→五行旺缺→喜用神判断→选字→候选名单 - 五行喜用参考：木（森/桐/榆）、火（煜/炜/晟）、土（坤/培/均）、金（铭/钧/铎）、水（泽/润/涵） - 音调搭配原则：三声调姓氏配一/二/四声名 - 公众号起名攻略文案（2套模板） ### 5. 育儿知识库（衔接 parenting skill） - 各月龄发育里程碑：身高/体重/能力对照表 - 分月龄辅食指南：吞咽期→蠕嚼期→细嚼期→咀嚼期 - 睡眠管理：各月龄时长+哄睡方法+睡眠仪式 - 健康护理：疫苗时间表+常见病家庭处理 - 公众号育儿内容（6套模板） ### 6. 孕期记录 - 孕期日志模板：体重/产检/身体感受/心情/待办 - 孕期照片规划建议 ## 参考文档 - `references/pregnancy_timeline.md` — 详细孕期日历+食谱 - `references/naming_guide.md` — 起名完整手册+案例 - `references/hospital_checklist.md` — 待产包完整清单 - `references/public_account_templates.md` — 公众号内容模板


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: akkualle/akkualle-amazon-paapi (version 1.0.0)

--- name: amazon-paapi description: "Search Amazon products and get product details using Amazon Product Advertising API (PA-API). Use for product searches, price lookups, and affiliate links." metadata: {"requires":{"env":["AMAZON_ACCESS_KEY","AMAZON_SECRET_KEY","AMAZON_PARTNER_TAG"]},"emoji":"🛒","always":true} user-invocable: true --- # Amazon Product Advertising API Skill This skill allows you to search for products on Amazon.de and retrieve product information using the Amazon PA-API. ## Tools ### amazon_search Search for products on Amazon. **Usage:** ```bash amazon-search "search keywords" [--category CATEGORY] [--max-results N] ``` **Examples:** - `amazon-search "wireless headphones"` - `amazon-search "gaming laptop" --category Electronics --max-results 5` ### amazon_product Get details for a specific product by ASIN. **Usage:** ```bash amazon-product ASIN ``` **Example:** - `amazon-product B09V3KXJPB` ## Environment Variables Required - AMAZON_ACCESS_KEY: Your Amazon PA-API Access Key - AMAZON_SECRET_KEY: Your Amazon PA-API Secret Key - AMAZON_PARTNER_TAG: Your Amazon Associates Partner Tag - AMAZON_HOST: Amazon API host (default: webservices.amazon.de) - AMAZON_REGION: AWS region (default: eu-west-1)


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: dapan0902/report-generator-new (version 1.0.1)

--- name: report-generator-new display_name：技术报告生成 description: Generates structured technical reports in Markdown. Use when the user asks to write, create, or draft a report, summary, or analysis document. metadata: pattern: generator output-format: markdown version：1.0.1 --- You are a technical report generator. Follow these steps exactly: Step 1: Load 'references/style-guide.md' for tone and formatting rules. Step 2: Load 'assets/report-template.md' for the required output structure. Step 3: Ask the user for any missing information needed to fill the template: - Topic or subject - Key findings or data points - Target audience (technical, executive, general) Step 4: Fill the template following the style guide rules. Every section in the template must be present in the output. Step 5: Return the completed report as a single Markdown document.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: dzming/clawpolicy (version 3.0.2)

--- name: clawpolicy description: Install and use ClawPolicy, an explainable autonomous execution policy engine for low-touch, auditable agent execution. Supports initialization, policy supervision, status checks, risky/suspended inspection, and Python API usage. metadata: { "openclaw": { "requires": { "bins": ["python3", "pip3"] }, "install": [ { "id": "pip", "kind": "python", "package": "clawpolicy", "bins": ["clawpolicy"], "label": "Install clawpolicy from PyPI" } ] } } --- # ClawPolicy ClawPolicy is an explainable autonomous execution policy engine for low-touch, auditable agent execution. ## What it does - Initializes canonical local policy storage in `.clawpolicy/policy/` - Tracks policy lifecycle: `hint -> candidate -> confirmed -> suspended -> archived` - Exposes a supervision CLI: `clawpolicy policy ...` - Provides a stable Python API for confirmation, policy storage, and Markdown conversion/export ## Install ```bash python3 -m pip install clawpolicy ``` Optional extras: ```bash python3 -m pip install "clawpolicy[phase3]" ``` ## Quick start ```bash clawpolicy init clawpolicy analyze clawpolicy policy status clawpolicy policy recent clawpolicy policy risky clawpolicy policy suspended ``` ## Verification The published package should pass this minimal smoke path: ```bash python3 -m pip install clawpolicy clawpolicy --help clawpolicy init clawpolicy policy status python -m clawpolicy policy status ``` ## Python API ```python from clawpolicy import ( ConfirmationAPI, PolicyEvent, PolicyStore, Playbook, Rule, MarkdownToPolicyConverter, PolicyToMarkdownExporter, create_api, ) ``` ## References - Upstream repo: `https://github.com/DZMing/clawpolicy` - Chinese README: `references/upstream-README.zh-CN.md` - English README: `references/upstream-README.md` - Changelog: `references/upstream-CHANGELOG.md` - Security policy: `references/upstream-SECURITY.md` ## Notes - This ClawHub package is a skill wrapper for the public `clawpolicy` project. - Canonical source code, releases, and issue tracking remain in the upstream GitHub repository.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: fonilye/content-stock (version 1.0.0)

--- name: content-stock description: Analyze themes/news for stock selection version: 1.0.0 metadata: openclaw: requires: env: - EASYALPHA_API_KEY bins: - node primaryEnv: EASYALPHA_API_KEY --- # 题材选股技能 此技能基于关键词、新闻标题或报告进行题材选股分析。 ## 使用方法 设置环境变量 `EASYALPHA_API_KEY`，然后调用 `get_content_stock(request)` 函数，其中 request 是包含 `query` 和 `type` 的对象。 ## 参数 - query: string - 分析查询 - type: string - 分析深度 ("fast" 或 "deep") ## 示例 ```javascript const { get_content_stock } = require('./content_stock'); async function main() { const req = { query: "新能源题材", type: "deep" }; for await (const line of get_content_stock(req)) { process.stdout.write(line); } } main(); ```


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: leooooooow/ecommerce-copy-humanizer-vn (version 1.0.0)

--- name: ecommerce-copy-humanizer-vn description: Humanize Vietnamese ecommerce copy to reduce robotic AI phrasing while keeping the message persuasive and platform-appropriate. Best for product pages, ad copy, seller replies, and ecommerce captions written in Vietnamese. --- # Ecommerce Copy Humanizer VN Make Vietnamese ecommerce copy sound more human, more native, and less obviously AI-generated without losing selling intent. ## Language scope - **Language:** Vietnamese only - Input should be written primarily in **Vietnamese**. - Output should stay in **Vietnamese**. - This skill is **not** for translation or bilingual localization. ## Solves - Copy sounds too robotic, generic, or machine-written. - The wording feels translated, over-polished, or not native to ecommerce usage. - Rewriting for natural tone often weakens the offer or creates compliance risk. Goal: **Make ecommerce copy feel more human and commercially usable while preserving clarity, persuasion, and safer wording.** ## Use when - Product page copy needs to sound more natural - Ad copy feels too templated or AI-written - Seller replies / customer replies need a more human tone - Ecommerce captions or selling scripts need less robotic phrasing ## Do not use for - Translation between languages - Legal, medical, or regulated compliance review - Long-form brand storytelling unrelated to ecommerce conversion - Claim invention or exaggerated benefit creation ## Inputs - Original Vietnamese copy - Platform or channel - Target audience - Tone preference - Compliance boundaries or banned wording ## Workflow 1. Detect obvious AI tone, generic phrasing, and translated-looking patterns. 2. Rewrite the copy into more natural Vietnamese ecommerce language. 3. Preserve the core offer, proof direction, and CTA intent. 4. Flag risky phrases and suggest safer wording swaps when needed. ## Output 1. AI-tone issues 2. Rewritten version (main) 3. Alternative version 4. Risk-safe wording swaps 5. Usage note by context ## Quality bar - Should sound like natural Vietnamese ecommerce communication, not a model template. - Should keep selling intent without sounding exaggerated or fake. - Should be usable for real storefront, ad, or customer-touch workflows. - Should not drift into translation, over-copywriting, or fabricated claims. ## Notes This skill is for Vietnamese ecommerce copy only. Use it to make copy sound less robotic, more native, and more natural for ecommerce selling contexts. ### Example Original: Serum cao cấp này cung cấp độ ẩm vượt trội và mang lại làn da rạng rỡ ngay lập tức. Rewrite: Serum này giúp da ẩm hơn và trông tươi hơn với cách diễn đạt tự nhiên, bớt cảm giác quảng cáo máy móc. ## Resource See `references/output-template.md`.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: jamierossouw/rho-telegram-alerts (version 1.0.1)

--- name: telegram-alerts version: 1.0.0 description: Send formatted trading alerts, portfolio updates, and market signals via Telegram. Supports price alerts, stop-loss notifications, win/loss reporting, and scheduled summaries. Use when you need Telegram notifications for trades, price alerts, portfolio updates, or automated trading reports. author: JamieRossouw tags: [telegram, alerts, trading, notifications, crypto, automation, bots] --- # Telegram Alerts — Trading Notification System Send rich trading alerts to Telegram for any crypto event or portfolio update. ## Alert Types - **Trade alerts**: entry/exit with P&L, entry price, stop, target - **Price alerts**: trigger when asset crosses threshold - **Portfolio summaries**: NAV, daily P&L, positions - **Stop-loss warnings**: drawdown approaching limit - **Win/loss streaks**: celebration + tilt prevention - **Scheduled reports**: daily 18:00, weekly Monday ## Usage ``` Use telegram-alerts to send a trade entry notification for BTC LONG at $68,000 Use telegram-alerts to send my daily portfolio summary Use telegram-alerts to alert me when SOL breaks $90 ``` ## Format Example ``` 🟢 TRADE OPENED Asset: BTC/USDT | LONG Entry: $68,247 | Stop: $67,200 | Target: $70,000 Risk: $0.38 (0.05% NAV) | R:R = 1:2.6 ``` ## Setup Requires TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID in your .env file.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: idapixl/cortex-review (version 1.1.0)

--- name: cortex-review version: 1.1.0 description: "[DEPRECATED] This skill has been merged into cortex-engine. Install clawhub.ai/idapixl/cortex-engine instead." author: idapixl tags: [deprecated] --- # Deprecated — Use cortex-engine This skill has been consolidated into **[cortex-engine](https://clawhub.ai/idapixl/cortex-engine)**. Install the replacement: ``` clawhub install cortex-engine ``` The new skill includes everything from cortex-review plus the full query/record workflow, pinned package versions, and source verification links.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: lyt0302/literature-helper (version 1.0.0)

--- name: literature-helper description: literature retrieval and single-pdf analysis for academic research. use when the user asks to find papers by topic, author, keyword, or latest papers in the last five years; when the user wants bilingual search terms; when the user uploads a single pdf and asks for keywords, summary, methods, findings, limitations, or question answering grounded in the pdf. --- # Literature Helper ## Literature retrieval When the user asks for literature on a topic, author, keyword, research field, or latest papers: 1. Identify: - topic - optional author - optional time range - optional language preference 2. If the user asks for "latest literature" but gives no time range, default to the last 5 years. 3. Generate: - Chinese keywords - English keywords - 2 to 4 useful search strings 4. Search for relevant papers and return a structured result list. 5. For each result, include: - title - authors - year - source or journal - one-sentence summary - link - availability label: - open access - repository pdf - abstract only - availability unconfirmed 6. Never claim full-text availability unless it is actually confirmed. ## Single PDF analysis When the user uploads one PDF: 1. Extract: - title - keywords - research question - methods - data or materials - main findings - conclusion - limitations 2. Then give a clear Chinese summary unless the user asks for another language. 3. If the user asks questions about the PDF: - answer primarily from the PDF - if the answer is not found in the PDF, say clearly that it was not found in the document - do not invent details ## Output style For literature retrieval, use: ### Search terms - Chinese: - English: - Suggested search strings: ### Results 1. Title - Authors: - Year: - Source: - Summary: - Link: - Availability: For PDF analysis, use: ### Basic information ### Keywords ### Research question ### Methods ### Data or materials ### Main findings ### Conclusion ### Limitations ### Answers to user questions ## Reliability rules - Be explicit about uncertainty. - Never fabricate paper links, authors, journals, or availability. - Distinguish clearly between: - open access direct pdf - repository version - abstract page only - unconfirmed access


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)