菜单
Analyzes skill descriptions for trigger quality — scores clarity, keyword density, and specificity, then suggests rewrites that improve discovery accuracy.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Handles PR review feedback by fetching comments, grouping issues, fixing one group at a time, and verifying before replies.
Reviews whether a skill will trigger reliably, guide useful behavior, avoid overlap, and produce testable outcomes.
Diagnoses OpenClaw provider, fallback, channel, MCP, and gateway config issues with read-only scans and stateful summaries.
Tracks required validation gates, records pass/fail/waived results, and reports readiness before task completion.
YAML-based delegation grant ledger — issues, validates, and tracks scoped permission grants for sub-agent expansions with token budgets and auto-expiry.
Walks the memory DAG to recall detailed context on demand — query, expand, and assemble cited answers from hierarchical summaries without re-reading raw transcripts.
| name | tool-description-optimizer |
| version | 1.0 |
| category | openclaw-native |
| description | Analyzes skill descriptions for trigger quality — scores clarity, keyword density, and specificity, then suggests rewrites that improve discovery accuracy. |
| stateful | true |
A skill's description is its only discovery mechanism. If the description is vague, overlapping, or keyword-poor, the agent won't trigger it — or worse, will trigger the wrong skill. Tool Description Optimizer analyzes every installed skill's description for trigger quality and suggests concrete rewrites.
Inspired by OpenLobster's tool-description scoring layer, which penalizes vague descriptions and rewards keyword-rich, action-specific ones.
| Metric | What it measures | Weight |
|---|---|---|
| Clarity | Single clear purpose, no ambiguity | 2x |
| Specificity | Action verbs, concrete nouns vs. vague terms | 2x |
| Keyword density | Trigger-relevant keywords per sentence | 1.5x |
| Uniqueness | Low overlap with other installed skill descriptions | 1.5x |
| Length | Optimal range (15–40 words) — too short = vague, too long = diluted | 1x |
| Grade | Score range | Meaning |
|---|---|---|
| A | 8.0–10.0 | Excellent — high trigger accuracy expected |
| B | 6.0–7.9 | Good — minor improvements possible |
| C | 4.0–5.9 | Fair — likely to miss triggers or overlap |
| D | 2.0–3.9 | Poor — needs rewrite |
| F | 0.0–1.9 | Failing — will not trigger reliably |
python3 optimize.py --scan # Score all installed skills
python3 optimize.py --scan --grade C # Only show skills graded C or below
python3 optimize.py --skill <name> # Deep analysis of a single skill
python3 optimize.py --suggest <name> # Generate rewrite suggestions
python3 optimize.py --compare "desc A" "desc B" # Compare two descriptions
python3 optimize.py --status # Last scan summary
python3 optimize.py --format json # Machine-readable output
Step 1 — Run a full scan
python3 optimize.py --scan
Review the scorecard. Focus on skills graded C or below — these are the ones most likely to cause trigger failures.
Step 2 — Get rewrite suggestions for low-scoring skills
python3 optimize.py --suggest <skill-name>
The optimizer generates 2–3 alternative descriptions with predicted score improvements.
Step 3 — Compare alternatives
python3 optimize.py --compare "original description" "suggested rewrite"
Side-by-side scoring shows exactly which metrics improved.
Step 4 — Apply the best rewrite
Edit the skill's SKILL.md frontmatter description: field with the chosen rewrite.
These words score 0 on specificity — they say nothing actionable:
helps, manages, handles, deals with, works with, does stuff, various, things, general, misc, utility, tool for, assistant for
scans, detects, validates, generates, audits, monitors, checks, reports, fixes, migrates, syncs, schedules, blocks, scores, diagnoses
Scan results and per-skill scores stored in ~/.openclaw/skill-state/tool-description-optimizer/state.yaml.
Fields: last_scan_at, skill_scores list, scan_history.