API reference

Skills

Teach the agent how you do one kind of task, in your own words. Skills work with every AI choice.

A skill is a folder with a file named SKILL.md: instructions for one kind of task. The agent sees the list of your skills and reads one when a task calls for it. Skills work the same with the Graspable agent, Claude Code and Codex.

Use a skill for things you would otherwise repeat in every request: how your studio lights a scene, your naming rules, the steps to export for a client.

Find a skill

Browse the library on the website. In the current desktop release, download a skill folder from its original source and add it in Settings.

The in-app library, project-specific adding and removing, and recorded skill usage require Graspable 0.19.0 or later. Update your installed app to use them.

In that update, open Skills from the Projects page, the project's Skills tab, or Settings → Plugins and skills.

Search by a task, author or tool, and filter by XR & AR, 3D, animation, AI glasses, characters, Gaussian splats, games, film, performance or accessibility. Open a skill to read its original instructions, source, license, requirements and reviewed version.

Choose Add skill in the app. Graspable checks the downloaded files against its reviewed catalog and adds any listed skill dependencies. It never overwrites a personal skill with the same name. Adding a skill does not execute scripts, install runtime packages or buy services. Existing skills stay usable offline; reading or adding a catalog entry needs a connection. Catalog versions come with app updates.

The skills work with all supported agents on this computer. Switch them on or off for a project in its Skills tab. Native tools, hardware, accounts and runtime software still have their own requirements. The catalog is not a guarantee of device compatibility or generated-project quality. Entries marked Research reference depend on a larger upstream setup and cannot be added as incomplete packages.

Projects using a skill

A skill's page shows up to five public projects ordered by views or likes. Show more projects using this skill opens the public projects directory with that skill selected. You can change the skill filter there.

Graspable records a catalog skill after an agent successfully reads its unchanged instructions through use_skill. Having a skill installed or switched on does not count as using it. The next completed publish includes those recorded skill IDs. Existing projects are not assigned skills retrospectively, and private, removed or unpublished projects are excluded. An empty list means no public projects have recorded that skill yet. This is contribution history, not a certification of the result.

Write one

---
name: scene-lighting
description: How we light scenes. Use for any new scene or when lighting looks flat.
---

Use one warm key light at intensity 2.4 from the upper left, and a cool rim light.
Never use ambient light above 0.3. Colours are in palette.md.
  • name: lowercase letters, digits and dashes.
  • description: one or two sentences that say what the skill covers and when to use it. The agent decides from this line alone, so be specific.
  • The rest is the instructions. Other files in the folder can be referred to by name; the agent reads them when the instructions point to them.

Add it

On a library page, follow Original skill to its source. Save the skill folder, including SKILL.md, its license and any companion files it references. For a standalone skill, save Read as Markdown as SKILL.md inside a folder. Read its requirements before adding it; some skills need other skills or software too.

Open Settings → Plugins and connectors → Skills, paste the folder's path and choose Add skill. Graspable copies the folder into ~/.graspable/skills.

From a terminal:

grasp skills add ./scene-lighting
grasp skills

A plugin can bring skills too. When your own skill has the same name as a plugin's, yours is used.

Skills that come with a template

A template can come with skills of its own. The Unreal Engine template does: Graspable's skills for naming and folders, for keeping a scene fast on a headset and for making it look like professional work, and two public collections for Unreal's own systems (C++, Blueprints, materials, input, UI, packaging and more). Every web template comes with a security review skill (the public OWASP skill, MIT licence): ask the agent whether your app is safe to publish, and it reviews the project against the OWASP Top 10 and the ASVS, from what the app does with addresses and files to what it sends to connectors. They are used in every project made from that template, with nothing to set up.

Settings → Plugins and connectors → Skills lists them under the template's name, each with a switch. Switch one off to leave it out of your projects. To replace one, add a skill of your own with the same name: yours is used instead.

Skills in one project

Open Skills beside the conversation, then Add skills. Search the directory without leaving your scene, choose a skill, check its requirements and choose Add to project. The full instructions and source are one click away. The full directory keeps your project selected and has a Back to project link.

Skills added here, including their listed dependencies, belong only to this project. Remove leaves a skill out of its next request without changing another project. To restore it, choose Add skills, then Add under Available on this computer. Removing a skill does not remove models or other work it helped create.

Your shared skills, plugin skills and template skills also appear here. A template skill switched off in Settings stays unavailable until you switch it on there. Settings remains the place to install or remove shared skills for all projects.

Work with local Blender

If Blender is already installed, add Blender Core, then the skills for the work: materials, animation, lighting, exporting or asset checks. Ask the agent to use your local Blender, keep an editable .blend source and export a .glb for the experience. You can keep editing the source in Blender and ask the agent to regenerate the exported asset afterward.

The agent uses Blender's local scripting interface through its normal command approvals. A skill does not install Blender or require a paid rendering service. Procedural materials and constraints may need baking before export; check the exported scene in Graspable, as a Blender render alone does not prove how it looks or performs in the browser or a headset.

How the agent uses them

The names and descriptions of your skills are part of every run's prompt. When a task matches one, the agent reads the skill and follows it. You can see this in the run as a use_skill step, and the list itself under Context.

Skills that already follow this layout for other tools, a folder with a SKILL.md that has name and description, can be added as they are.