Publish a spec
publish_specPublishes a spec on Spekkr under the signed-in person's username, as username/name, or publishes a new version of one of theirs. Send the text of spekkr.json and every file it lists. A small text file goes in files with its content. Any other file (an image, a PDF, a video, a long document) goes in files with its size in bytes and no content: the answer then gives an address to upload those files to with HTTP PUT, and once they are uploaded you call publish_spec again with the same arguments. Nothing is listed until a call answers with published. A listed spec names the member who published it. A published version never changes: to update a spec, raise the version, add a changelog entry and list every file again. A file that has not changed goes in files with keep set to true and nothing else, and Spekkr takes it from the version listed now, so a screenshot need not be uploaded again. In this version a published spec is free. If anything has to change first, the answer names every problem. This tool needs sign-in. Ask the person before you call it: publishing makes the files public.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"manifest": "<manifest>",
"files": "<files>"
},
"name": "publish_spec"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| files | Yes | Every file the manifest lists, every file inside a folder it lists, and every screenshot under demo.screenshots. Leave out spekkr.json, BUILD.md and spekkr.inputs.json. Each file has a path and one of content, bytes or keep. | |
| manifest | Yes | The whole text of the spec's spekkr.json. Its id is username/name, with the signed-in person's username, and its author.id is that username. |