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 interesting about the domain and workflows. Do you think domain could map to a team or is it different?
At your company how are you shipping your assets? How do you do the domain and workflow grouping?
we are shipping as plugins.
we have a internal cli that creates the plugin on the fly after you select the domains you want to work with. This cli is a standalone cli + wizard that does it all. Generally speaking, we have skills that are code related and mostly independent (ex: a skill to teach python how to log in our tech stack). Another type are skills related to our workflow (a skill to plan that outputs a file that is used in the next step "implement", together with a dev agent and so on)
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?
engineering, product managers, business people.
the problem we have right now is the repository (where to store the documents).
lets say i'm a business expert and want to use a skill to create a md file with all the info about some area. It is ok to learn claude/cursor, but to upload this generated material to git is another level of problem...
Makes sense. Would a tool that let non-tech people easily share and distribute skills without needing git be worth adoption? Would the info being shared just be skills or something else?
We are already distributing the skills without Git. We package everything (skills, assets, CLI, wizard) into a single file and distribute it.
The problem is collaboration without Git.
For example: I am a business person, someone sends me the skills/plugins, and I install them effortlessly. I use Claude Cowork to generate some financial information related to my area, and I need to share this information with the development team.
Right now, since I am not familiar with Git, I would probably upload it to Google Drive. The developers would then download it and push it to the repository in order to use it for coding.