
publish
Publish a Harbor task or dataset to the registry. Use when the user wants to upload, publish, or share tasks or datasets/benchmarks on the Harbor registry.
- Installs
- 196
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/harbor-framework/harbor --skill publish- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads publish automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Help the user publish a Harbor task or dataset to the registry. Walk them through each step, checking prerequisites and confirming before running publish commands.
All commands use uvx harbor so the user does not need to install the CLI globally.
Prerequisites
-
Auth: Ensure the user is logged in by running
uvx harbor auth status. If not logged in, prompt them to runuvx harbor auth login. -
Task identifiers: All tasks must have a
[task]section in theirtask.tomlwith a name like<org>/<name>. If missing, run:uvx harbor task update "<path/to/task>" --org "<org>"To update all tasks in a directory:
uvx harbor task update "<path/to/tasks>" --org "<org>" --scan
Publishing a task
uvx harbor publish "<path/to/task>"
Publish multiple tasks or all tasks in a directory:
uvx harbor publish "<path/to/task-a>" "<path/to/task-b>"
uvx harbor publish "<path/to/tasks>"
Publishing a dataset
1. Initialize the dataset manifest (if no dataset.toml exists)
uvx harbor dataset init "<org>/<dataset>" \
--description "<description>" \
--author "Jane Doe <jane@example.com>"
Add --with-metric if the user needs a custom metric script. If omitted, the dataset uses the default metric (average reward across tasks, with missing values treated as 0).
Auto-add behavior: If dataset init is run in a directory that already contains tasks, those tasks are automatically added to the manifest. After init, ask the user if they want to add additional tasks — either from the Harbor registry or from other local folders.
2. Add additional tasks and files (optional)
cd "<path/to/dataset>"
uvx harbor dataset add "<path/to/task-a>" "<path/to/task-b>" # local tasks from elsewhere
uvx harbor dataset add "<path/to/folder>" --scan # all tasks in another folder
uvx harbor dataset add org/task-name # published tasks from registry
uvx harbor dataset add org/dataset-name # all tasks from a published dataset
uvx harbor dataset add metric.py # metric file (same dir as dataset.toml)
uvx harbor dataset remove "<org>/<task-name>" # remove a task
Specific versions: org/task@tag, org/task@revision, or org/task@sha256:<hash>.
3. Sync digests (if tasks/metrics changed since last publish)
uvx harbor sync
uvx harbor sync --upgrade # also upgrade remote tasks to latest
4. Publish the dataset
uvx harbor publish "<path/to/dataset>"
uvx harbor publish automatically refreshes digests of local tasks in the dataset directory.
Publish options (tasks and datasets)
-t / --tag: add tags (repeatable).latestis always included.-c / --concurrency: control upload concurrency.--public: make public (private by default).--no-tasks(datasets only): skip publishing tasks in the dataset directory.
Example:
uvx harbor publish "<path>" -t v1.0 --public
After publishing
- Visibility can be changed later with
uvx harbor task visibility/uvx harbor dataset visibilityor on https://hub.harborframework.com/. - Run a published dataset with:
uvx harbor run -d "<org>/<dataset>@v1.0" -a "<agent>" -m "<model>"
FAQ
What does the publish skill do?
Publish a Harbor task or dataset to the registry. Use when the user wants to upload, publish, or share tasks or datasets/benchmarks on the Harbor registry.
How do I install publish?
Run npx skills add https://github.com/harbor-framework/harbor --skill publish in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/publish/ (personal) or .claude/skills/publish/ (project).
Which AI agents can use publish?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is publish safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains publish?
It is published by harbor-framework in harbor-framework/harbor. It has 196 recorded installs.
More from harbor-framework/harbor
rewardkit
harbor-framework/harbor
Write Harbor task verifiers using Reward Kit. Use when creating or editing a task's tests/ directory, adding grading criteria, setting up LLM/agent judges, or designing verifiers that produce a reward score.
create-task
harbor-framework/harbor
Create a new Harbor task for evaluating agents. Use when the user wants to scaffold, build, or design a new task, benchmark problem, or eval. Guides through instruction writing, environment setup, verifier design (pytest vs Reward Kit vs custom), and solution scripting.
harbor-exec
harbor-framework/harbor
Use when working with Harbor's harbor exec CLI workflow: compiling files, directories, or globs into Harbor tasks; running map jobs; configuring artifacts and existence-only verification; using map-reduce; writing or reviewing ExecConfig YAML/JSON/TOML; or debugging command behavior, config validation, and job outputs.
upload-parity-experiments
harbor-framework/harbor
Create or reuse Hugging Face dataset PRs for harborframework/parity-experiments and upload Harbor parity/oracle result folders efficiently with sparse checkout, raw git pushes, and Git LFS.
Popular data & databases skills
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pgcron, pgmq), vector/semantic search (pgvector), and restoring dumps (pgrestore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-client-api
prisma/skills
Prisma Client API reference covering model queries, filters, operators, and client methods. Use when writing database queries, using CRUD operations, filtering data, or configuring Prisma Client. Triggers on "prisma query", "findMany", "create", "update", "delete", "$transaction".
prisma-database-setup
prisma/skills
Deprecated compatibility name for prisma-orm-setup. Use only when a user or existing integration explicitly invokes prisma-database-setup; otherwise select prisma-orm-setup.
prisma-cli
prisma/skills
Prisma ORM 7 CLI reference for existing Prisma 7 applications or explicitly selected Prisma 7 workflows. Covers prisma init, generate, migrate, db, dev, studio, and mcp. For setup, connection repair, or Prisma 8, use prisma-orm-setup; not the Prisma Platform CLI.
prisma-postgres
prisma/skills
Deprecated compatibility name for prisma-postgres-setup. Use only when a user or existing integration explicitly invokes prisma-postgres; otherwise select prisma-postgres-setup.
prisma-driver-adapter-implementation
prisma/skills
Required reference for Prisma ORM 7 SQL driver adapter work. Use when implementing or modifying adapters, adding database drivers, or touching SqlDriverAdapter, Transaction, savepoint, result mapping, or DriverAdapterError behavior. Covers current transaction lifecycle, optional savepoint hooks, original database-error preservation, and verification.