Skills and apps in the Catalog
Two of the Catalog's sections lead to things a Builder takes into Studio: Skills, the instructions an agent follows for one kind of task, and Apps, the app templates that run on this installation. Each reads the same list Studio does, so what you see here is what a Builder sees there.
Who can use it: the Member role reads both sections. Attach to agent, Open in Studio, Fork and Deploy need the Builder role.
Skills
The page describes skills as instructions an agent follows for one kind of task. Katonic's own skills are ready for every organisation with nothing to install: there is no install step, and attaching one adds it to an agent's draft.
- Find a skill
In the Catalog, select Skills, or Browse skills on Featured. The list is the one Studio's Skills library shows, with the same names, descriptions, versions and labels.
- Open it
Select a skill. Its page is the page Studio shows for it, with its instructions, its versions and where it is used. The open skill is in the page's address, so a link to it opens it.
- Attach it to an agent
Select Attach to agent and pick the agent. A draft takes the skill at once; a published agent gets a draft, which opens in the builder on its Skills step. Open in Studio opens the skill in Studio's Skills library instead.
For a Member, the skill's page says that Builder access is required to open Studio where Attach to agent would be, and Open in Studio is absent.
| Message | What it means |
|---|---|
| The skill did not load | The Catalog could not read it. Nothing is wrong with the skill; select Try again |
| Skill not found | No Katonic skill has the name the link carries. It may have been renamed, or the link is stale; Browse all skills returns to the list |
How skills work, from writing one to what attaching freezes, is on Skills and Attach a skill to an agent.
Apps
The page lists app templates that work here, with a count, a search box and a Category list. Each card carries the one action that fits it.
- Fork is on a source template, whose files you edit. It copies the files into a new private dataset.
- Deploy is on a packaged app that runs as it is. It opens New app in App Studio on that template; nothing is created in the Catalog.
- Fork a template
Select Fork. The dialog, headed Fork template, asks whether to fork the template, says its files are copied into a new private dataset you can edit and that you choose what to do with them once the copy is done. Nothing is created until you select Fork into a workspace; Cancel leaves.
- Wait for the copy
The dialog shows the copy in progress. When it finishes, it says the template is copied and names your private dataset, which is in Studio's Storage.
- Choose what to do with the files
Open in a workspace opens the workspace setup with the dataset attached; inside the workspace the files are under the datasets/ folder. Deploy this folder deploys the files as they are from App Studio. If you close the dialog instead, the dataset stays, and you can deploy it later from App Studio with New app, then Deploy this folder.
| Message | What it means |
|---|---|
| Copying "failed, and the unfinished dataset was removed" | Nothing is left behind; try again |
| Copying failed and the unfinished dataset "could not be removed" | Select Delete dataset in the dialog, or delete it from Storage |
| The copy "is taking longer than expected" | The dataset is still being prepared in Storage. Try again to keep waiting, or delete it |
| Couldn't open this template | Preparing the template failed; try again |