tinyhat-hat-wearing

Files (1)

• SKILL.md

SKILL.md (first lines)

# Wear a Tinyhat Hat

A Hat adds a private repository of skills and optional Computer-local
credentials to an agent. Hats are free to install. Tinyhat checks whether the
Hat is public or this user is in its private audience, then the Computer
downloads the exact repository with a short-lived, read-only GitHub credential.
Credentials that the Hat creator supplied still transfer as encrypted
ciphertext. Credentials the creator left for each user to provide are resolved
against this Computer first, so an existing compatible credential is reused.

## Install on this agent

When the user provides a Hat URL, a full Hat handle, or asks to install it:

1. Call `tinyhat_hats` once with:

   ```json
   {"action":"wear","identifier":"https://tinyhat.ai/account/hats/hat-name"}
   ```

2. If `installation_started=true`, say:

   > I loaded **{hat_title}** and am preparing this Computer from its
   > instructions. This usually takes less than a minute.

3. Read the credential outcome:
   - `creator_credentials_pending`: explain that the creator-supplied encrypted
     bundle is moving automatically between Computers. Never ask either person
     to approve it or paste a value into chat.
   - `user_credential_required`: name the missing credential and explain which
     service it is for using the returned description. Tinyhat has already sent
     a secure Credentials button. If the user does not have an account with
     that provider, guide them to its official signup or credential page, then
     tell them to enter the value through the secure button. Never ask them to
     paste it in chat.
   - `credentials_ready`: if `reused_credentials` is non-empty, say Tinyhat
     reused those existing Computer credentials and did not ask for duplicates.
4. Do not claim the Hat is ready until `status=active` or Tinyhat sends the
   final `Hat installed` confirmation after the gateway refresh.

If the platform says the Hat is not accessible, explain that it is private and
the creator must add this Tinyhat user. Do not reveal other allowed users.

## Resume after assignment

Only when the user asks to install or resume a Hat, or a Tinyhat message in
this conversation reports a pending Hat setup, call:

```json
{"action":"resume_installation"}
```

Use the same progress and completion rules above. A resume is idempotent.

A new Computer or a greeting alone does not imply a Hat installation. If
`status=none`, continue the user's conversation silently. Do not announce that
there is no Hat, repeat a setup checklist, or ask the user to install one.

Creator-supplied credential transfer does not require an agent or creator-side
chat turn. The platform dispatches a bounded command to the exact Computer
registered for that Hat. Its plugin encrypts to the consumer key and signs with
the Hat's creator key; the consumer verifies, decrypts, and saves locally.
Tinyhat relays ciphertext only. User-provided credentials use the normal
browser-encrypted Tinyhat Credentials flow and become available to other Hats
on the same Computer by exact credential name.

## Boundaries

- Never put credential values in a Hat repository.
- Never ask for secrets in Telegram or ordinary chat.
- Never request write access to a consumed Hat repository.
- Never run authoring repository sync for a consumed Hat.
- Accept the canonical handle or the Hat page URL exactly as the user sends it.
- Use `hat-authoring` for create, title/audience/handle edits, files,
  credentials, or deletion of a Hat owned by this user.

From tinyhat-ai/tinyhat, MIT.

More from tinyhat-ai/tinyhat