MarkTechPost ★ 87 4 min

Microsoft’s SkillOpt Shows Optimized Agent Skill Artifacts Transfer Across Model Scales and Between Codex and Claude Code Harnesses

Agentic AIAI AgentsAI Paper SummaryOpinionSoftware Engineering

🔗 https://www.marktechpost.com/2026/08/05/microsoft-skillopt-agent-skill-transfer-portability/

📌 【Microsoft 研究】SkillOpt 實現 Agent 技能轉移:從 Codex 到 Claude Code 都能用的通用技能檔

TL;DR:SkillOpt 能將優化後的自然語言技能封裝成單一 Markdown 檔,實現跨模型與跨工具環境的技能轉移。

當我們在為 AI Agent 優化工作流程時,最頭痛的問題之一就是:在 A 工具環境下學到的「最佳實踐」,換到 B 工具或更小的模型時,還能用嗎?Microsoft 與多所大學合作開發的 SkillOpt 提出了新的解法:透過優化自然語言指令,讓 Agent 具備可移植的「技能檔案」。

🤔 解決「技能與環境綁定」的困境

目前的 Agent 技能優化往往依賴於微調(fine-tuning),這意味著技能與特定的模型參數緊密耦合。SkillOpt 則採用「文字空間優化」(text-space optimizer)的思路:

  • 凍結模型:目標模型(Target Model)在訓練過程中保持不變。
  • 優化器模型:由一個專門的優化模型讀取評分後的執行軌跡(rollouts),並提出「新增、刪除、替換」的編輯建議。
  • 單一檔案輸出:最終產出一個名為 best_skill.md 的 Markdown 檔案,這就是 Agent 的「技能清單」。

🧩 跨工具、跨模型的技能轉移實驗

研究團隊測試了技能在不同規模模型與不同開發工具(Harnesses)之間的遷移能力。這裡的關鍵指標不是「直接訓練」,而是「轉移後的效能能保留多少原本在目標領域訓練出的增益」。

📊 從 Codex 到 Claude Code:跨越工具界限的成功案例

研究中一個極具意義的發現是,在 Codex 環境下優化出的技能,竟然能直接應用在 Claude Code 上:

  • SpreadsheetBench 表現:在 Codex 中優化出的技能,讓 Claude Code 的分數從 22.1 提升至 81.8,甚至超越了從頭在 Claude Code 中訓練出的 80.4 分。
  • 為什麼這很重要? 因為 Codex 與 Claude Code 使用完全不同的工具 API 與指令介面。這證明 SkillOpt 學習到的是「程序性知識」(procedural knowledge),而非僅僅是針對特定工具的指令指令集。

💡 程序性技能 vs. 推理型技能

研究發現,技能的遷移率並不均勻,這取決於技能的本質:

  • 程序性技能(Portable):例如「先檢查工作簿結構與公式,再寫入靜態值」這種步驟化的流程。這類技能在跨環境時表現優異,因為其邏輯不依賴於特定的 CLI 工具。
  • 推理型技能(Tied to environment):這類技能與訓練環境的關聯較深,在跨環境轉移時效能下降較明顯(例如 Codex 到 Claude Code 在 LiveMath 任務中僅保留了 10% 的增益)。

⚠️ 部署與成本的優勢

對於工程師而言,SkillOpt 帶來了兩項實務上的改變:

  1. 一次訓練,隨處部署:訓練成本僅需支付一次(離線完成),且在部署時不需要額外的推理開銷(inference-time calls),因為技能已經內化在 Markdown 檔中。
  2. 可審核性(Auditability):與黑盒子的權重檔案不同,best_skill.md 是人類可讀的文字檔。每一項編輯都有 edit_apply_report.json 記錄,讓開發者可以清楚追蹤技能是如何被優化出來的。

🎯 實務啟示

如果你正在開發 AI Agent,SkillOpt 告訴我們:優化「如何做」的程序,比優化「答案是什麼」的推理更具擴展性。 透過將最佳實踐封裝成可讀的 Markdown 檔案,你可以實現「在成本最低的環境進行優化,並在實際產品環境中部署」的高效工作流。

🔗 來源

#AI #Agent #Microsoft #SkillOpt #MachineLearning #LLM #SoftwareEngineering #Productivity #AIResearch #Automation

原始資料 MarkTechPost · 收集於 2026-08-06
來源原標題
Microsoft’s SkillOpt Shows Optimized Agent Skill Artifacts Transfer Across Model Scales and Between Codex and Claude Code Harnesses
作者
Asif Razzaq
原始標籤
Agentic AI · AI Agents · AI Paper Summary · Applications · Artificial Intelligence · Editors Pick · Opinion · Software Engineering · Staff · Tech News · Technology
原始連結
https://www.marktechpost.com/2026/08/05/microsoft-skillopt-agent-skill-transfer-portability/

