/create-skill command turns a plain-language description into a saved slash command. Digcrate does a real dry run first — using live tools, returning real results — so you can see exactly what the command will do before saving it.
Workflow
Run /create-skill with a description
Type Be specific. The more detail you give, the better the dry run results — and the more accurate the saved command will be.
/create-skill followed by a description of what you want the command to do.Digcrate runs a dry run immediately
Digcrate executes the task right now using its available tools. No questions, no clarifications — it uses your description and its best judgment.For a website task, it navigates to the page and scrapes results. For a search task, it queries the relevant data sources. For research, it runs the same multi-step agent loop as any other query.
Results appear as interactive components
Results are displayed using OpenUI components — the same components used everywhere in Digcrate:
- Event listings →
ConcertListwith venue, date, and ticket links - Records and releases →
TrackListwith links to source pages - Artist research →
ArtistCard - Playlists →
SpotifyPlaylist
Digcrate suggests a command name
After the dry run, Digcrate suggests a command name based on your description — for example,
/rave-events. Command names are lowercase with hyphens.You can accept the suggestion or ask for a different name before saving.Worked example
Here’s what the full flow looks like for a real skill: Input:ConcertList with artist names, dates, venues, and ticket links.
Suggested command name: /rave-events
After confirming: The skill is saved. From now on, typing /rave-events in any session runs the same scrape and returns fresh results every time.
What gets saved
When you confirm a skill, Digcrate stores:| Field | What it contains |
|---|---|
| Command name | The slash command, e.g. rave-events |
| Name | Human-readable label, e.g. “The Rave Events” |
| Description | One sentence describing what the skill does |
| Prompt template | The full prompt that produced the dry run results, including instructions for OpenUI rendering and clickable links |
| Tool hints | The names of the tools that worked during the dry run |
| Source URL | The URL of any website that was involved |
Editing and deleting skills
Use/skills to manage your saved commands:
- To edit a skill’s name or description, select it from the list
- To delete a skill, select it and choose Delete
- To temporarily stop a skill from appearing in autocomplete, disable it without deleting
Skills run the same agent loop as every other Digcrate command. They have access to all 20+ data sources — Discogs, MusicBrainz, Last.fm, Ticketmaster, Bandcamp, WhoSampled, Wikipedia, Genius, and more. If you can describe it, you can skill it.