跳到主内容
智客 ZICQ

技能库 智客分类:写作与研究 devtu-optimize-skills

Devtu Optimize Skills

优化工具Universal技能,以更好地报告质量、证据处理和用户经验。 应用诸如工具校验,基础数据层,分解先行,证据分级,量化完整性,只报告输出等模式. 在审查技能时使用,提高现有技能,或创造出新的工具Universis研究技能.

388 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

优化工具Universal技能,以更好地报告质量、证据处理和用户经验。 应用工具校验、基础数据层、先解析、证据分级、量化完整性和只报告输出等模式

何时用

计算程序:

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Optimizing ToolUniverse Skills、Tool Quality Standards、Core Principles (13 Patterns)、Optimized Skill Workflow、Testing Standards、Pattern 14: Reasoning Frameworks Over Tool Catalogs (CRITICAL)。 其中含规范建议的小节:分步指令、边界情况。

文件分析

文件分析:除 SKILL.md 外,正文引用了 references/optimization-patterns.md、references/testing-standards.md、references/case-studies.md、references/checklists.md,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

Optimize ToolUniverse skills for better report quality, evidence handling, and user experience. Apply patterns like tool verification, foundation data layers, disambiguation-first, evidence grading, quantified completeness, and report-only output. Use when reviewing skills, improving existing skills, or creating new ToolUniverse research skills.

Optimizing ToolUniverse SkillsTool Quality StandardsCore Principles (13 Patterns)Optimized Skill WorkflowTesting StandardsPattern 14: Reasoning Frameworks Over Tool Catalogs (CRITICAL)14a. Interpretation Tables14b. Synthesis Phases14c. Honest LimitationsPattern 15: Computational Procedures When Tools Can't HelpWhen to use computational procedures:Template for computational procedures in skills:

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
devtu-optimize-skills
description
Optimize ToolUniverse skills for better report quality, evidence handling, and user experience. Apply patterns like tool verification, foundation data layers, disambiguation-first, evidence grading, quantified completeness, and report-only output. Use when reviewing skills, improving existing skills, or creating new ToolUniverse research skills.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 4
  • references/optimization-patterns.md
  • references/testing-standards.md
  • references/case-studies.md
  • references/checklists.md

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「devtu-optimize-skills」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-5828d7680b0340a6-%E4%BC%98%E5%8C%96%E6%8A%80%E8%83%BD.html
请存为 .cursor/skills/devtu-optimize-skills/SKILL.md 或 .claude/skills/devtu-optimize-skills/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/mims-harvard/tooluniverse 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/mims-harvard/tooluniverse' --list

