# Agent playbook (Skillkren)

You are connected to **Skillkren**, a library of reusable AI skills and examples of their output. Skills follow the open [Agent Skills](https://agentskills.io/specification) format: a SKILL.md (instructions with `name` and `description` frontmatter), plus optional files in `references/`, `scripts/`, and `assets/`.

**Brand name:** always **Skillkren**. Domain: `skillkren.tech`.

## First steps

1. Call `get_docs` with topic `agent` (or read `https://skillkren.tech/docs/agent.md`) if you need a refresher.
2. Use `list_skills` to check the user's skills and their teams' libraries before creating duplicates. To open someone else's shared skill, use `get_skill` with the id from its link.
3. On the Free plan a user can save up to 25 skills; `upsert_skill` returns an error at the limit. Don't work around it.
4. Use `upsert_skill` with a clear title. It updates your own skill with that title, or creates a new one. Pass `team` to work in a team library.
5. Always attach at least one **example** when publishing a new skill (`add_example`).

## Using a skill

1. Load it with `get_skill` and follow its instructions.
2. `get_skill` lists bundled `files` by path. Read one with `get_skill_file` only when the instructions point to it or the task needs it.
3. Use the skill's examples as the reference for format, tone, and quality.

## Writing a good skill

- **Description:** what the skill does *and when to use it*, with the words a user would actually say. Agents decide whether to load a skill from this alone.
- **Instructions** (`content`): raw Markdown, not HTML. Steps, rules, and what good output looks like. Keep it under about 500 lines.
- **References:** move long material (style guides, API notes, checklists) into `references/` with `put_skill_file`, and name each file by its path in the instructions, e.g. "For banned words, read `references/banned-words.md`". Templates and data go in `assets/`, runnable code in `scripts/`.
- **License:** only set `license` (e.g. `MIT`, `Apache-2.0`, `CC-BY-4.0`, `Proprietary`) when the user chooses one. Ask; don't pick for them.
- **Requirements:** set `compatibility` only if the skill needs specific tools or access.

## Uploading a skill folder

When the user asks you to upload a local skill (for example `~/.claude/skills/pdf-processing/`):

1. Read `SKILL.md`. Use its `name` (as a readable title), `description`, and `license`; the body after the frontmatter is the `content`.
2. Call `upsert_skill` with those fields. If the folder has a LICENSE file, pass its text as `licenseText`.
3. For each file under `references/`, `scripts/`, and `assets/`, call `put_skill_file` with the same relative path, e.g. `references/forms.md`.
4. Only text files up to 100 KB each, 30 per skill, one subfolder deep. Skip binaries (images, PDFs) and tell the user which files you skipped.
5. Give the user the skill's link when done.

To go the other way, the user can download any skill as a zip from its page and unzip it into their app's skills folder.

## Visibility

New skills are **Private** (only the owner). **Unlisted** skills can be opened by anyone with the link; **Public** skills are also listed on the owner's profile at `https://skillkren.tech/u/<username>`.

You can't change visibility. If the user wants to share a skill, send them to its page and tell them to use the switch next to the title. Never suggest sharing a skill with secrets in it.

## Auth context

Your connection belongs to one user. Everything you create is owned by that user, and you can only change what that user can change.

## URLs to cite

- App: `https://skillkren.tech/app`
- Skill: use the `url` the tools return. It looks like `https://skillkren.tech/u/<username>/skills/<id>`.
- Examples: the skill URL plus `/examples`. References: the skill URL plus `/references`.
- Docs: `https://skillkren.tech/docs`
- Agent doc (raw): `https://skillkren.tech/docs/agent.md`

## Don'ts

- Don't delete skills or files unless the user confirms.
- Don't paste secrets into skills, files, or examples.
- Don't rely on client-side rendering; store Markdown source.
