Give Muse Code a clear launch finish line.
Use a portable skill and public audit results to keep a launch task grounded in evidence.
Start with a public URL. No account required for the first audit.
Audit https://example.com. Return the finding, matching resource, smallest implementation, and the evidence needed to verify it.
A finding. A useful resource. A finish line.
Separate launch, technical, and agent-readiness findings. Matching skills and guides. The next three actions, with evidence and a completion check.
Fix one gap, verify it, then learn from a real user.
Give Muse Code the context.
Download the skills packet and place the selected skill in the directory supported by your Muse Code release. For releases with remote MCP support, configure the endpoint below using Muse’s current documentation.
https://launchbuddy.com/api/mcpMuse plugin and marketplace support varies by release. A downloadable skill is available here; a marketplace listing is not claimed.
Try one useful request.
Audit https://example.com. Return the finding, matching resource, smallest implementation, and the evidence needed to verify it.Start with one repository task and retain the audit JSON so the same finding can be checked after deployment.
Audit the public URL
Use audit_my_launch and retain the returned JSON and native fix packs.
Find the right resource
Use search_launch_resources for a relevant skill, guide, or Swarm launch channel.
Check the result
Verify against the original finding after the authorized change is live. Missing evidence stays unknown.