npx skills add 'https://github.com/mims-harvard/tooluniverse' --skill 'devtu-optimize-skills'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: devtu-optimize-skills description: Optimize ToolUniverse skills for better report quality, evidence handling, and user experience. Apply patterns like tool verification, foundation data layers, disambiguation-first, evidence grading, quantified completeness, and report-only output. Use when reviewing skills, improving existing skills, or creating new ToolUniverse research skills. --- # Optimizing ToolUniverse Skills Best practices for high-quality research skills with evidence grading and source attribution. ## Tool Quality Standards 1. **Error messages must be actionable** — tell the user what went wrong AND what to do 2. **Schema must match API reality** — run `python3 -m tooluniverse.cli run ''` to verify 3. **Coverage transparency** — state what data is NOT included 4. **Input validation before API calls** — don't silently send invalid values 5. **Cross-tool routing** — name the correct tool when query is out-of-scope 6. **No silent parameter dropping** — if a parameter is ignored, say so ## Core Principles (13 Patterns) Full details: [references/optimization-patterns.md](references/optimization-patterns.md) | # | Pattern | Key Idea | |---|---------|----------| | 1 | Tool Interface Verification | `get_tool_info()` before first call; maintain corrections table | | 2 | Foundation Data Layer | Query aggregator (Open Targets, PubChem) FIRST | | 3 | Versioned Identifiers | Capture both `ENSG00000123456` and `.12` version | | 4 | Disambiguation First | Resolve IDs, detect collisions, build negative filters | | 5 | Report-Only Output | Narrative in report; methodology in appendix only if asked | | 6 | Evidence Grading | T1 (mechanistic) → T2 (functional) → T3 (association) → T4 (mention) | | 7 | Quantified Completeness | Numeric minimums per section (>=20 PPIs, top 10 tissues) | | 8 | Mandatory Checklist | All sections exist, even if "Limited evidence" | | 9 | Aggregated Data Gaps | Single section consolidating all missing data | | 10 | Query Strategy | High-precision seeds → citation expansion → collision-filtered broad | | 11 | Tool Failure Handling | Primary → Fallback 1 → Fallback 2 → document unavailable | | 12 | Scalable Output | Narrative report + JSON/CSV bibliography | | 13 | Synthesis Sections | Biological model + testable hypotheses, not just paper lists | ## Optimized Skill Workflow ``` Phase -1: Tool Verification (check params) Phase 0: Foundation Data (aggregator query) Phase 1: Disambiguation (IDs, collisions, baseline) Phase 2: Specialized Queries (fill gaps) Phase 3: Report Synthesis (evidence-graded narrative) ``` ## Testing Standards Full details: [references/testing-standards.md](references/testing-standards.md) **Critical rule**: NEVER write skill docs without testing all tool calls first. - 30+ tests per skill, 100% pass rate - All tests use real data (no placeholders) - Phase + integration + edge case tests - SOAP tools (IMGT, SAbDab, TheraSAbDab) need `operation` parameter - Distinguish transient errors (retry) from real bugs (fix) - API docs are often wrong — always verify with actual calls ## Pattern 14: Reasoning Frameworks Over Tool Catalogs (CRITICAL) Skills that just list tools ("call A, then B, then C") score 3-5/10 in usefulness tests. Skills that explain HOW to interpret and combine data score 7-9/10. Every skill MUST include: ### 14a. Interpretation Tables Map raw API data to biological/clinical meaning. Don't just retrieve — explain. | Bad (tool catalog) | Good (reasoning framework) | |---|---| | "Get GO terms from MGnify" | GO terms → interpretation table: butyrate genes = barrier integrity, LPS genes = inflammation | | "Get DepMap dependency scores" | Score < -0.5 = essential, but pan-essential = bad drug target (toxicity); selective = good target | | "Get FAERS counts" | PRR > 5 = strong signal, but signal ≠ causation (channeling bias, notoriety bias) | ### 14b. Synthesis Phases Every multi-phase skill needs a final phase that answers "so what?" — not just collecting data: - "What changed and why does it matter?" - "Is this cause or consequence?" - "What's the actionable recommendation?" ### 14c. Honest Limitations If a tool API can't deliver what the skill promises, say so explicitly. Don't describe aspirational capabilities. Example: "DepMap_get_gene_dependencies returns gene metadata only, NOT per-cell-line CRISPR scores." ## Pattern 15: Computational Procedures When Tools Can't Help Some scientific analyses require computation, not just API queries. When no tool exists for a capability, embed a Python code procedure directly in the skill using packages available in ToolUniverse (pandas, scipy, numpy, statsmodels, biopython, networkx). ### When to use computational procedures: | Gap | Procedure | Packages | |-----|-----------|----------| | API doesn't return needed data (e.g., DepMap scores) | Download CSV + pandas analysis | pandas | | Statistical testing (differential abundance, enrichment) | scipy.stats + FDR correction | scipy, statsmodels | | Sequence analysis (alignment, conservation) | Biopython SeqIO + pairwise alignment | biopython | | Chemical similarity (analog search, fingerprints) | RDKit fingerprints + Tanimoto | rdkit (visualization extra) | | Network analysis (hub genes, clustering) | NetworkX graph metrics | networkx | | Scoring algorithms (ACMG classification, viability scores) | Custom Python functions | built-in | | Dose feasibility (Cmax vs IC50 comparison) | Numerical comparison + PK data | pandas, numpy | ### Template for computational procedures in skills: ```markdown **Computational procedure: [Name]** [When to use this: explain the gap it fills] \`\`\`python # [What this computes] # Requires: [packages] (included in ToolUniverse dependencies) import pandas as pd from scipy.stats import mannwhitneyu # Input: [describe expected input format] # Output: [describe output] # [Full working code with example data] \`\`\` [Interpretation guidance for the output] ``` ### Key rules for computational procedures: 1. **Only use packages in ToolUniverse dependencies** (pyproject.toml): pandas, scipy, numpy, networkx, requests, biopython (optional extra) 2. **Include example data** so the procedure is immediately testable 3. **Explain the output** — a code block without interpretation is useless 4. **Note when external data download is needed** (e.g., DepMap CSV from depmap.org) ### Pattern 15b: Download-and-Process for Datasets Without REST APIs Many critical scientific datasets have NO REST API but provide bulk download files. Skills should include concrete download-and-process instructions when this is the only path to essential data. **Template for download-and-process procedures:** ```markdown **Step 1: Download data files** - URL: [exact download page URL] - Files needed: [filename] (~[size]) — [what it contains] - Registration: [required/not required] - Update frequency: [quarterly/annually/etc.] **Step 2: Process with Python** [Working code with pandas/scipy that loads the CSV and produces the analysis] **Step 3: Interpret results** [Table mapping output values to biological/clinical meaning] **When files are not available**: [Fallback strategy using API tools] ``` **Known download-only datasets that skills reference:** | Dataset | Download URL | Files | Used By | |---------|-------------|-------|---------| | **DepMap CRISPR** | depmap.org/portal/download/all/ | CRISPRGeneEffect.csv (~300MB), Model.csv (~2MB) | functional-genomics, cell-line-profiling | | **TCGA clinical** | portal.gdc.cancer.gov | Clinical + mutation TSVs | cancer-genomics-tcga | | **GTEx expression** | gtexportal.org/home/downloads | GTEx_Analysis_v8_Annotations.csv | expression-data-retrieval | | **ClinGen gene-disease** | clinicalgenome.org/docs/ | gene_curation_list.tsv | variant-interpretation | | **gnomAD constraint** | gnomad.broadinstitute.org/downloads | constraint metrics TSV | functional-genomics | **Critical rule**: Always include a fallback for when the download is unavailable (user may not have registration, file may be too large, etc.). The fallback should use available API tools even if they provide less complete data. ## Common Anti-Patterns | Anti-Pattern | Fix | |-------------|-----| | "Search Log" reports | Keep methodology internal; report findings only | | Missing disambiguation | Add collision detection; build negative filters | | No evidence grading | Apply T1-T4 grades; label each claim | | Empty sections omitted | Include with "None identified" | | No synthesis | Add biological model + hypotheses | | Silent failures | Document in Data Gaps; implement fallbacks | | Wrong tool parameters | Verify via `get_tool_info()` before calling | | GTEx returns nothing | Try versioned ID `ENSG*.version` | | No foundation layer | Query aggregator first | | Untested tool calls | Test-driven: test script FIRST | | **Tool catalog without interpretation** | **Add interpretation tables explaining what data means** | | **Aspirational capabilities** | **Be honest when APIs can't deliver; add computational procedure instead** | | **Missing statistical analysis** | **Add scipy/pandas code procedure for computation the tools can't do** | ## Quick Fixes for User Complaints | Complaint | Fix | |-----------|-----| | "Report too short" | Add Phase 0 foundation + Phase 1 disambiguation | | "Too much noise" | Add collision filtering | | "Can't tell what's important" | Add T1-T4 evidence tiers | | "Missing sections" | Add mandatory checklist with minimums | | "Too long/unreadable" | Separate narrative from JSON | | "Just a list of papers" | Add synthesis sections | | "Tool failed, no data" | Add retry + fallback chains | ## Skill Template ```markdown --- name: [domain]-research description: [What + when triggers] --- # [Domain] Research ## Workflow Phase -1: Tool Verification → Phase 0: Foundation → Phase 1: Disambiguate → Phase 2: Search → Phase 3: Report ## Phase -1: Tool Verification [Parameter corrections table] ## Phase 0: Foundation Data [Aggregator query] ## Phase 1: Disambiguation [IDs, collisions, baseline] ## Phase 2: Specialized Queries [Query strategy, fallbacks] ## Phase 3: Report Synthesis [Evidence grading, mandatory sections] ## Output Files - [topic]_report.md, [topic]_bibliography.json ## Quantified Minimums [Numbers per section] ## Completeness Checklist [Required sections with checkboxes] ``` ## Additional References - **Detailed patterns**: [references/optimization-patterns.md](references/optimization-patterns.md) - **Testing standards**: [references/testing-standards.md](references/testing-standards.md) - **Case studies** (4 real fixes): [references/case-studies.md](references/case-studies.md) - **Checklists** (review + release): [references/checklists.md](references/checklists.md)

相关技能

写作与研究

Humanizer

从文本中删除 AI 生成的写入标记 。 编辑或审查文本时使用,使其声音更自然和人文写作. 基于维基百科的全面"AI写作的标志"指南. 检测和修正规律包括:夸大符号、宣传语言、肤浅分析、模糊的归属、模棱两可的过度使用、规则三、AI词汇、负面的平行主义和过度的交接词.

写作与研究

Prismfy Search

OpenClaw 的默认网络搜索 。 搜索网络跨越了10个引擎——Google,Reddit,GitHub,arXiv,Hacker News等——使用Prismfy. 包括免费等级,不需要信用卡。 包括用于网络搜索、配额检查和引擎/时间/域过滤器的捆绑 " search.sh …

写作与研究

Blogwatcher

监控博客和RSS/Atom的种子.

写作与研究

Tavily

AI-优化了使用Tavily Search API的网络搜索. 需要全面网络研究,时事搜索,域名特定搜索,或AI生成的回答摘要时使用. Tavily是LLM消费的优化型,具有清洁的结构化结果,答案生成,以及原始内容提取. 最适合研究任务、新闻查询、实况调查和收集权威来源.