跳到主内容
智客 ZICQ

技能库 智客分类:写作与研究 devtu-self-evolve

Devtu Self Evolve

管弦乐全"工具University自改进"循环:发现API,创建工具,用研究者人物来测试,解决问题,优化技能,并通过git来推. 参考和发送到所有其他 devtu 技能。 被请求时使用:运行自改进回路,进行调试/测试回合,扩展工具覆盖,提高工具质量,或演化出"工具Universe".

306 安装量

官方网址:skills.sh

技能介绍

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

做什么

管弦乐全"工具University自改进"循环:发现API,创建工具,用研究者人物来测试,解决问题,优化技能,并通过git来推. 所有其他敬业技能的参考和发送

何时用

请求:运行自改进循环,进行调试/测试回合,扩展工具覆盖,提高工具质量,或进化工具Universe

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:ToolUniverse Self-Evolution Orchestrator、The Cycle、Quick Start、Phase 1: Discovery (optional)、Phase 2: Tool Creation (optional)、Phase 3: Testing Phase。

文件分析

文件分析:除 SKILL.md 外,正文引用了 references/persona-template.md、scripts/run_eval.py、scripts/analyze_results.py、scripts/generate_report.py、references/bug-patterns.md,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

Orchestrate the full ToolUniverse self-improvement cycle: discover APIs, create tools, test with researcher personas, fix issues, optimize skills, and push via git. References and dispatches to all other devtu skills. Use when asked to: run the self-improvement loop, do a debug/test round, expand tool coverage, improve tool quality, or evolve ToolUniverse.

ToolUniverse Self-Evolution OrchestratorThe CycleQuick StartPhase 1: Discovery (optional)Phase 2: Tool Creation (optional)Phase 3: Testing PhaseSetupResearcher Persona AgentsVerification (CRITICAL)Fix PrinciplesSkill Usefulness Testing (NEW — beyond tool testing)Phase 3.5: Benchmark Evaluation

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
devtu-self-evolve
description
Orchestrate the full ToolUniverse self-improvement cycle: discover APIs, create tools, test with researcher personas, fix issues, optimize skills, and push via git. References and dispatches to all other devtu skills. Use when asked to: run the self-improvement loop, do a debug/test round, expand tool coverage, improve tool quality, or evolve ToolUniverse.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 5
  • references/persona-template.md
  • scripts/run_eval.py
  • scripts/analyze_results.py
  • scripts/generate_report.py
  • references/bug-patterns.md

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

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

安装这个技能

Skills CLI ↗

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

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

交给 Agent 安装

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

把 Agent Skill「devtu-self-evolve」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-59c72954894d7982-Devtu-%E8%87%AA%E6%BC%94%E8%BF%9B.html
请存为 .cursor/skills/devtu-self-evolve/SKILL.md 或 .claude/skills/devtu-self-evolve/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-self-evolve'

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

