Skills

Status

Skill installation works: Hoook fetches a skill, validates it, records it, and can remove it again. Skill execution does not exist. There is no runtime, no dispatcher, and nothing that loads a skill into a prompt. An installed skill sits on disk and does nothing.

Installing skills today is useful for staging content you want ready later, and for authoring and validating your own. It will not change how an agent behaves.

Installing

Two sources are supported.

From a local folder

Point Hoook at a directory and it copies the whole tree into your workspace. Useful while writing a skill.

From a git repository

Give Hoook a git URL and it runs a shallow clone (--depth 1) into your workspace. It clones the default branch; there is no way to pin a tag, branch, or commit yet, and no update command. To refresh a skill, uninstall and reinstall it.

A clone runs code-adjacent content from a URL, so only install skills you trust.

What a skill looks like

A skill is a folder with a SKILL.md at its root. Hoook reads three fields from that file's frontmatter:

---
name: seo-blog-writer
description: Drafts a long-form SEO post from a keyword brief.
version: 0.1.0
---

Everything below the frontmatter is the skill body.

Field	Used for
name	Display name and folder name
description	Shown in the skills list
version	Shown in the skills list

Anything else in the frontmatter is ignored. In particular there is no target field yet, so Hoook guesses which agent a skill is for by matching text in its name and description. Do not rely on that guess.

Where skills are stored

~/.hoook/workspaces/<workspace-id>/skills/<skill-name>/

Uninstalling deletes that folder. Because skills are ordinary files, you can inspect one before trusting it.

The marketplace

The Marketplace tab in the app is a mockup. The listings are hardcoded, the install counts are not real, and the Install button does nothing. There is no registry behind it. To install a skill, use a local folder or a git URL as described above.