Use a custom skill in your workspace

Build a small handoff-note skill, find it in the catalog, and ask an agent to apply it to a note. You only need a text editor.

Choose the workspace

  1. Select the conversation or choose a location for a new conversation.
  2. Open Agents in the sidebar, or find it under More. Select the Skills tab. In the Custom section, check the workspace path and runtime. For an SSH session, create the files on the remote machine at the displayed path.
  3. Use a Plus, Pro, Lab or Enterprise account with valid subscription credentials on that runtime. Official skills follow the active domain's content tiers. Custom agents require Lab or Enterprise.

If the panel asks you to update Core, use a Core and UI version that includes workspace rescanning. A conversation connected through the cloud-process relay currently has no workspace scan in this panel.

Create and load a skill

In the workspace you just checked, create skills/handoff-note/SKILL.md. Save the following text as UTF-8.

---
name: handoff-note
description: Turn a short work note into a handoff for a colleague.
---
Write HANDOFF-NOTE on the first line.
Then give two items, Completed and To confirm, using only the user's facts.
If nothing needs confirmation, write None.

Click Rescan workspace on the Skills tab. Find handoff-note in the custom list, select it, and click Use it in a new chat. Complete the draft with the task below and send it. You can also send this request in an existing conversation in the same workspace.

Call handoff-note to summarize this note. The charts have been exported. The title needs confirmation.

Expand the reply's tool steps. Look for a skill call with name set to handoff-note. The reply should start with HANDOFF-NOTE and place the charts and the title under the corresponding items. A catalog entry confirms discovery. The tool step shows whether the agent actually loaded the instructions for this reply.

If you see call_agent first, expand the tool steps for the agent that received the task. Look there for skill and, after adding a reference file, for the path read by skill_resource.

Include a reference file

To include a checklist, put a rule in skills/handoff-note/references/checklist.md. Add an instruction to the skill body asking the agent to read references/checklist.md with skill_resource before checking the handoff. Save, rescan, and ask the agent to apply the rule in your next request.

skills/
└── handoff-note/
    ├── SKILL.md
    └── references/
        └── checklist.md

For instructions alone, you can use skills/handoff-note.md. A standalone Markdown skill has no packaged resources. Choose one layout per skill name. Existing workspaces can also use .omicos/skills/.

Use a skill someone shared with you

OmicOS reads skill files directly from your workspace. If you received handoff-note.md, copy the file into the workspace's skills/ directory. If you received a handoff-note/ folder, copy the whole folder so its entry is at skills/handoff-note/SKILL.md. Keep the reference files, scripts and other resources inside it. In the Skills tab, click Rescan workspace and select the skill. These steps require no Harness Kit installation or command line.

If the top level contains agent-harness/ and harness-manifest.json, you received the author's development bundle. Ask the author for the skill folder prepared as described below, then copy that folder into your workspace.

Troubleshoot a custom count of zero

What you see What to check
Scan succeeds with zero entries Check the machine and workspace path. Use the plural skills/ directory. A package entry belongs directly at skills/<name>/SKILL.md.
A saved skill is missing Click Rescan workspace and expand the diagnostics. Check file permissions, the closing ---, extra nesting and symbolic links. Use regular files and directories.
Duplicate name Change the frontmatter name and rescan. Packages take precedence over standalone files in the same root. The official catalog takes precedence over the ordinary workspace roots.
Subscription, credentials or device-limit message Follow the panel to sign in, refresh credentials or resolve the device limit, then rescan. A downgrade leaves your files in place.
The cloud asks you to refresh credentials while a local skill still loads If renewal is temporarily unavailable for the same account, Core has a 24-hour grace period by default. The cloud requires current credentials. Reconnect, refresh credentials and rescan. Core applies the new entitlement when it receives a downgrade or device-limit decision.
Official catalog refresh fails Click Rescan workspace. A connected runtime reads local files directly.

Optional Harness Kit workflow for skill authors

If you develop skills with Harness Kit, prepare the folder for your users on your own machine. Choose an existing empty directory as your staging workspace. With a Kit version that supports workspace installation, run the following command using the paths to your bundle and staging workspace. Workspace installation command

ohf install ./my-harness --workspace ./staging-workspace

Share the entire generated staging-workspace/skills/<name>/ folder. The recipient can copy it into their workspace with SKILL.md, harness-manifest.json, scripts and references together. If you reuse the staging workspace and the skill already exists, the installer stops. Add --replace to back up the old version before replacing it. If the scaffold still reports dry_run, verify the real algorithm's dependencies and outputs on the target runtime.

results matching ""

    No results matching ""