Agent审查
- 作者仓库星标 815
- 作者更新于 实时读取
- 作者仓库 ScienceClaw
- 领域
- 工程开发
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @beita6969 · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- 网络行为
- 允许外网请求
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: skill-evolution
description: Track and improve skill effectiveness over time using VOYAGER-style skill library patterns. Use…
category: 工程开发
runtime: 无特殊运行时
---
# skill-evolution 输出预览
## PART A: 任务判断
- 适用问题:代码实现、重构、调试或代码审查。
- 输入要求:目标材料、限制条件、期望输出和验收方式。
- 证据边界:围绕“When to Use / When NOT to Use / VOYAGER Skill Library Pattern”读取原文规则,不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断:确认你的需求是否属于代码实现、重构、调试或代码审查,并标出输入、限制和预期结果。
- **02** 执行计划:优先按“When to Use / When NOT to Use / VOYAGER Skill Library Pattern”拆成步骤,说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果:给出可复制的命令、文件改动、检查清单或内容草稿,并说明如何继续迭代。
- **04** 风险边界:结合 读取文件、写入/修改文件、会按任务需要访问外部网络、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件;会按任务需要访问外部网络;通常不需要额外 API Key。
- 先小样例验证,再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 原文没有稳定的斜杠命令要求。安装验证后通常全局生效,直接在对话里点名这个 Skill 并描述任务即可。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是:读取文件、写入/修改文件。
先用一个小任务确认它会围绕“When to Use / When NOT to Use / VOYAGER Skill Library Pattern”工作;涉及文件或命令时,先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作;如果输出泛泛而谈,就补充输入、边界和验收标准后重跑。
---
name: skill-evolution
description: Track and improve skill effectiveness over time using VOYAGER-style skill library patterns. Use…
category: 工程开发
source: beita6969/ScienceClaw
---
# skill-evolution
## 什么时候使用
- 把工程方向的常用动作沉淀成 Agent 可调用的技能 适合处理工程开发场景下的代码实现、调试、重构、测试或代码审查,核心价值是把输入、判断、执行、验证和交付边界固定下来,避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代…
- 面向代码实现、重构、调试或代码审查,优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「When to Use / When NOT to Use / VOYAGER Skill Library Pattern」组织步骤,不把推断写成作者事实。
- 读取文件、写入/修改文件;会按任务需要访问外部网络;通常不需要额外 API Key。
- 先跑小样例,确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown,不编造命令、平台或依赖。 作者原文负责流程事实;仓库文件负责来源和命令;流狐只补充适用场景、限制和质量判断。
skill "skill-evolution" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> When to Use / When NOT to Use / VOYAGER Skill Library Pattern
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件 | 会按任务需要访问外部网络
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
} Skill Evolution
Track tool and strategy effectiveness across research tasks, propose improvements to existing skills, and maintain a reusable pattern library inspired by VOYAGER's skill library architecture.
When to Use
- After multiple research sessions to identify improvement opportunities
- "Which search strategies work best for biomedical topics?"
- "Propose improvements to the literature-search skill"
- "Store this successful analysis pattern for reuse"
- When the science-evolution extension triggers post-session analysis
When NOT to Use
- During active research (focus on the task, reflect afterward)
- For one-off questions that don't need pattern storage
- For simple skill usage (just use the skill directly)
VOYAGER Skill Library Pattern
Inspired by VOYAGER (Wang et al., 2023), maintain a library of reusable research patterns:
Pattern Structure
{
"pattern_id": "lit-review-biomedical-v2",
"name": "Biomedical Literature Review",
"domain": ["biology", "medicine"],
"task_type": "literature_review",
"version": 2,
"description": "Optimized search strategy for biomedical topics",
"steps": [
"Search Semantic Scholar with MeSH-equivalent terms",
"Search PubMed via NCBI Entrez with MeSH filters",
"Cross-reference with ClinicalTrials.gov for ongoing trials",
"Citation chain top 3 papers (forward + backward)",
"Verify key genes/proteins in UniProt",
"Verify drug interactions in ChEMBL"
],
"tools_used": ["semantic-scholar", "ncbi-entrez", "uniprot-protein", "chembl-drug"],
"success_rate": 0.85,
"avg_quality_score": 21,
"times_used": 12,
"last_used": "2026-03-11",
"lessons": [
"PubMed MeSH terms are more precise than free-text for biomedical queries",
"Always check ClinicalTrials.gov for therapy-related topics",
"UniProt cross-references to PDB save a separate search step"
]
}
Pattern Operations
# Store a new pattern
curl -X POST http://localhost:18789/evolution/pattern \
-H "Content-Type: application/json" \
-d '{"pattern": {...}}'
# Search for patterns matching a new task
curl "http://localhost:18789/evolution/search?domain=biology&task_type=literature_review"
# Update pattern after use (increment times_used, update success_rate)
curl -X PATCH http://localhost:18789/evolution/pattern/lit-review-biomedical-v2 \
-d '{"success": true, "quality_score": 22}'
Skill Improvement Proposals
Analysis Framework
After 5+ uses of a skill, analyze its performance:
## Skill Analysis: [skill-name]
### Usage Statistics
- Times used: N
- Average quality score: X/25
- Success rate: Y%
- Common failure modes: [list]
### Strengths
- [What the skill does well]
### Weaknesses
- [Where the skill falls short]
- [Missing capabilities]
- [Incorrect or outdated guidance]
### Proposed Changes
1. [Specific change to SKILL.md]
- Rationale: [why]
- Expected impact: [improvement area]
2. [Another change]
- Rationale: [why]
- Expected impact: [improvement area]
### Priority: [high/medium/low]
Automated Improvement Detection
Track these signals across research sessions:
| Signal | Indicates | Action |
|---|---|---|
| Repeated tool failures | API endpoint changed or unreliable | Update SKILL.md with workaround |
| Consistent low scores in one dimension | Skill gap in that area | Add guidance for that dimension |
| User corrections | Skill provides wrong guidance | Fix the incorrect guidance |
| New API discovered | Opportunity to expand | Add new tool instructions |
| Cross-domain pattern success | Transferable knowledge | Create cross-domain pattern |
Cross-Domain Knowledge Transfer
Identifying Transferable Patterns
Some research patterns work across disciplines:
- Citation chain analysis — Works for any field with citation data
- Database cross-verification — Applicable whenever primary data exists
- Effect size reporting — Standard across quantitative disciplines
- PICO framework — Adaptable beyond medicine (SPIDER for qualitative)
- Visualization standards — Journal figure requirements are similar
Transfer Process
When a pattern succeeds in domain A, evaluate for domain B:
- Are the tools available? (e.g., does domain B have equivalent databases?)
- Are the methods appropriate? (e.g., meta-analysis needs comparable studies)
- What adaptations are needed? (e.g., different search terms, different databases)
- Store as a new domain-specific variant
Evolution Metrics
Skill Health Dashboard
| Skill | Uses | Avg Score | Trend | Health |
|-------|------|-----------|-------|--------|
| literature-search | 45 | 22/25 | +1.2 | Healthy |
| statsmodels-stats | 12 | 18/25 | -0.5 | Needs attention |
| semantic-scholar | 38 | 23/25 | +0.8 | Healthy |
| meta-analysis | 3 | -- | -- | Too few uses |
Trend Analysis
- Improving: Score trending up → skill guidance is effective
- Declining: Score trending down → investigate (API changes? outdated guidance?)
- Stable: No trend → working as expected
- Insufficient data: < 5 uses → collect more data before drawing conclusions
Integration with science-evolution Extension
This skill works with the science-evolution extension:
- Extension tracks tool usage and outcomes automatically
- Stores data in
~/.openclaw/science-evolution.db - Provides API endpoints for pattern storage and retrieval
- Triggers post-session analysis when enough data accumulates
Best Practices
- Don't optimize prematurely — wait for 5+ uses before proposing changes
- Track both successes and failures for each pattern
- Version patterns so you can roll back if a change hurts performance
- Cross-reference reflections (research-reflection) with evolution data
- Focus improvements on the highest-impact skills first
- Keep the pattern library curated — remove patterns that are never reused
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核