brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
tooluniverse-publish-toolHelp the user publish one tool from their shared computer to ToolUniverse so other scientists' AI assistants can find and run it, choosing whether only they, specific colleagues, or everyone can use it. Prepares and tests the tool for them; the user makes the final Publish click. Use when the user says "publish my tool", "put my model in Discover", "let any…
Independent GitHub snapshot · Automated classification · Original documentation governs
Publishing puts one tool from a computer the user already shares into ToolUniverse, with a page in Discover if they make it public. People can run that one tool; they cannot see the computer's other tools or anything else on it.
The person you are helping is usually a scientist, not a programmer. You do the preparation; the final choice of who can use it, and the Publish click, are the user's on the website. Never ask for passwords, keys or tokens in the chat.
Publishing needs the tool to be running on a computer connected to ToolUniverse.
list_remote_tools), call it and look for the user's computer ("your computer ...") and the tool.If it is not shared yet, do that first with the skill tooluniverse-share-computer, then come back.
Ask in plain words and explain the choice:
To give a few colleagues every tool on that computer instead of one tool, publishing is not needed: use a share code (see tooluniverse-share-computer, step 7).
If you have the prepare_tool_publication tool (the hosted ToolUniverse connection), do the preparation yourself:
list_remote_tools for its input schema).prepare_tool_publication with computer (its name as list_remote_tools shows it), tool, name, description, keywords and test_arguments. It creates (or reuses) the private draft and runs a real test call.test_passed is false, read test_error, fix the cause on the computer (the tool itself, or the computer went offline) and call it again.review_link and say exactly this: open it, choose who can use it (Choose who can use it: Only me, Specific people with their account emails, or Public), then click Publish. You cannot publish for them: that choice is theirs, on purpose.Without that tool, walk them through the website one or two steps at a time:
If a test fails, fix the cause on the computer, then test again. Do not ask the user to publish a tool that has not passed.
list_remote_tools, search for it by name and run it once with the same example.list_remote_tools / run_remote_tool if you can.Explain that the tool only works while the computer is on and sharing. Offer to keep it running with a background service (tooluniverse-share-computer, step 6).