The whole skill is one file
manifest, UI and assets inside
The manifest format
YAML + instructions for the model
Widget version
skill support from requires
A skill from the inside.
What is inside the ZIP
The whole skill is a single .skill file. A plain ZIP: the manifest, the interface HTML and JavaScript, and the media. Only SKILL.md is required.
SKILL.md
YAML front matter: slug, version, triggers, parameters. The body holds imperative instructions for the model.
drawer.html + js
A full-chat drawer: forms, a calendar, buttons. The JS receives drawer, item and params.
card.html + js
The skill card in the feed — an HTML template and its script. Both files are optional.
Not just files — a manifest too
Behaviour is declared, not coded. Assets, trigger phrases and version requirements live inside the bundle itself — next to the code.
All through data attributes
Mark it up and the widget assembles it. Components are declared with data attributes and processed through a MutationObserver — they work even when created dynamically from JS.
Developer questions
A ZIP archive with the whole skill: SKILL.md (the manifest and the instructions for the LLM), card.html and drawer.html with their JS, and an assets folder with media. Only SKILL.md is required.
Build your own skill
The format is open. Ready skills come from the marketplace in one click; your own arrive as a plain ZIP in the .skill format.
Sign-up
Create an account in a minute — no card, free plan forever.
/02Marketplace
A ready skill drops into your project in one click.
/03Your own skill
SKILL.md with triggers plus HTML and JS — pack a ZIP in the format.
/04Upload
The .skill file is uploaded in the admin panel — the assets go to storage on their own.
Tell us your task
Projects by type grow year over year
MVP, redesign, AI and support — cumulative
The studio profile across key axes
Speed, quality, transparency, engineering
Research, design and build overlap
Parallel streams — not a waterfall