skill-evolution
- Repo stars 815
- Author updated Live
- Author repo ScienceClaw
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @beita6969 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- External requests
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: skill-evolution
description: Track and improve skill effectiveness over time using VOYAGER-style skill library patterns. Use…
category: engineering
runtime: no special runtime
---
# skill-evolution output preview
## PART A: Task fit
- Use case: Track and improve skill effectiveness over time using VOYAGER-style skill library patterns. Use when: analyzing which tools/strategies worked best, proposing skill improvements, or storing reusable research patterns. NOT for: active research tasks or immediate problem-solving..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “When to Use / When NOT to Use / VOYAGER Skill Library Pattern” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Track and improve skill effectiveness over time using VOYAGER-style skill library patterns. Use when: analyzing which tools/strategies worked best, proposing skill improvements, or storing reusable research patterns. NOT for: active research tasks or immediate problem-solving.”.
- **02** When the source has headings, the agent prioritizes “When to Use / When NOT to Use / VOYAGER Skill Library Pattern” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; may access external network resources; usually needs no extra API key.
## Running Rules
- read files, write/modify files; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “When to Use / When NOT to Use / VOYAGER Skill Library Pattern”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: skill-evolution
description: Track and improve skill effectiveness over time using VOYAGER-style skill library patterns. Use…
category: engineering
source: beita6969/ScienceClaw
---
# skill-evolution
## When to use
- Track and improve skill effectiveness over time using VOYAGER-style skill library patterns. Use when: analyzing which…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “When to Use / When NOT to Use / VOYAGER Skill Library Pattern” and keep inference separate from source facts.
- read files, write/modify files; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "skill-evolution" {
input -> user goal + target files + boundaries + acceptance criteria
context -> When to Use / When NOT to Use / VOYAGER Skill Library Pattern
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | may access external network resources
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} 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
Decide Fit First
Design Intent
How To Use It
Boundaries And Review