# Asking Claude to run your Osyrin account

> The toolchain ships six Claude Code skills for Osyrin Cloud, so you can ask Claude to sign you in, create an app and its environments, deploy it, add people, set secrets and a custom domain, take and restore backups, and read logs and usage. Each one drives the ordinary `osy` and `osyrin` commands, says what it will change, asks before anything that cannot be taken back, and never sees a password or a secret's value. The installer puts them in `~/.claude/skills`; `osy init --agent claude` writes them into the project.

<!-- id: local-asking-claude-to-run-your-osyrin-account · area: local · stability: preview · html: https://osysharp.com/reference/local/asking-claude-to-run-your-osyrin-account/ -->

## Summary        {#summary}

Once you have an Osyrin account, you can ask Claude Code to do the work in it: *"deploy this to staging"*, *"invite
ada@example.com as an admin"*, *"restore yesterday's backup"*. The toolchain carries one skill for each kind of
operation, and Claude loads the one that fits what you asked. A skill tells Claude which `osy` and `osyrin` commands to
run, how to read their answers, and where to stop and ask you.

## Signature      {#signature}

```console
osy skills list [--json]
osy skills install [--project] [--refresh] [--json]
osy skills remove [--project] [--json]
osy init --agent claude [--no-cloud-skills]
```

## Description    {#description}

**The skills.**

| skill | what you can ask it |
|---|---|
| `osyrin-account` | sign in or out; which account, organization, apps and environments you have; which app this project is |
| `osyrin-deploy` | create an app, add an environment, deploy and follow the rollout, see what is deployed, go back to an earlier version |
| `osyrin-people` | invite or add people to an organization, change or remove their role, give someone a role on one app, the app's own user accounts |
| `osyrin-configure` | give the app's secrets their values, serve it at your own domain and check the DNS records |
| `osyrin-backups` | take a backup, list and download them, restore one into a copy and switch onto it |
| `osyrin-observe` | read the logs, open a trace at the fault, see deployments, and how much of the plan is used |

**What every skill does the same way.**

- **It drives the CLI.** Every step is an `osy` or `osyrin` command you could type yourself, and a skill never calls
  the platform any other way. Answers are read as JSON where the command offers `--json`.
- **It names what it acts on.** Before changing anything it checks you are signed in and says the server,
  organization, app and environment, and when there is more than one and you have not said which, it asks.
- **It asks before what cannot be taken back.** A deploy into the environment that serves your users, restoring a
  backup over live data, removing a person or a domain, and making someone an Owner each wait for your yes.
- **It never handles a password or a secret.** Signing in happens in your browser (`osyrin login`). Setting a secret's
  value, or a password for an app account, is a command Claude gives you to run in a terminal of your own; the CLI asks
  you for the value there, and when there is no terminal to ask on it refuses and prints the command instead.

**Where they come from.** The skills are part of the `osy` binary, so they always describe the commands the binary
beside them has. The installer runs `osy skills install`, which writes them to `~/.claude/skills` (or
`$CLAUDE_CONFIG_DIR/skills`), where Claude Code reads them in every project. Set `OSY_NO_SKILLS=1` when installing to
leave them out. A Homebrew install prints the command instead of running it.

`osy init --agent claude` also writes them into the new project's `.claude/skills`, beside `osy-design`, so a teammate
who clones the project has them too. `--no-cloud-skills` leaves them out.

**Keeping them current.** `osy upgrade` rewrites the skills already installed in `~/.claude/skills` with the new
release's text. It never adds back one you removed. `osy skills install` again does the same by hand, and replaces any
copy that differs from the binary's.

- `osy skills list` — each skill, what it is for, and whether it is installed for every project and in this one.
- `osy skills install` — write them to `~/.claude/skills`; `--project` writes them to this folder's `.claude/skills`;
  `--refresh` only updates the ones already there.
- `osy skills remove` — take them out again (`--project` for this folder). Only the skills' own files are removed;
  anything else in those folders is kept.

## Examples       {#examples}

```console
osy skills list                 # which skills ship, and where they are installed
osy skills install              # for every project
osy skills install --project    # into this project only
osy skills remove               # take them out of ~/.claude/skills
```

Then, in Claude Code, ask in your own words — *"sign me in to Osyrin and deploy this app to staging"*.

## See also       {#see-also}

[Signing in to Osyrin](https://osysharp.com/reference/local/signing-in-to-osyrin/) — what `osyrin login` does in the browser.

[Deploying your app to an environment](https://osysharp.com/reference/local/deploying-your-app/) — what a deploy does, step by step.

[Starting a project](https://osysharp.com/reference/local/starting-a-project/) — what else `osy init` writes.

[Upgrading the toolchain](https://osysharp.com/reference/local/upgrading-the-toolchain/) — `osy upgrade`, which keeps the skills current.