Your first Skill
Author agent-readable instructions for Harbor workflows without fake CLI commands.
Current surface
The public hrbr CLI does not expose a dedicated Skill-management command family. Author Skill markdown in your repo or workspace docs, validate the referenced tools with hrbr inspect, and publish/share through the dashboard or repository process used by your team.
A Skill is markdown that teaches an LLM when to use Harbor and how to call the right tools. Treat the CLI as the discovery/runtime checker, not as a skill package manager.
Create the markdown
---
name: triage-sentry-issue
description: Use when the user names a Sentry issue and wants a Linear ticket created with context.
---
# Triage a Sentry issue
1. Inspect source readiness with Harbor.
2. Search for the Sentry issue-read tool and Linear issue-create tool.
3. Execute the smallest tool calls needed.
4. Return the Linear issue URL and trace id.Verify the tools
hrbr inspect 'return await hrbr.sources.list()'
hrbr inspect 'return await hrbr.tools.search({ query: "sentry get issue", limit: 3 })'
hrbr inspect 'return await hrbr.tools.search({ query: "linear create issue", limit: 3 })'Test the workflow
hrbr exec -f ./triage-smoke.tsKeep the exec file small and return the IDs, URLs, and trace evidence the Skill expects.
Share it
Publish the markdown through the dashboard or the repo/package that owns your team's agent skills. If the Skill references Harbor, include the exact inspect queries and runtime namespace examples that passed locally.