◈OpenTree DashboardSign in

$ skills add

Skills: the tools, wrapped in a task

A tool call is a verb. A skill is a job — publish this artifact, migrate that site, keep this loop's output at one address. Same twelve tools underneath, but the agent knows when to reach for them.

Tool versus skill

The MCP server gives an agent capability: publish_html, update_site, set_password. A skill gives it judgement — which of those to call, in what order, with what expiry, and what to do with the URL afterwards. If your client reads the skills format, a skill is a folder with a description and a few instructions; if it does not, the same content works as a project rule or a slash command.

Publish

The one every user wants first: the artifact exists, put it somewhere a human can open. The skill's whole job is to stop the agent pasting HTML into the chat as a fallback. It calls publish_html, sets a sane expiry, and reports only the link.

Migrate

Move a rendered site off a website builder. Fetch the pages, keep the markup and assets, publish the tree as one zip, then check the result actually renders rather than trusting the 201 — the honest version of this job is mostly verification. Details on the migration page, including what does not survive: forms, search and anything the builder was running server-side.

Review

Publish with the toolbar enabled, hand the link to a human client, then read the comments back as structured input with list_feedback and close them with resolve_feedback. That is a whole review round with no shared account — how the loop is wired.

Keep one address alive

For a long-running loop: publish once, then replace in place forever after. The skill's real content is a rule — never mint a second link for the same job — plus where to store the site id so the next run finds it. See agent-loop hosting.

Install one

This deployment does not ship a package registry, and there is nothing to install for the capability itself: register the server, and every client that works with skills already has the tools. Write the skill against the tool names — they are stable, and they are documented in the docs.

Register the server first:

claude mcp add --transport http opentree https://read.botook.ai/mcp \
  --header "Authorization: Bearer otr_live_YOUR_KEY"

A skill worth copying

---
name: publish-artifact
description: Publish an HTML or markdown artifact to a private link and report the URL.
---
1. Call publish_html with the artifact's full text.
2. expires_in_hours: 168 unless the user said otherwise.
3. If the content is for someone outside the team, set a password and say so.
4. Fetch the returned URL once and confirm it renders before reporting it.
5. Report the URL. Do not paste the HTML back into the conversation.

Step 4 is the part people leave out. A 201 means the bytes were accepted, not that the page renders — check the artifact, not the status code.

Where skills work

Human still holds the keys

A skill can publish, gate and expire. It cannot mint or revoke API keys, and it cannot claim a page into a different account — those stay in the dashboard, where a person is looking at them.

Handoff

The job nobody writes down: getting something out of a chat and into a colleague's hands with a rule attached. The skill's content is mostly the rule — a password when the audience is external, an expiry that matches how long the thing is true for, and burn_after_read when the page carries a credential and should not survive being read once.

set_password({ site_id: "…", password: "…" })
set_expiry({ site_id: "…", expires_in_hours: 48 })

Clean up

Loops publish. Without a rule they publish forever, and six weeks later the account is a graveyard of drafts that still open. This skill is list_sites plus a policy: delete anything whose job is finished, and let the seven-day default catch the rest.

list_sites({})
delete_site({ site_id: "…" })

Writing one that will not lie to you

Every skill above ends with the same instruction, and it is the one that matters: verify the artifact, not the status code. A 201 proves the bytes were accepted. It does not prove the markdown rendered, the zip unpacked with a usable entry point, or the gate is really in front of the page. Fetch the URL back and look at what came out before reporting success.

# the last step of every skill worth trusting
curl -s "$URL" | head -c 400

Questions

Do I need skills to use this?

No. Skills are ergonomics. The twelve tools work on their own.

Do skills cost anything?

Nothing here does — see pricing.

Can a skill set expiry?

Yes, that is just set_expiry, and never is a legal value.

Keep reading