[HN Gopher] Show HN: Skrun - Deploy any agent skill as an API
___________________________________________________________________
Show HN: Skrun - Deploy any agent skill as an API
Author : frizull
Score : 36 points
Date : 2026-04-08 12:34 UTC (10 hours ago)
(HTM) web link (github.com)
(TXT) w3m dump (github.com)
| frizull wrote:
| Hey HN.
|
| My colleague built this because he wanted to use his skills
| outside of Claude Code.
|
| With this project you can expose your skills as an API endpoint
| in under 2 minutes.
|
| If you could have a look at the repo and give your feedback, it
| would be much appreciated.
|
| Thanks!
| jonnycoder wrote:
| This is clever and provides a clean alternative to using custom
| plugins and mcp servers for doing code reviews.
|
| For example, with the degradation of Claude in the past 1-2
| months, I am always asking Codex to review Claude's plans and
| vice versa and I get excellent results that way.
|
| Also, making a skill an API call allows for easy deployment if
| the security around tool calling could be isolated in an
| ephemeral sandbox.
| Tarcroi wrote:
| Thanks! Sandbox deployment is planned in the roadmap. I
| already have a RuntimeAdapter interface in my architecture
| that I'll use to isolate the VMs. I'm doing exactly the same
| thing: I'm cross-referencing the models to challenge their
| plan, and my code reviewer agent's API is a big help.
| senthilnayagam wrote:
| sounds interesting, lets me test the skills I created and
| collected over the last few months
| Tarcroi wrote:
| Hi, I'm the "colleague", Impatient to have your feedback!
| hmartin wrote:
| Thanks for sharing a cool project! Just fyi, more idiomatic
| English would be "eager to have your feedback" since
| "impatient" implies frustration.
| Tarcroi wrote:
| Ha, thanks for the correction! I'll remember that!
| sergioisidoro wrote:
| This looks like a security nightmare in case someone decides to
| publish this interface publicly. Prompt injection to exfiltrate
| sensitive Information being on the top of the list.
| Tarcroi wrote:
| You're right. For now, it's only local. For a public
| deployment, the idea is to have sandboxes and verification
| steps. That won't completely eliminate the risk of prompt
| injection, but so far no solution has managed to completely
| resolve this problem.
___________________________________________________________________
(page generated 2026-04-08 23:00 UTC)