Hey all, I spoke with @elegant-branch-54423 and we’re thinking of supporting the agentskills spec in

software-agent-sdk

. Are there any objections to this? If not, I’ll create some issues and we can try to get openhands to bang them out.

yay!

IMHO we definitely need this, thank you! I'm a bit confused though, I think John Mason was working on it last week in agent-sdk? For example here https://github.com/OpenHands/software-agent-sdk/issues/1452 There is some overlap, it seems

Sorry, I just wasn’t aware of this! I could drop this and let @curved-angle-80449 finish the work if he’s already on it

I am excited that we are all wanting compatibility with Agent Skills and Plugins! We have customers asking us for this too, hence why the parent PRD was created to explain the customer problem and use cases: https://github.com/OpenHands/OpenHands/issues/12085 I think we might have a scenario here where too many 'cooks are in the kitchen' - I don't mean that to be negative, but just something I am observing right now. AFAIK, we don't yet have developers assigned to the three underlying tickets: 1. Plugin 1.0 Definition software-agent-sdk#1440 2. OpenHands Cloud - REST API #12087 3. Organization-level Plugin Marketplace GUI #12088 Re: Plugin 1.0 Definition software-agent-sdk#1440, I think John-Mason has been experimenting and researching the new AgentSkills spec and helping us understanding the key differences; however, I do not believe he is critical path for this work given he holds several other responsibilities. Therefore, I think we need an engineer on the agent team to: • Get assigned to Plugin 1.0 Definition software-agent-sdk#1440 • Work with John-Mason to understand what he is learning in his AgentSpec ticket • Update the original ticket Plugin 1.0 Definition software-agent-sdk#1440 with any changes we think we need to incorporate. • Begin executing the work/ For business context, the OpenHands Plugins PRD is going to be an important priority for us in January. I need to work with @purple-thailand-64770 from our engineering team to make sure we get the work assigned for this one.

The main thing that confuses me a bit, and it was in John Mason's brainstorming issues, and I think you may have hit it in one of the draft PRs, @limited-student-10747, is the loading incompatibility: I started to write here but it got really long, so I made an issue just for that: https://github.com/OpenHands/software-agent-sdk/issues/1507

I’ve already started working on agentskills compatibility so I’m happy to continue working on it if nobody else is doing it. From my POV @calm-artist-7206 I’d like to support agentskills as the main priority, but ideally keep the parts that we implement above and beyond agentskills

This also touches the

AGENTS.md

issue, which is another (ish) emerging standard... I'm thinking now that maybe we can simplify if we migrate our repo.md (all of those of repo type) to it

Yeah, agreed. repo.md is basically the same as agents.md

I don't know, I thought here there are 4 of them, which I don't fully understand https://github.com/OpenHands/software-agent-sdk/pull/1484/files#diff-045a21226c9f93a6afc623d3e3fa9bd9ba7f5f27172d038ab4674f53a08e093aR68

Going back to your comments @elegant-branch-54423, I think agentskills is the first step to plugin support no matter what way we look at it (since plugins are a superset of agentskills), so I could probably finish agentspec support over the next week or so, and then we could circle back to the other issue.

It's my understanding as well, Agentskill packages can be just copied in

Got it, I’ll go back and take a closer look. That’s still a draft PR (read: vibe-coded by openhands), so I’ll look at your description and try to clean up that one.

On a side note. We actually supported agentskills since Xingyao made them a long time ago under the form of

scripts + some prompt description

, and of course microagents as markdown. It's... interesting that simply their combination seems to be The New Thing. 🫠

Agreed @limited-student-10747 - AgentSkills compatibility needs to be done anyways. And yes agree it's a precursor to Plugins. Appreciate your help on this 🙏

I think we load

AGENTS.md

,

CLAUDE.md

, and

GEMINI.md

. But we load them all the time, which is actually a problem: claude and gemini should be only when that LLM is active for the agent, while AGENTS has been the OpenAI version; it's spreading to quite a number of LLMs/agentic harnesses I think; and people including myself have copies or symlinks between

AGENTS.md

and

repo.md

, which actually means the Agent gets them twice in context. I mean, it seems to me we could simplify everyone's life if we migrate our permanent skills to it. It's the reason why in this PR, I dealt only with

CLAUDE.md

and

GEMINI.md

, which are special cases, because I feel maybe we could treat

AGENTS.md

differently, it's not just "the GPT version of Claude.md": #1328 Load model-specific repo instructions (CLAUDE.md for Claude only, GEMINI.md for Gemini only)

ooo that makes sense Engel. So basically: • In general, we should replace repo.md with AGENTS.md going forward (but preserve backward compatability). Update docs to reflect preference for AGENTS.MD naming convention. • when using Claude or Gemini, and the repo has a CLAUDE.md or GEMINI.md (respectively), load those; else, load AGENTS.MD

Yes, I think so. 🤔 Tiny note:

replace repo.md with AGENTS.md going forward

where "repo.md" means here our permanent skill files, so actually any .md file in

.openhands/skills

without a trigger; so it includes e.g.

local_vscode.md