oly-apps
Serves local HTML, SPA, or proxied services via the oly daemon for interactive user feedback.
Install
mkdir -p .claude/skills/oly-apps && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10441" && unzip -o skill.zip -d .claude/skills/oly-apps && rm skill.zipInstalls to .claude/skills/oly-apps
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when building a web app/api to present rich output or interactive experiences to users.Key capabilities
- →Serve web apps from wwwroot
- →Discover apps automatically
- →Configure apps via manifest
- →Share static assets
How it works
It serves web content from specific folders, supporting simple HTML or complex SPAs via a manifest file.
Inputs & outputs
When to use oly-apps
- →Creating custom dashboards for AI tool output
- →Serving interactive UI prototypes
- →Sharing static assets across local services
About this skill
Overview
Publish rich output as a web app served by the oly daemon. Each app lives in its own folder under <OLY-ROOT>/wwwroot/apps/ and is reachable at:
http://127.0.0.1:<OLY-PORT>/apps/<app-name>/
Run oly daemon status to discover <OLY-PORT> and <OLY-ROOT>.
Quick start
Simple HTML app
Drop an index.html (plus any assets) into a new folder:
<OLY-ROOT>/wwwroot/apps/<app-name>/index.html
No manifest needed — oly discovers index.html automatically.
SPA or proxied service
Create oly.app.json in the app folder:
{
"title": "My App",
"entry": "index.html",
"redirect_files": ["../shared-assets"]
}
Set the base href to ./ (or /apps/<app-name>/) so relative asset paths resolve correctly when served from the discovered route.
Manifest schema (oly.app.json)
| Field | Type | Description |
|---|---|---|
title | string? | Display name. |
description | string? | Short description. |
icon_href | string? | Icon URL or relative path. |
app_type | string? | App type hint. |
redirect_files | string[] | Extra asset directories outside the app folder. Oly checks the app folder first, then each redirect directory in order; 404 if not found. |
entry | string | Required. URL, path, or HTML file to serve as the entry point. |
Rules
- Use relative asset paths or the
/apps/<app-name>/base — absolute paths will break. - One folder per app, one
index.htmlor oneoly.app.jsonper folder. - Use
redirect_filesto share static assets across apps without copying.
When not to use it
- →Serving non-web content
Limitations
- →Requires relative asset paths
- →Requires specific folder structure
How it compares
This provides a standardized, daemon-managed serving mechanism compared to manual web server configuration.
Compared to similar skills
oly-apps side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| oly-apps (this skill) | 0 | 4mo | No flags | Beginner |
| pwa-development | 9 | 4mo | Caution | Intermediate |
| add-cdn-bundle | 1 | 5mo | Review | Intermediate |
| vite-patterns | 0 | 2mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by slaveOftime
View all by slaveOftime →You might also like
pwa-development
alinaqi
Progressive Web Apps - service workers, caching strategies, offline, Workbox
add-cdn-bundle
getsentry
Create a new CDN bundle for the browser package with specified features
vite-patterns
Fmarzochi
Vite build tool patterns including config, plugins, HMR, env variables, proxy setup, SSR, library mode, dependency pre-bundling, and build optimization. Activate when working with vite.config.ts, Vite plugins, or Vite-based projects.
progressive-centralization-starter
Swader
Bootstrap Bun-based single-file frontends with Filebase/IPFS, ENS, and Arweave/ArNS deploy tooling. Use when creating a progressive centralization starter project, setting up .env-driven deploys, or when the user asks to "just do it" for IPFS/ENS/Arweave hosting.
drn-buildwww-vite
duranserkan
DRN buildwww Vite build system - multi-build configuration, TypeScript aliases, wwwroot output, appPreload/appPostload, and Vite manifest discovery. Keywords: drn, buildwww, vite, typescript, bundling, asset-compilation, npm, javascript, css, scss, build-pipeline, entry-points, manifest
zustand
lobehub
Zustand state management guide. Use when working with store code (src/store/**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.