detkin

7 ms·

1.
by detkin 2mo ago
How do you concretely solve this for your marketing team? What’s the tech stack you have in place to support them?
2.
by detkin 2mo ago
A repo, if it’s not overly complex, is a great place to store skills for all the reasons you list. It’s just not the only place where skills are super valuable.
3.
by detkin 2mo ago
I completely agree and sx tries to make it easier to share, not just on one project/repo but across teams. For example, we have a collection of skills that have to do with brand marketing and blog writing. But developers use these too
4.
by detkin 2mo ago
The one place I’ve seen this break down on teams is when a skill gets improved or adjusted. If everyone is copying it you end up not knowing which the best and most accurate. We worked with a team that had 5 copies that had all drifted. Tha
5.
by detkin 2mo ago
It also wouldn't surprise me if the model companies ship a strong version of this to try to lock us all in a bit more. I hope that's not the case, or at the very least one storage and distribution system will work for all harnesse
6.
by detkin 2mo ago
That makes sense. The one thing that really bugs me about git sharing is when you have different repos but want to share the same collection of skills. We have three different golang projects/repos. They follow very similar patterns an
7.
by detkin 2mo ago
Very cool, sounds like you have some technically open-minded co-workers. Do you just create a claude or codex plugin in git for them? Since they likely aren't working against any code repos?
8.
by detkin 2mo ago
sx has a git vault storage layer, or a local file layer or a server backed vault. The thing it buys you over vanilla git is that you don't have to sym-link dirs for different AI harnesses. And, you can share skills across repos and tea
9.
by detkin 2mo ago
Hey man! Yeah, many of the non-techincal folks I've spoken to are using claude.ai or chatgpt.com. But I've been amazed at how many are using Claude CoWork or even Claude Code. The theme seems to be wanting the same set of knowledg
10.
by detkin 2mo ago
I agree that that works pretty well for developers who work with a code repository everyday. But, if you're working on a mono-repo, you can end up with more skills loading than you'd like pretty quickily. Have you had success with
11.
Show HN: Sx 2.0 – Share AI skills with your team through a Dropbox folder(sleuth-io.github.io)
44 points by detkin 2mo ago|33 comments
12.
A package manager for AI assets (and why the lock file is per-user)(sleuth-io.github.io)
4 points by detkin 3mo ago|0 comments
13.
by detkin 4mo ago
Yes. You can just point sx add at your existing skill directories and it will put them into the git vault which you can easily share via Github access control.
14.
by detkin 4mo ago
Thank you for sharing, this is exactly the kind of thing I'm interested in learning. Is this just for engineering or is it being used for other functions, like Marketing and HR as well?
15.
by detkin 4mo ago
Very cool! What would you say is the biggest learning you've had about how people are using it?
16.
by detkin 4mo ago
We added the idea of dependencies for exactly that reason. However, honestly, I've not see any usage of it in the wild. Seems like most folks are ok with either bundling them and calling it a day or not really worrying about it. Very i
17.
by detkin 4mo ago
Say more, what kind of tools are you thinking about? The tool support is certainly one of the key pillars of the project so we're open to any tool additions that will help people get value from the project.
18.
by detkin 4mo ago
lol, just s ... x, the two letters. We wanted something short and easy to remember
19.
by detkin 4mo ago
The sx vault also stores things in git, I agree that it's a pretty good medium for storage. My main argument is that just using vanilla git where you store it in the directory that the AI coding agent expects means that you can't
20.
by detkin 4mo ago
Hi HN — I'm one of the maintainers. The short version: sx treats skills, MCP server configs, slash commands, agents, hooks, and rule files as versioned packages. You define them once, push them to a vault (a local folder, a git repo, o
21.
Show HN: Sx – an open-source package manager for AI skills, MCPs, and commands(github.com)
50 points by detkin 4mo ago|28 comments
22.
Agent Skills move too fast for Git(sleuth.io)
2 points by detkin 5mo ago|0 comments
23.
by detkin 5mo ago
At some of the larger orgs that I've worked at each individual system had some level of RBAC. Often they would try to centralize around an Okta-style system, but the roles in there infrequently matched what was needed. In the places yo
24.
Without RBAC for Skills and MCP, your org has root access to your company(sleuth.io)
3 points by detkin 5mo ago|3 comments
25.
by detkin 6mo ago
Machine assisted, not fully machine generated ¯\_(ツ)_/¯
26.
by detkin 6mo ago
You're right, I used AI to help organize the content but we have spoken to almost 50 companies over the last 5 months and the messages and pains they have conveyed are real. How are you handing distributing your Agent Skills and MCP&#x
27.
by detkin 6mo ago
I hear you, results is a gray area. However, with the companies we spoke to results looks like increased productivity for their developers. It was a constant with all that they felt like 2 - 7 percent of their developers had made huge produ
28.
by detkin 8mo ago
Seems very interesting.
29.
by detkin 9mo ago
Skills have been really helpful in my team as we've been encoding tribal knowledge into something that other developers can easily take advantage of. For example, our backend architecture has these hidden patterns, that once encoding i
30.
Show HN: Automate best practices across your toolchain – Sleuth Automations(marketplace.sleuth.io)
20 points by detkin 3y ago|3 comments

More ›