阅读排版
--- name: devtu-self-evolve description: > Orchestrate the full ToolUniverse self-improvement cycle: discover APIs, create tools, test with researcher personas, fix issues, optimize skills, and push via git. References and dispatches to all other devtu skills. Use when asked to: run the self-improvement loop, do a debug/test round, expand tool coverage, improve tool quality, or evolve ToolUniverse. --- # ToolUniverse Self-Evolution Orchestrator Coordinates the full development lifecycle by dispatching to specialized devtu skills. ## The Cycle ``` Discover → Create → Test → Fix → Optimize → Ship → Repeat ``` Each phase maps to a dedicated skill: | Phase | Skill | What it does | |-------|-------|-------------| | **Discover** | `devtu-auto-discover-apis` | Gap analysis, web search for APIs, batch discovery | | **Create** | `devtu-create-tool` | Build tool class + JSON config + test examples | | **Test** | *(this skill)* | Launch researcher persona agents to find issues | | **Fix** | `devtu-fix-tool` | Diagnose failures, implement fixes, validate | | **Optimize** | `devtu-optimize-skills` | Improve skill reports, evidence handling, UX | | **Optimize** | `devtu-optimize-descriptions` | Improve tool JSON descriptions for clarity | | **Docs** | `devtu-docs-quality` | Validate documentation accuracy | | **Ship** | `devtu-github` | Branch, commit, push, create PR | ## Quick Start Pick an entry point based on what's needed: - **"Run a test round"** → jump to [Testing Phase](#testing-phase) - **"Expand coverage"** → invoke `Skill(skill="devtu-auto-discover-apis")` - **"Create a new tool"** → invoke `Skill(skill="devtu-create-tool")` - **"Fix a broken tool"** → invoke `Skill(skill="devtu-fix-tool")` - **"Improve skills"** → invoke `Skill(skill="devtu-optimize-skills")` - **"Full cycle"** → follow all phases below in order --- ## Phase 1: Discovery (optional) Invoke `Skill(skill="devtu-auto-discover-apis")` to: 1. Run gap analysis on current tool categories 2. Search for life science APIs in underrepresented domains 3. Score and prioritize APIs by coverage, reliability, documentation ## Phase 2: Tool Creation (optional) Invoke `Skill(skill="devtu-create-tool")` for each new API: 1. Create Python tool class implementing the API 2. Create JSON config with parameters, descriptions, test examples 3. Register in `_lazy_registry_static.py` and `default_config.py` 4. Validate: `python -m tooluniverse.cli test ` ## Phase 3: Testing Phase This is the core testing loop, run directly by this skill. ### Setup 1. Check for open PRs: `gh pr list --state open` 2. If unmerged PR → use that branch; if merged → new branch from `origin/main` 3. Rebase: `git fetch origin && git rebase origin/main` ### Researcher Persona Agents Launch 2 agents per round (A + B) using the Agent tool with these parameters: **Each agent gets:** - Domain specialty (oncology, genomics, pharmacology, etc.) - Research question (specific biological question) - 5-7 test scenarios exercising different tools - Instructions to report issues with severity (HIGH/MEDIUM/LOW) - Issue IDs: `Feature-{round}{letter}-{num}` (e.g., `Feature-59A-001`) **Agent prompt template** — see [references/persona-template.md](references/persona-template.md) ### Verification (CRITICAL) Before implementing ANY agent-reported issue, verify via CLI: ```bash python3 -m tooluniverse.cli run '' ``` **50%+ of agent reports are false positives** from MCP interface confusion. Only fix verified issues. ### Fix Principles 1. **Prevent, don't recover** — fix root cause, not symptoms 2. **Validate at input** — reject bad params early with clear guidance 3. **Distinguish "no data" from "bad query"** — different messages for each 4. **Fix the abstraction** — don't add alias lists that grow forever Anti-patterns: hint text instead of validation, parameter aliases instead of fixing naming, post-hoc probing instead of pre-validation. ### Skill Usefulness Testing (NEW — beyond tool testing) Standard testing verifies tools work. Usefulness testing verifies skills actually solve scientist problems. Run this after standard testing: 1. **Pick a real research question** that the skill claims to answer (not a tool-level test) 2. **Launch an agent** following the skill workflow on the real question 3. **Assess honestly**: Does the skill produce an actionable answer, or just a data dump? **Score 1-10 rubric**: - 1-3: Tool catalog — lists tools without interpretation - 4-6: Data collector — gathers data but doesn't help combine/interpret - 7-8: Reasoning framework — guides interpretation with tables/scoring/synthesis - 9-10: Decision engine — produces concrete, defensible recommendations **Common failure patterns found in usefulness tests**: | Pattern | Score Impact | Fix | |---------|-------------|-----| | "Call A, then B, then C" without explaining what to DO with results | -3 | Add interpretation tables | | Tool params wrong (tool works but skill documents wrong names) | -2 | Verify ALL tool params via `get_tool_info()` | | Promises data the API can't deliver (e.g., DepMap CRISPR scores) | -2 | Be honest about limitations; add computational procedure workaround | | No synthesis phase at the end | -2 | Add "so what?" phase that combines all evidence | | No evidence grading | -1 | Add T1-T4 or similar confidence tiers | | No computational procedures for things tools can't do | -1 | Add Python code blocks using scipy/pandas/numpy | **When tools can't help, add computational procedures**: Some analyses need Python code, not API calls. Skills should include working code blocks for: - Statistical testing (scipy.stats, FDR correction) - Data analysis from downloaded files (pandas + CSV from DepMap, TCGA, etc.) - Scoring algorithms (ACMG classification, viability scores) - Sequence analysis (Biopython) See `devtu-optimize-skills` Patterns 14-15 for full guidance. ## Phase 3.5: Benchmark Evaluation Quantify plugin performance after testing. Uses `Skill(skill="devtu-benchmark-harness")`. ```bash # Run lab-bench (20 MCQ) python skills/devtu-benchmark-harness/scripts/run_eval.py --benchmark lab-bench --mode plugin-only --n 20 # Run BixBench (computational, use first 20) python skills/devtu-benchmark-harness/scripts/run_eval.py --benchmark bixbench --mode plugin-only --n 20 # Analyze results python skills/devtu-benchmark-harness/scripts/analyze_results.py --results # Generate report python skills/devtu-benchmark-harness/scripts/generate_report.py --results --output BENCHMARK_REPORT.md ``` Compare with previous round. If any category regresses, prioritize fixing that skill/tool in Phase 4. ## Phase 4: Fix & Commit 1. Implement verified fixes (see [references/bug-patterns.md](references/bug-patterns.md) for code-level patterns) 2. **Run code-simplifier**: `Skill(skill="simplify")` — always after writing or modifying code 3. Lint: `ruff check src/tooluniverse/.py` 4. Verify syntax: `python -c "from tooluniverse. import "` 5. Test: `python -m tooluniverse.cli run ''` 6. Pre-commit hook pattern: stage → commit (fails, reformats) → re-stage → commit 7. Push: `git push origin ` > Also see `Skill(skill="devtu-code-optimization")` for reusable fix patterns and anti-patterns. ## Phase 5: Optimize (optional) After fixes are stable: - `Skill(skill="devtu-optimize-descriptions")` — improve tool descriptions - `Skill(skill="devtu-optimize-skills")` — improve research skill quality - `Skill(skill="devtu-docs-quality")` — validate docs accuracy ## Phase 6: Ship Invoke `Skill(skill="devtu-github")` or manually: 1. Rebase: `git fetch origin && git stash && git rebase origin/main && git stash pop` 2. `git push --force-with-lease origin ` 3. Create or update PR: `gh pr create` / verify with `gh pr view --json mergeable` 4. Verify `"mergeable": "MERGEABLE"` before reporting done **GitHub repo**: `mims-harvard/ToolUniverse` — always verify with `git remote -v` before pushing. --- ## Git Rules (CRITICAL) - **NEVER push to main** — all work on feature branches - **NEVER have multiple open fix PRs** — keep adding to current branch - **Always rebase before push**: `git fetch origin && git rebase origin/main` - **Commit message format**: no "BUG" terminology, use "Feature" or "Fix" - **No AI attribution** in commits ## Common Issue Categories | Category | Signal | |----------|--------| | Silent parameter miss | Wrong-field check; param ignored | | Always-fires conditional | `.get("field")` on wrong type | | Silent normalization | Auto-transform not disclosed | | Wrong notation/case | Gene fusions, Title Case names | | Substring match | Short symbol returns multiple targets | | try/except indent | Mismatched → SyntaxError | Full patterns → [references/bug-patterns.md](references/bug-patterns.md) ## Round Tracking After each round: advance counter, update patterns file, keep this SKILL.md under 150 lines. **Current round: 127** (rounds completed: 52-126)

相关技能

写作与研究

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消费的优化型,具有清洁的结构化结果,答案生成,以及原始内容提取. 最适合研究任务、新闻查询、实况调查和收集权威来源.