# AI Agent Skills for 3D Slicer?
**URL:** https://discourse.slicer.org/t/ai-agent-skills-for-3d-slicer/45893
**Category:** Development
**Created:** [January 24, 2026, 11:52pm UTC](https://discourse.slicer.org/t/ai-agent-skills-for-3d-slicer/45893 "2026-01-24T23:52:43Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@mikebind](https://discourse.slicer.org/u/mikebind)
#### Post date: [January 24, 2026, 11:52pm UTC](https://discourse.slicer.org/t/ai-agent-skills-for-3d-slicer/45893/1 "2026-01-24T23:52:44Z")
I noticed in the most recent release notes for VS Code support for “Agent Skills”, which are an [open-standard platform-agnostic method of specifying helpful standards and domain-specific reference materials for AI Agents to reference](https://agentskills.io/home). This seems like potentially a great way of improving Slicer-specific coding abilities for AI agents. This could also be connected with improving the effectiveness of the prototype tool described in this thread [Developer Agent for Slicer - Support - 3D Slicer Community](https://discourse.slicer.org/t/developer-agent-for-slicer/44787). While I think this is still in the realm of rapid development (and so may not be stable), it does intend to be an open standard and currently looks like it has fairly wide support. Has anyone tried to use this framework in the context of Slicer extension development? I think there is an opportunity here to develop some shared community resources like a “skill repository” (skills are intended to be shareable). Personally, I am just starting to try to dip a toe into using an agent to explore developing a segment editor effect, so I don’t yet have enough experience to try to set up anything useful, it just seems like an intriguing and intuitively sensible approach to improving Slicer-related coding via agents. Any experience or thoughts?
---
### Author:  [@muratmaga](https://discourse.slicer.org/u/muratmaga)
#### Post date: [January 25, 2026, 12:22am UTC](https://discourse.slicer.org/t/ai-agent-skills-for-3d-slicer/45893/2 "2026-01-25T00:22:50Z")
Actually this was a topic I was planning to do as a project week project, alas other things intervened and I am not headed to Las Palmas.
I tried a few things on my end (as you linked above). The latest iteration of it uses DeepSeek inference engine on the JS2, which mitigates the need of API keys or subscriptions (though you have to either run inside the JS2 -which is not an issue if you are using MorphoCloud- or need to tunnel the request).
I am more interested in educational aspect of this, bringing people who are not used to coding and wouldn’t invest the time on their own but with a little bit of help would maybe be able to hack together something…
---
### Author:  [@pieper](https://discourse.slicer.org/u/pieper)
#### Post date: [January 25, 2026, 11:02am UTC](https://discourse.slicer.org/t/ai-agent-skills-for-3d-slicer/45893/3 "2026-01-25T11:02:30Z")
A related project will be going on at Project Week:
[https://projectweek.na-mic.org/PW44\_2026\_GranCanaria/Projects/ClaudeScientificSkillForImagingDataCommons/](https://projectweek.na-mic.org/PW44_2026_GranCanaria/Projects/ClaudeScientificSkillForImagingDataCommons/)
Informally I know there will be a lot of discussion about how these tools are changing out coding habits and how they are working out for developers and users with more or less experience. We’ll try to capture those experiences and publish any experiments that come up during the week.
---
### Author:  [@pieper](https://discourse.slicer.org/u/pieper)
#### Post date: [June 5, 2026, 3:48pm UTC](https://discourse.slicer.org/t/ai-agent-skills-for-3d-slicer/45893/5 "2026-06-05T15:48:41Z")
See this thread for more recent developments: [New slicer-skill ai tool](https://discourse.slicer.org/t/new-slicer-skill-ai-tool/46243)
---
### Author:  [@Hemran\_313](https://discourse.slicer.org/u/Hemran_313)
#### Post date: [June 6, 2026, 7:57pm UTC](https://discourse.slicer.org/t/ai-agent-skills-for-3d-slicer/45893/6 "2026-06-06T19:57:31Z")
I think its a pretty interesting idea, one of the biggest issues with AI tools and slicer development is that they often dont know much about Slicers APIs and development patterns. Having shared “skills” or reference material could help a lot with that. Even a small community repository covering common tasks like module creation, Segment Editor effects, and MRML usage could make AI generated code much more accurate.
---
### Author:  [@Hemran\_313](https://discourse.slicer.org/u/Hemran_313)
#### Post date: [June 6, 2026, 7:58pm UTC](https://discourse.slicer.org/t/ai-agent-skills-for-3d-slicer/45893/7 "2026-06-06T19:58:04Z")
good, saw it.
> [@New slicer-skill ai tool](https://discourse.slicer.org/t/new-slicer-skill-ai-tool/46243):
>
> After learning from [previous experiments, several productive discussions](https://github.com/pieper/slicer-skill?tab=readme-ov-file#related-projects) at project week and at the [last developer meeting](https://github.com/pieper/slicer-skill?tab=readme-ov-file#related-projects), I put together this [slicer-skill](https://github.com/pieper/slicer-skill) that can be used with coding agents like Claude code. It involves pulling down all the source code from Slicer and libraries like VTK, ITK, etc, together with all the discourse archives and other material like the source code for all the extensions. It also includes a new mcp server so that it can iterate on doing programming tasks. I thi…
---
### Author:  [@Hemran\_313](https://discourse.slicer.org/u/Hemran_313)
#### Post date: [June 29, 2026, 9:56am UTC](https://discourse.slicer.org/t/ai-agent-skills-for-3d-slicer/45893/8 "2026-06-29T09:56:07Z")
I think its a pretty interesting idea, one of the biggest issues with AI tools and slicer development is that they often dont know much about Slicers _[`APIs`](https://speedport-ips.de/)_ and development patterns. Having shared “skills” or reference material could help a lot with that. Even a small community repository covering common tasks like module creation, Segment Editor effects, and MRML usage could make AI generated code much more accurate.
> [@Hemran\_313](#):
>
> I think its a pretty interesting idea, one of the biggest issues with AI tools and slicer development is that they often dont know much about Slicers APIs and development patterns. Having shared “skills” or reference material could help a lot with that. Even a small community repository covering common tasks like module creation, Segment Editor effects, and MRML usage could make AI generated code much more accurate.
It could also help new developers get started faster by giving AI agents reliable examples to follow instead of relying on generic Python or Qt code that doesn’t fit Slicer well. If the community keeps those skills updated alongside new [`Slicer`](https://fritzboxlogins.de/) releases, I think it could become a really useful resource.