摘要原文

SkillOpt is a text-space optimizer developed by a team of researchers from Microsoft, Shanghai Jiao Tong University, Tongji University, and Fudan University. SkillOpt trains a single natural-language skill document while the target model stays frozen. An optimizer model reads scored rollouts and proposes bounded add/delete/replace edits. A held-out selection split accepts an edit only when the score strictly improves. The exported artifact is one file, best_skill.md . The transfer tables report three columns. Baseline is the target’s no-skill score. Direct is SkillOpt trained in-domain on that exact target. Transferred applies a skill trained elsewhere, with no further optimization. The useful comparison is not transferred versus direct. It is how much of the in-domain gain survives the move. Skills were trained on GPT-5.4 and deployed on smaller variants. Two rows deserve attention. SpreadsheetBench on GPT-5.4-mini keeps 82% of the in-domain gain. That is close to free reuse. The LiveMath row on GPT-5.4-nano is stranger: the transferred skill scores 28.8 against an in-domain SkillOpt result of 27.2. The paper reads this as evidence that some learned procedures are target-model agnostic. The GPT-5.4-nano SpreadsheetBench row is the weak one at 16%. Retention is not uniform, and the paper does not claim it is. Its stated bound is narrower: no row falls below the target’s no-skill baseline. Note the scope. All four rows stay inside one GPT family. Cross-family transfer, such as GPT to Qwen , is not tested. This is the section that matters most for deployment. All rows use GPT-5.5. The first row is the headline. A skill optimized inside Codex lifted Claude Code from 22.1 to 81.8. That slightly exceeds the 80.4 Claude Code reached by training its own skill from scratch. The two harnesses expose different tool and file APIs and different command surfaces. A skill that survives that shift is not encoding command recipes. The research paper attributes SpreadsheetBench’s portability to workbook-level procedures: structure-first inspection, formula-aware verification, and static-value materialization. Those hold regardless of which CLI runs the Python. LiveMath tells the opposite story. Codex → Claude Code retains only 10% of the in-domain gain. The asymmetry is worth sitting with. Procedural skills — how to inspect, verify, and format — appear to be the portable class. Reasoning-heavy skills appear more tied to their training environment. There is no Direct column here. No in-domain SkillOpt run on Omni-MATH is reported, so the comparison is against no-skill only. Gains are positive across all three model scales but small. The research paper’s reading is that the skill retained reusable mathematical procedure after both the test instances and the answer-format conventions changed. The mechanism is stated plainly in the research paper. All three execution modes: direct chat, Codex, Claude Code – consume the same best_skill.md file format. That shared contract is what makes the cross-harness experiment possible in the first place. The Codex harness renders the current skill to a per-task SKILL.md alongside task files, then reads back a compact execution trace. The Claude Code harness mirrors the same workspace contract through the claude CLI. Neither harness gets a bespoke skill format. The artifact’s shape supports portability too. Final skills run 379 to 1,995 tokens across the six benchmarks, with a median near 920. They are assembled from 1 to 4 accepted edits. The paper’s Figure 4 samples one learned rule per benchmark, and all are procedural rather than instance-specific. The SpreadsheetBench rule, verbatim: inspect workbook structure and formulas, then write evaluated static values across the full requested target range instead of relying on Excel recalculation. Training cost is paid once, offline, and measured. The research paper reports 0.6M to 46.4M training tokens per absolute test point, depending on benchmark. SpreadsheetBench sits at 0.6M per point; DocVQA at 46.4M. The optimizer model runs only during training and adds zero inference-time calls at deployment. If a skill trained in one harness holds up in another, that one-time cost spreads across environments. The Codex → Claude Code SpreadsheetBench result is the existence proof. It also implies you can optimize where tooling is cheapest and deploy where the product lives. The audit angle is separate and underrated. The deployed artifact is a text file a domain practitioner can read in minutes. Every change to it is traceable: each step records an edit_apply_report.json with per-edit accept and skip status. Portability plus inspectability is a different operational posture than shipping fine-tuned weights. Resources: Paper , GitHub , Project page , Docs , PyPI and Demo video Baselines referenced: GEPA , TextGrad , EvoSkill and Trace2Skill Benchmarks referenced: SearchQA , SpreadsheetBench , DocVQA , LiveMathematicianBench and ALFWorld The post Microsoft’s SkillOpt Shows Optimized Agent Skill Artifacts Transfer Across Model Scales and Between Codex and Claude Code Harnesses appeared first on MarkTechPost .

tencent/hy3:free 自動生成