Turn your skill into an app anyone can use

Your skill only works for people who run an AI coding tool. Make it a hosted app at yourapp.skillsafe.ai and it works for everyone with a browser — on a phone, a tablet, a locked-down work laptop. No servers, no auth code, no billing integration — and no API keys: the platform runs the models, so you ship an AI app without an account at any provider. Set your price and keep 100% of what you earn — the platform never takes a cut of your markup. New here? See the step-by-step walkthrough.

From skill to live app in three steps

1

Save your skill

Your skill is the app's brain: its SKILL.md is pinned as the app's system prompt at deploy time. If it's already on SkillSafe, you're done with this step.

2

Ask your agent to deploy it

Paste this into Claude Code, Cursor, or any agent with web access — it drives the SkillSafe platform API end to end:

Read https://deploy.skillsafe.ai/llms.txt, then deploy my skill @you/your-skill as a hosted app.

Prefer to do it by hand? The same guide documents every REST call.

3

Pass the scan, go live

Your app serves at https://your-slug.skillsafe.ai/ immediately. Publish it to the public directory once the skill and frontend pass a clean security scan — or keep it unlisted and just share the link.

Everything around your skill, already built

Runs anywhere, for anyone

Hosted on the edge with streaming output. Users run it in any browser on any device — no install, no API key. Guests can use it without creating an account.

User accounts, solved

Guest sessions, one-click SkillSafe sign-in, and per-app consent for profile or email access. Every token is scoped to your app alone — you write zero auth code.

Billing in dollars

Runs are metered at actual token usage, billed in US dollars exact to the cent, with the unused hold refunded after every run. Set your own markup and keep all of it, or sponsor free usage with daily caps — no Stripe integration, and every run's earnings land in your dashboard.

A backend without building one

Declared record collections with per-collection ACLs and a safe query DSL, vector similarity search, per-user key-value storage, and file uploads — including image inputs for vision runs.

AI models included

Pick Claude, GPT, or Workers AI models per app. Your users never bring a key, and per-job caps bound the spend of every run regardless of the model.

Scanned, trusted, discoverable

Every public app is built from a security-scanned skill and must pass a clean scan — skill and frontend — before listing. Listed apps get a directory entry and an SEO-indexed detail page for free.

Runs on a schedule

Put an app on a timer with one API call — a cron expression in your timezone, or a plain interval. Each run submits the app's prompt and can email the output or POST it to a webhook. No server, no CI runner, no secrets in a YAML file.

One goal, several skills

An app is built for a goal, and a goal usually draws on more than one skill. Compose several owned skills into one app and each is framed as a step toward the goal — not a menu of alternatives your agent has to choose between.

No skill yet? Start from a Claude artifact

Built something in Claude, v0, or ChatGPT that's about to be forgotten in a chat thread? Paste it into the app builder chat — HTML artifacts keep their original look and behavior (games and canvas pieces included): the artifact serves as the app's own frontend at your subdomain, with its AI calls wired to the platform's metered models. Hosted, scanned, and earning — from a paste.

Working from an agent instead? POST /v1/import/artifact takes the artifact source and returns a ready-to-publish draft spec — no account needed for the preview. See the agent guide.

Fair by design: users see a cost estimate before every run, are only charged for what a run actually consumed, and failed runs are refunded automatically. New accounts start with free usage credit (refreshed by a small daily grant), so your app always has an audience able to try it.

Frequently asked questions

How to turn a Claude Code skill into a web app?

Save the skill on SkillSafe, then deploy it as an app — its SKILL.md becomes the app's system prompt and the app goes live at https://your-slug.skillsafe.ai/. The fastest path is pasting one prompt into Claude Code or any agent with web access; it drives the SkillSafe platform API end to end, and the same guide documents every REST call if you prefer to do it by hand. Publishing to the public directory additionally requires the skill and frontend to pass a clean security scan.

How to share an AI agent with someone who doesn't code?

Host it as a SkillSafe app and send them the URL. Apps run in any browser on any device — phone, tablet, locked-down work laptop — with no install, no API key, and no CLI setup, and guests can use them without creating an account. Because every public app is built from a security-scanned skill, the person you share with can check its scan status before running it.

How to charge users for an AI app without Stripe?

SkillSafe apps meter every run in US dollars, exact to the cent, at actual model-token usage and the platform handles payment collection. As the owner you set a markup of up to 100% of each run's compute cost and keep 100% of it — nothing is deducted from your side. Earnings and per-run metering appear in your dashboard, and there is no payment integration to build.

How to host an AI app without a server or backend?

SkillSafe apps are hosted on edge infrastructure at your-slug.skillsafe.ai — there is nothing to deploy or operate. The backend pieces are built in: declared record collections with per-collection ACLs and a safe query DSL, vector similarity search, per-user key-value storage, file uploads, and access to Claude, GPT, and Workers AI models without your users bringing keys.

How to add user accounts and billing to an AI app?

On SkillSafe both are platform features rather than code you write. Users arrive as guests with no sign-up, or sign in with their SkillSafe account in one click, with per-app consent for profile or email access and tokens scoped to your app alone. Billing is metered in US dollars per run: users see a cost estimate before every run, unused holds are refunded, and failed runs are refunded automatically.

How to run a skill on a schedule?

A skill runs inside your agent, so a schedule needs somewhere to run without you. Deploy the skill as an app, then schedule the app: one API call with a cron expression in your timezone (or a plain interval from 15 minutes to 7 days) runs the app's prompt on a timer and can email the output or POST it to a webhook. No server to maintain and no CI runner to configure — see the deploy guide.

Start with a skill you already have

Pick any skill from your dashboard — your agent handles the rest. Wondering about running costs? Read the full cost breakdown.