Skill per folder/repo in addition to existing global skill viewer

[manyponds]

Some skills might only apply to a specific repo and you want to keep it to that way (i.e. you don't want your YouTube research skill clogging up context on unrelated App work). Idk if there's an easy way to do this but would be nice to see which projects/folders skills are applied to, and the ability to toggle them on/off.

[Shpigford]

so we already show if a skill is project/folder-exclusive. however, when a skill is duplicated across multiple projects, it would potentially be nice to only show that skill once in the list and then provide a UI element to easily toggle on/off.

need to think through potential implications of that. 🤔

[manyponds]

I think the industry's current IA of agentic tool management is broken:

Claude

• Skill A
• Skill B

Codex

• Skill B
• SKill C

Chops has the opportunity to fix this.

You switch to Codex and expect Skill A but it's not there

Since LLMs are in a leapfrog race we're always switching models so I think skills should be model agnostic and more related to area

Global

• Skill A
• Skill B
  ...

Project/Folder 1

• Specific Skill A
• Global Skill B (toggled off)
  ...

This applies to tools and MCPs too. Thoughts? Could even have a LLM toggle, but the current IA being flipped is working against the expected mental model that "I install a skill once (from any entry point), all my LLMs have access."

IDE's like Cursor solve this, but with IDE's changing so fast I don't wanna be locked in, so Chops allows you to work anywhere/anyway you want with your agentic toolset layer intact.

I can mock something up and put in a PR if you'd like

---

Also the way MCP would work here is giving the model context on what skills/tools it has access too (across models s as they store in different locations). I've trying to manage this with symlinks but it's messy as I want cloud sync across machines.

So if you were to tell it copy the toolset (skills, mcp, tools) from Project 1 into this project.

Or disable Global Skills B-E on this project.

Or with categories like Skills relating to marketing disable them here

I find LLM often misses a bunch of the skills when I do this and I end up with skill spaghetti

The MCP gives context to this shared, model agnostic toolset layer.

[slaFFik]

@Shpigford Currently, the same skills installed in different folders are displayed only once (and it looks like the last one in alphabetical order wins).

So even though I have laravel/boost installed in 2 folders (starting with letter l and letter s in the Projects/ folder), I see it being mentioned only once (as located in project s).

There is also an edge cases when skills are different versions, like the skill provided by laravel/boost v1 and v2.