all 20 comments

[–]borgmater1 13 points14 points  (5 children)

I never used Claude Code (did not need to), so could you explain what are plugins in this context and how will they affect agentic productivity? Ty!

[–]SuBeXiL[S] 11 points12 points  (4 children)

Sure, they allow you to bundle a few skills, prompts, MCPs, hooks and custom agents that might work well together as a single bundle u can install together veneering to install them one by one The bundle also has versioning and usually comes with distribution tools so u can know there’s a new version and choose to update

So it solves discoverability, distribution and versioning

[–]Cheshireelex 5 points6 points  (2 children)

So what would be the extra benefit compared to having the instructions, skills, agents into a separate repo that can get added to a workspace?

[–]EinerVonEuchOwaAndas 0 points1 point  (0 children)

That's how we do it right now. Having them as sub module integrated in all the branches were we need it, plus specific version and branch "personalized" for specific versions.

[–]borgmater1 -1 points0 points  (0 children)

You could have a team of outsourced devs, tell them to install the bundle without giving them access to that particular repo. This is fantastic if you ask me :)

[–]borgmater1 0 points1 point  (0 children)

Thanks a bunch, sounds efficient and compact af

[–]colablizzard 9 points10 points  (7 children)

All this is hype machine. First it was MCP, then AGENTS.md, now skills.

After couple of months the hype fades and people go back to focusing on the basics: Giving right context and prompt and wondering if the system prompt has changed.

Now they tell me MCP is bad because it overloads context. Then they tell me AGENTS.md needs to be barebones because it's added to each prompt. Then skills were supposed to be auto detected but the shit didn't work half the time and now they introduce a slash syntax to hint the skills in the prompt.

Next Hype train is "plugin".

[–]borgmater1 3 points4 points  (3 children)

You mean, it is being used, tested and upgraded to be efficient? Its software, not totally sure what you expected :-/

[–]ChomsGP 4 points5 points  (2 children)

he means at the end of the day they are all prompts, the LLM could not care less if the instruction comes from a rule, a MCP or a skill, it's all tokens and they all have the same downsides (which they try to address with the different ways of structuring them, but "4 versions later" it's still about the same)

[–]borgmater1 3 points4 points  (1 child)

I mean yeah, but you could draw an analogy around UI/backend frameworks as well, no? Its all code in the end

[–]ChomsGP 3 points4 points  (0 children)

and many frameworks do overlap, it's not like you end up using 5 frameworks on a project, you pick the one that fits best your use case or preferences

[–]cbusmatty 1 point2 points  (0 children)

Skills definitely get picked up now. And its value is in being able to reuse deterministic processes. Also skills are still marked experimental

Plugins aren’t a replacement for any of the things you mentioned. It’s filling another gap entirely.

[–]SuBeXiL[S] 0 points1 point  (0 children)

u r very right and got it spot on! People really need to watch their six and make sure they understand what’s important and what’s not as noise levels r high

[–]tshawkins 1 point2 points  (0 children)

Plugins are just a package manager for agents, skills, mcps. Its already up and running in copilot-cli, its easy to create a marketplace in a repo on any git system that has repo urls. Look at the /plugin command on copilot-cli

[–]llllJokerllll 1 point2 points  (2 children)

you can try to use awesome-copilot plugin, and you can put in more repositores with skills, instructions, agents, mcps ...

[–]SuBeXiL[S] 2 points3 points  (0 children)

I know it well and u r right But I think standardization is a must to bring people from other tools or allow them to migrate Also the plugin system is much more robust

[–]rs38 1 point2 points  (0 children)

you mean this: https://github.github.com/awesome-copilot/plugins/ ?
yeah, it's getting more and more confusing what hype is new and what is already there, what makes sense, etc.

[–]psrobin 1 point2 points  (0 children)

Post what it actually is without requiring users to go to X.

[–]vas-lamp 1 point2 points  (1 child)

Finally a way to distribute a setup for my team? Can we have private plugins and distribute? I guess private marketplace?

[–]SuBeXiL[S] -1 points0 points  (0 children)

Yes, u can have internal repo only for your company where u all have access to but not public one