- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
SELM manages agent skills as a library rather than as a single document. Each skill has a task category, a confidence score adjusted by LLM up- and down-votes, and a utility score tracked from task rewards. For each task, SELM retrieves skills from the task's category and a general category, ranked by relevance and utility. It then analyzes trajectories separately for each category, turns the analyses into add, edit, vote, and delete operations, keeps an update only if the selection score improves, and retires skills with low utility or confidence. SELM is evaluated on four benchmarks and three target models, and achieves the best score on most benchmarks.
Critical strengths
S1. The paper addresses a practical problem for multi-skill agents: as skills accumulate, the agent must decide which skills to retrieve, which to update, and which to remove. SELM answers these questions with one concrete design, using per-skill utility and confidence scores, explicit library constraints, and a complete algorithm.
S2. The evaluation is broad. It covers four benchmarks, three target models, and two execution settings, and compares against both single-document and multi-skill baselines. SELM achieves the best score on most benchmarks.
Critical weaknesses
W1. The novelty is limited. Most components come from prior work. The paper states that its fast and slow updates follow prior work, and its related work already cites methods that keep separate skills for different task types, validate candidate skills, and manage a skill library over its lifecycle. On top of these, SELM mainly splits skills by task category and adds per-skill scores for retrieval and removal. Overall, the method is a combination of existing components rather than a new idea.
Questions for authors
Q1. Retrieval and trajectory analysis both rely on a category label for each task. Where do these labels come from for each benchmark, and are they needed at test time?
Q2. The utility score u(s) is the average reward of the tasks that retrieved the skill, with no comparison to the same tasks solved without it. It may therefore reflect task difficulty as much as the skill's usefulness. This matters because utility has a larger weight than relevance in retrieval (wu = 0.6), and skills with utility below 0.05 are retired. How does SELM separate a skill's contribution from the difficulty of the tasks it is retrieved for?
3 comments
Q2. Utility estimation and task difficulty
Admittedly, task difficulty can affect skills' utility estimation. However, SELM uses several designs to mitigate its effects on the utility signal and downstream decisions.
First, we prioritize soft rewards for utility updates. Soft rewards retain partial credit when a difficult task falls short of full success, reducing the chance of repeated zero feedback under binary scoring. During retrieval, specialized skills compete within the task category alongside general skills, and ranking combines utility with task relevance.
Second, SELM reduces the influence of individual utility estimation errors by aggregating utility scores during library updates. Instead of relying on a single skill's utility, SELM averages the utility scores of all retrieved skills for each task. This reduces the impact of extreme individual scores on trajectory selection. The selected trajectories are then grouped by task category and jointly analyzed to generate targeted skill updates. Finally, candidate libraries are evaluated on a selection set before the updates are accepted, providing an additional check on overall performance.
Our ablation results support the effectiveness of these mechanisms. On SpreadsheetBench (Table 2), the full SELM achieves 56.5%, compared with 46.3% without utility scores and 49.2% without utility-aware ranking. Removing the validation gate further reduces performance to 42.5%. These results show that utility-based retrieval and library validation both contribute to overall performance. They also suggest that utility provides a useful signal despite its potential estimation bias.
To assess whether utility reflects a skill’s contribution, we conducted a skill-removal experiment across task difficulty levels. The results show that removing the highest utility injected skill reduced performance across difficulty tiers, indicating that high utility skills provide measurable performance benefits across difficulty levels, including challenging tasks, rather than merely being associated with easy tasks. For each task, we compare the full injected skill set with the set that removeing the injected skill with the highest stored utility, holding all other skills and execution settings fixed. The results below shows that removal would lower overall accuracy, dropping 16.6, 8.5, and 12.5 percentage points on easy, medium, and hard tasks, respectively. We will add the table to the appendix later.
| Difficulty | Tasks Num | Soft Acc. with full skills (%) | Soft Acc. without top-utility skill (%) | Δ (pp) |
|---|---|---|---|---|
| All | 77 | 69.8 | 59.7 | 10.1 |
| Easy | 6 | 83.3 | 66.7 | 16.6 |
| Medium | 47 | 76.6 | 68.1 | 8.5 |
| Hard | 24 | 54.2 | 41.7 | 12.5 |
Thank you for the detailed response and additional experiment. My remaining concern is that the contribution is still limited, as the method mainly combines existing update, validation, and lifecycle management components around task categories, so I will maintain my current assessment.
Thank you for recognizing our work. We believe SELM's contribution lies in systematic library management for skill, and we will detail its innovation compared to existing work.
W1. Contribution and Novelty
First, SELM introduces a holistic skill library management system. Prior work has made progress in skill acquisition, evolution, and lifecycle management. Methods such as EvoSkill and Memento-Skills primarily focus on acquiring and improving skills, while SkillOps and MUSE-Autoskill explore library health, reliability, and lifecycle management. However, a key challenge remains when skills continuously accumulate and evolve: improvements to individual skills may lead to worse library-wide performance. For example, updates that improve sheet-level tasks may introduce regressions in cell-level tasks, while outdated or ineffective skills may remain retrievable and interfere with future execution. Existing mechanisms for skill evolution do not, by themselves, fully address these interactions between skill updates, retrieval, and retention. Without systematic management of the entire library, these problems will accumulate, making library become increasingly difficult to maintain, and its overall performance may decline despite the growing number of skills.
To address this challenge, SELM introduces a systematic approach to managing the entire skill library. First, SELM analyzes execution trajectories from different task categories separately to identify problems and generate targeted skill updates. This reduces interference between different types of tasks. Second, SELM uses utility and confidence scores to guide skill retrieval and removal, helping retain useful skills and eliminate ineffective ones. Finally, SELM evaluates the updated library on a selection set and accepts changes only when they improve its performance. Together, these mechanisms allow SELM to improve the library as a whole, rather than simply accumulating or optimizing individual skills.
Our experiments support the importance of this management process. Table 3 shows that adding five skills in the first epoch does not immediatly improve accuracy. Table 2 further shows that removing validation, utility scores, or the graveyard reduces performance from 56.5% to 42.5%, 46.3%, and 50.4%, respectively.
Q1. Category sources and test-time requirements
First, SELM does not require ground-truth category annotations at test time, but task categories inferred from task description is needed at test time , for they are important content of our method. When a new task arrives, SELM can leverage an LLM to infer its category from the task description. The category is then used for retrieval. We will describe the category inputs in the appendix.
Second, all methods are evaluated under the same data configurations to ensure fair comparisons. When reproducing existing baselines, we observed that some eimplementations expose task type information to the agent, such as the instruction type in SpreadsheetBench. To maintain consistency with these settings, we provide the same task text and metadata to all baselines, which may include category information in certain benchmarks. We acknowledge that access to complete metadata may influence agent performance. However, since all methods receive identical task information and metadata, we believe the comparisons remain fair and the demonstrated advantages of SELM remain valid.