Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.simplehost.dev/llms.txt

Use this file to discover all available pages before exploring further.

​
Install in 5 seconds

npx skills add sk-code-01/simplehost-skill -g
That’s it. Your agent can now publish to the web.

​
What happens after install

Your AI agent gains a new ability: turning any files into a live website. Just tell it what you want:
You sayAgent does
”Publish this project”Scans files, uploads to SimpleHost, returns a live URL
”Deploy my dist folder”Same — finds dist/, publishes it
”Give me a URL for this”Same — detects the right directory, publishes
”Update my site”Compares hashes, uploads only changed files
”Make this live”Same — publishes whatever you’re working on
The agent handles everything: file scanning, hashing, uploading, authentication, error handling, and retries. It can also act like a SimpleHost product assistant, not just a deploy button. That means the agent can answer SimpleHost questions, explain errors, and guide users through the dashboard in plain language.

​
Safe publishing for non-technical users

If the agent finds a private key or secret in website files during publish, it should not just fail with a technical error and it should not publish the site as-is. Instead, the expected experience is:
  1. The agent explains the issue in simple language
  2. The agent reassures the user that original local files will stay untouched
  3. The agent asks permission to secure it before publishing
  4. If the user agrees and secure browser-side proxying is available on the deployment, the agent secures the published version and retries
  5. If secure browser-side proxying is not available, the agent should explain that SimpleHost refused the publish rather than expose the secret publicly
  6. If the user refuses, the agent does not publish
The tone should be calm, friendly, and clear because many users will not be technical. Example:
“I found a private key in your website files. If I publish it like this, other people could see it and misuse it. I can secure it for you before publishing, and I will not change your original project files. Would you like me to do that?”
If secure browser-side secret handling is unavailable on the deployment, the agent should say so clearly instead of pretending the site can still be published safely.

​
Docs-aware support

The skill is designed to use the SimpleHost docs as its knowledge source for product questions. So if a user asks things like:
  • “How do anonymous sites work?”
  • “Where do I manage secrets?”
  • “Why did my publish fail?”
  • “What does this plan include?”
the agent should answer in simple language first, then point to the relevant docs page if needed.

​
One install, every project

The skill installs globally. Every project, every conversation, every agent session — it just works. Your agent always has the ability to publish. 
Session 1: "Build a landing page" → agent builds + publishes
Session 2: "Create a dashboard" → agent builds + publishes
Session 3: "Update the landing page" → agent updates only changed files

​
Supported agents

AgentInstall method
Claude Codenpx skills add sk-code-01/simplehost-skill -g
Cursornpx skills add sk-code-01/simplehost-skill -g -a cursor
Windsurfnpx skills add sk-code-01/simplehost-skill -g -a windsurf
All agentsnpx skills add sk-code-01/simplehost-skill -g --all
Follows the open Agent Skills standard.

​
No account? No problem

Your agent publishes instantly without any setup. No API key, no signup — just a live URL in seconds. The site expires in 24 hours. After publishing, the agent will offer to make it permanent for free (takes 30 seconds).

​
What’s next

Installation details

Manual install, environment setup, and troubleshooting.

Usage examples

Real examples of what agents can publish.