Actually it's "/magpie-setup" :) -> and the only two skills you have in youre repo are the setup ones. All the other skills are dynamically set-up when maintainer or contributor decides to "setup Magpie" on their own system.
On Thu, Jul 9, 2026 at 4:41 PM Jarek Potiuk <[email protected]> wrote: > Yes. Absolutely Magpie after adoption is only usable when you run > `/setup-magpie` in your local environment. Other than that those are just > dangling skills. > > Also the solution we are using for the ambiguities of AGENTS.md is > symbolic links. My recommended solution is to use AGENTS.md and a symbolic > link to it named CLAUDE.md. > > Just to explain why: AGENTS.md is part of the independent (kind of) - but > at least multi-actor Agentic Foundaiton (run as one of the Linux Software > Foundation sub-foundations), You can se all the details at > https://agents.md/. > This is actually why we could implement Magpie as a "vendor neutral" > solution. > > Pretty much all agentic solutions follow AGENTS.md (including Claude). > Magpie aims to be 100% vendor neutral (and it's not only aspirational - we > actually measure it - see > https://magpie.apache.org/architecture/#vendor-neutrality - it has a > chapter about "LLM & agent-integration neutrality" - and while all the > agent harness we have is already agnostic, some of the features > (security/privacy related) are multi-agentic-solution - but Claude, Open > Code, Kiro are already supported in all of them, Codex on the way and > contributions are welcome for any other agentic CLI. > > One thing Magpie currently does during setup is place agentic SKILLs in > the neutral ".agents" folder and symbolically link them from > ".claude/skills". ".github/skills" -> because that part is not yet fully > "resolved" - but it's also easy to fix when there will be a global standard > on where to place them - https://github.com/agentskills/agentskills is an > open standard that everyone follows, but there is not yet established > standard "where" to put them to be discoverable. > > But those are just symlinks dangling, and we do not force it - if adopting > project uses different convention - Magpie will just follow what is already > there. > > J. > > > > > On Thu, Jul 9, 2026 at 2:55 PM Vladimir Sitnikov < > [email protected]> wrote: > >> If Magpie is for on-demand use only, then it is fine with me. A dangling >> magpie-setup should not be a problem. >> We can evaluate if the added "project metadata" rots over time or not. >> >> >Microsoft APM, perhaps prepare a PR also? >> >> There's an open issue regarding AGENTS.md / CLAUDE.md handling: >> https://github.com/microsoft/apm/issues/1807 >> I will wait for the resolution and then consider adding it to JMeter. >> >> Vladimir >> >>
