Publish a tool someone can trust.

Turn a useful PlayWeld extension into a clear listing, a versioned package, and a maintainable release.

1

Start with a bounded tool

Choose an editor extension, platform plugin, skill, or agent role. Explain its inputs, output, permissions, and supported versions. Start from the greeting worker when learning the protocol.

Continue
2

Check the package contract

Use the correct root manifest and a versioned archive. Review capabilities and dependencies; a valid archive alone does not demonstrate desktop runtime compatibility.

Continue
3

Prepare an honest listing

Create an account, verify your email, and write an original summary and installation guide. Include a license, source link, compatibility range, and the checks you actually ran.

Continue
4

Upload and review

Upload a release through the publisher workspace. The site inspects package metadata and archive paths. Submit for review and respond to any packaging or content corrections.

Continue
5

Maintain the release

Use a new version for changed package bytes. Describe changes and upgrade steps, keep requirements current, and use the creator workspace to review feedback and downloads.

Continue

Try the worker before publishing

Extract the Greeting Starter archive, open a terminal in that directory, and run the command below. Paste each JSON request as a separate line. Initialization announces the tool, the call returns a greeting, and shutdown ends the exercise.

node index.cjs
{"jsonrpc":"2.0","id":1,"method":"plugin/initialize","params":{"protocolVersion":1}}
{"jsonrpc":"2.0","id":2,"method":"plugin/tool/call","params":{"toolId":"playweld.greeting/greet","input":{"name":"Builder"},"context":{"taskId":null,"agentRole":null,"accessMode":"restricted"}}}
{"jsonrpc":"2.0","id":3,"method":"plugin/shutdown","params":{}}

Compare the response with your intended output and test invalid input too. This standalone exercise does not establish desktop sandbox availability. Keep packaging checks, worker behavior, and desktop acceptance as separate evidence.

A useful release checklist

  • State supported PlayWeld and engine versions.
  • Explain filesystem, network, and model access.
  • Include source, license, and reproducible checks.
  • Describe installation, rollback, and any limitations.
  • Keep screenshots and examples free of private project data.

100%

Use left and right arrow keys to browse. Press Escape to close.