Three rounds of automated repair add up to 12pp of consistency — and beat a mature production system by 13.76pp
Notes on SkillForge: Forging Domain-Specific, Self-Evolving Agent Skills in Cloud Technical Support (arXiv:2604.08618) — Xingyan Liu, Xiyue Luo, Linyu Li, Gang Huang, Jianfeng Liu, Hongli Qiao · April 2026 · Proceedings of the 49th International ACM SIGIR Conference on Research and Development in Information Retrieval
Note published · written by SkillFed’s research pipeline from the paper above · how these notes are made
AI-assisted notes · reviewed by SkillFed Skill evolutionSkillForge builds and maintains agent skills for cloud technical-support agents at Alibaba Cloud, closing a loop that most skill-authoring setups leave open. A Domain-Contextualized Skill Creator writes the initial skill by mining historical support tickets, tool-usage logs, and internal documentation — not a generic prompt working blind. From there, a three-stage pipeline (Failure Analyzer, Skill Diagnostician, Skill Optimizer) batches failed task executions, traces each one back to a specific section of the skill file, and rewrites only that section. The team ran it across five real cloud-support scenarios — Account, Domain, DNS, OSS, ECS — spanning 1,883 tickets and 3,737 tasks, with Qwen3-Max as the backbone and an LLM judge (validated at over 90% agreement with human experts) scoring each response against what a human engineer actually used to resolve the ticket.
Grounding skill creation in ticket history beats generating one generically, but the bigger lever is the self-evolution loop. Three rounds of diagnose-and-rewrite add up to roughly +9 to +12 points of strict consistency — no matter whether the skill started out generic, domain-mined, or hand-written by a human expert. Even the expert-authored skill, already the strongest starting point, still gains +10.99 points on its own — and after three rounds the evolved skill beats the mature, human-engineered production system it was measured against by +13.76 points. The gains taper, though: tool-use and tone errors keep shrinking round over round, but knowledge errors stop improving after round one. The authors trace that ceiling to contradictory historical answers, a deliberate policy against stuffing skills with case-specific facts, and tacit expertise that support staff never wrote down.
Key numbers
| Evaluation scale | 1,883 tickets / 3,737 tasks across 5 scenarios |
| Domain-grounded creator vs. generic creator | +4.3pp Strict CR / +3.6pp Lenient CR |
| Self-evolution gain after 3 rounds | +9.2 to +11.6pp Strict CR, any starting point |
| Evolved skill vs. production legacy system | +13.76pp Strict CR |
| Knowledge-failure reduction, round 1 to round 2 | 0% further reduction (plateau) |
Skills related to this research
Related notes
- Skill pass rates jump from 33.6% to 88.0% — with zero gradient steps →
- A skill library built by GLM-4.6 boosts GPT-4.1's task success by 10 points →
- 200k+ skills wired into one graph, +40% reward across three backbones →
- Skill synthesis that checks its own work: +3 to +10 accuracy points, only 6% of skills still backfire →
- 40,285 Skills Later, Supply Still Doesn't Match Demand →
- Auto-evolved skill specs beat hand-written ones by 7 points, at twice the constraint density →
- 0 of 9 add-skill edits improved pass rate; cost fell up to 31.7% vs. static bundles →
- Turning a corpus into a skill tree cuts RAG hallucination from 50% to 4.5% →
- Wrapping a harmful request inside a skill file nearly triples model harm scores, from 0.27 to 0.76 →
References
- SkillForge: Forging Domain-Specific, Self-Evolving Agent Skills in Cloud Technical Support (arXiv:2604.08618)
- Li et al., SkillsBench: benchmarking how well agent skills work across diverse tasks (arXiv:2602.12670)
- Zhao et al., Agent-in-the-Loop: a data flywheel for continuous improvement in LLM-based customer support (EMNLP 2025 Industry Track, arXiv:2510.06674)
- Zhang, Lazuka & Murag, Equipping agents for the real world with agent skills (Anthropic, Oct 2025)
- Yao et al., ReAct: synergizing reasoning and acting in language models (arXiv:2210.03629)