Showing results visually
A Cmdop Skill produces text, so when a result needs to be seen it should build a file and hand it to something that displays files. Three shipped paths do that: publish a finished static build to a public URL, leave the artifact on the machine, or send it to a chat. A Skill never hosts a UI itself.
A Skill produces instructions and text. When the result really needs to be seen — a report, a chart, a rendered page — the Skill should build a file and hand it to a surface that displays files. Three shipped paths cover it.
Publish a finished page
The most direct option: have the Skill produce a static build and publish it to a public URL.
cmdop publish ./distpublish takes a finished build — one generated HTML file or a completed
output directory. It does not run a build for you or upload source. It returns
the public URL and a publication ID; pass that ID on a later publish to update
the same URL instead of minting a new one.
Anything you publish is reachable by anyone with the link, so keep secrets out of it entirely. See Transfer files.
Leave the artifact on the machine
Write the file where you can open it: the Skill generates it into the project, and you read it through the machine. If the machine is mounted locally, it opens in your own tools with no transfer at all — see Mount a machine.
Send it to a chat
For results that should reach a person rather than a screen you are already looking at, a messenger bot delivers into Telegram, Slack, or Discord. Set one up under Server → Bots in the web console.
Skills do not host a UI
A Skill is not a place to run a web server. It has no long-lived process, no port of its own, and no runtime that keeps a service alive between requests — executable Skills do not run at all yet, and instruction Skills produce output rather than serve it. See Runtime status.
If you need a service running on the machine reachable from elsewhere, that is a port-exposure question, not a Skill question — see Run commands on a machine.
Related
Common questions
Can a Cmdop Skill show a dashboard?
A Skill can generate a file or static build that you view elsewhere. It does not host a dashboard itself.
How should a Skill publish a visual result?
Have the Skill produce a finished static build and publish it with
cmdop publish ./dist, or leave the artifact on the machine for local review.
Keep secrets out of anything published to a public URL.
Can a Skill run a web server?
No. A Skill is not a long-lived service and has no port of its own. If you need a service reachable from elsewhere, treat that as a machine and network operation, not as a Skill runtime.
Cmdop