Share your toolkit

Sharing a toolkit saves other people the work you already did. Send a link to a teammate joining your project and they launch with your exact tools; list it in Community and anyone building the same kind of thing can start from it.

You share from your computer with csc, or ask your coding agent to do it for you. What you share is a copy of the toolkit as it is when you share it. Your later edits stay private until you share an update.

What your toolkit needs before you share it

Every repository your toolkit picks tools from has to be public on GitHub, and Code Config has to have read it. Tools from your private tools repository can go too: set your public tools repository with csc repo set --role public --url <address> --json, and sharing copies them there first. If a tool’s file holds a key, nothing is copied and you are told which file and which lines. Your tools repositories explains what sharing does to your files.

MCP servers go with the share, with the names of the keys they need but never the keys themselves. Share only tools you are allowed to share; the Terms of service apply.

Share in Community

1. Find the toolkit’s id with csc toolkit get --json.

2. Pick what the toolkit is for: one or more subcategories, all from one category of Community, such as code-review and testing-debugging. csc toolkit share --help lists every subcategory.

3. Run the share, with --subcategory once for each subcategory:

   csc toolkit share --toolkit <toolkit-id> --subcategory code-review --subcategory testing-debugging

4. Copy the link it prints.

In Community, the listing is a copy of the toolkit as it is when you share it, and sharing again updates it. A listing can be removed after someone reports it.

Share by link only

To hand someone a link without listing the toolkit in Community, run:

csc toolkit share --toolkit <toolkit-id> --link-only

Anyone with the link can open the toolkit, and it does not appear in Community. A toolkit already listed in Community stays listed. Whoever opens it chooses whether to follow your updates or keep a copy as it is today.

What the shared page shows

The page shows the toolkit’s name, its subcategories, you as the publisher, how many tools it has and which repositories they come from, and which coding apps it works with. It also shows which of its MCP servers need a key and how many people use it, never a key’s value.

Check it worked

Open the link in a signed-out browser and check the name, the tools, and the Use this toolkit button. A toolkit shared by link says it is not listed in Community.

Send people to Use a shared toolkit. Opening the link does not change anything on their computer.

Share an update after you edit

Edit your toolkit, then run the same share command again. A toolkit already in Community keeps its subcategories when you leave out --subcategory, and the link stays the same.

People who follow your updates get the new version the next time their computer syncs. A tool they changed stays as they left it.

Stop sharing

Run csc toolkit share --toolkit <toolkit> --stop, or in Toolkits open the toolkit’s menu, choose Stop sharing, and confirm. The link stops opening and the toolkit leaves Community. Toolkits other people already saved are not deleted, and they show Community source withdrawn.

Deleting a toolkit does not stop its share. To stop the share of a toolkit you already deleted, give its link: csc toolkit share --toolkit <link> --stop.

Next

Use a shared toolkit explains what the person who opens your link sees.