@rauchg@andrewqu also cooking up a few things that make this much more interesting, beyond just managing dependencies. let’s talk?
https://t.co/MQACYorXzY
`sk` has a few things that are bettter (I’m biased)
- transparently understands/support claude-plugins for other agents (extract skills from claude-plugins)
- agents.toml, the package.json for agent skills. makes it dead simple for skills to depend-on other skills!
- working on an agent-agnostic package format and registry (a la npm)
The ultimate life hack is the ability to quickly reset and recover. From a bad interaction. From a bad day. From a missed workout. From a poor decision. You can start over whenever you want. You can't always control what happened, but you can control how long you carry it.
@andrewqu@shuding Yes, this is the way.
Check out `sk` - it’s a more complete npm-for-agent-skills. We’re adding support for commands and hooks as well. Works across all agents
@dguido@trailofbits Looks great! We’re building skills-supply (`sk`) - a universal package manager for skills (npm for skills) that works with claude, codex, opencode, amp, factory, etc…
Can I submit a PR to update the readme to use `sk`?
@rauchg@reactjs@nextjs@shuding I've built a harness-agnositc skills package manager called `sk`. It's like npm but for agents. going to add support for commands as well.
would you be interested. in using it for this? the UX becomes:
```
sk pkg add vercel/react-best-practices
sk sync
```
i'm building skills-as-a-service.
we've already built a harness-agnostic skills package manager `sk`, which let's you install skills anywhere.
we're adding the ability to charge money for skills (one-time and subscription)
would anyone be interested in this?