# Install Oysterun Skills

Use this page when you need to check whether Oysterun Skills are available for
the selected provider, install or update the packaged Oysterun skill set, and
verify the visible result before asking a provider to use a Skill.

Oysterun Skills are installed into the selected provider's skill folder for the
Session. They are not dashboard login, provider authorization, or a shortcut
around normal Oysterun controls.

## Prerequisites

- You are signed in to Oysterun.
- A Session Setup screen or live Session Profile is open.
- The Session uses a supported provider skill root. Current supported providers
  are Claude and Codex.
- The selected Session folder is the folder where you want the provider-facing
  `Oysterun` skill set to be installed or updated.

Starting screen: either Session Setup before starting or resuming a Session, or
Session Profile for a live Session.

## Use Session Setup

1. Open Session Setup.
2. Find **Install/Overwrite Oysterun Skills**.
3. Keep the checkbox state that matches the visible status for the selected
   provider and folder.
4. Start or resume the Session.

Expected result: you should see one of these visible states before launch:

- missing Oysterun skills default to checked;
- existing marker-owned Oysterun skills default to unchecked and are overwritten
  only when checked;
- existing unowned Oysterun folders disable the checkbox.

Host Preferences is not the route for provider skill install or update controls.

## Use Session Profile

1. Open the live Session.
2. Open **Session Profile**.
3. Find **Install/Update Oysterun Skills**.
4. Use the button for the selected live Session.
5. If Oysterun asks for confirmation before overwriting marker-owned skills,
   confirm only when you intend to update that owned Oysterun skill set.

Expected result: Oysterun checks status first, installs missing skills, updates
marker-owned skills only after confirmation, or refuses an unsafe overwrite.

Session Profile does not use this action to change `.oysterun/config.json`.

## Use The Local Install Command

You can also type `/install_oysterun_skill` in the Route C composer. Oysterun
intercepts this as a local Host command before it reaches Claude, Codex, or
another provider.

Use the command by itself to install a missing aggregate Oysterun skill set. To
overwrite an existing marker-owned set, include one of these update tokens:

```text
--overwrite
overwrite
--update
update
```

Expected result: the chat shows a local Host outcome for the same command
message. The result explains whether Oysterun installed, updated, refused, or
could not verify the provider skill state. The command is not sent as ordinary
provider chat text.

## Use An Installed Skill

After Oysterun reports an eligible installed state, use visible product routes
to insert a provider-relative Skill reference into the composer.

Current helper Skill slash routes are:

- `/oysterun_sessions_skill`
- `/oysterun_session_chat_skill`
- `/oysterun_find_context_skill`
- `/oysterun_scheduler_skill`
- `/oysterun_mail_skill`
- `/oysterun_notifications_skill`
- `/oysterun_website_skill`
- `/oysterun_telegram_skill`

Expected result: the helper route inserts text for the provider to read. It
does not auto-send, install, update, mutate provider skill folders, prove
provider delivery, or prove command success by itself. Review the inserted text
and send intentionally only when you want the provider to use that Skill.

## What Oysterun Installs

Oysterun installs one aggregate provider skill set named `Oysterun`, with
module Skill files for the supported Oysterun product areas. The installed files
come from Oysterun's packaged runtime source, not from development-only mirror
folders.

Oysterun-owned Skill files include an ownership marker. Installation is
fail-closed:

- if the `Oysterun` folder is missing, install is allowed;
- if an existing `Oysterun` folder is marker-owned, overwrite is allowed only
  when you explicitly choose update or overwrite;
- if an existing `Oysterun` folder is unowned, overwrite is refused;
- symlinks, non-file entries, and target paths outside the selected Session
  folder are refused.

## What This Does Not Mean

Installing Oysterun Skills does not grant dashboard login, raw token output,
direct Host endpoint calls, provider authorization, broad dashboard authority,
automatic destructive actions, or general provider skill folder mutation.

Runtime Oysterun product Skill commands use the live Session capability
environment provided by the Host. Dashboard/admin operations, provider auth,
credentials, raw config editing, and external operator shells still use their
normal authorization paths.

The current product does not provide a user capability-selection screen.
Installed Oysterun capabilities are available by default. This does not mean a
provider has successfully used the correct Skill: the provider must still read
the matching installed Skill, call its supported product CLI route, and return
the requested result. A separate readback may verify that a requested create or
update actually exists; that readback is evidence, not another Session-
management feature.

In-session Loops and Host Scheduler schedules are distinct. A request about a
Loop must use the Session Chat/Loop route; a request about a Host schedule must
use the Scheduler route. A truthful empty Scheduler list does not prove that a
Loop is absent. An unqualified “Loop” request refers to the current Session;
only genuinely ambiguous intent requires a clarification question.

## Recover From Install Or Update Problems

If installation or update does not reach an eligible installed state:

1. Check the visible status in Session Setup or Session Profile.
2. If skills are missing, use the checked Session Setup option, the Session
   Profile install button, or `/install_oysterun_skill`.
3. If Oysterun reports a marker-owned existing set, choose overwrite or update
   only when you intend to replace the existing Oysterun-owned set.
4. If Oysterun reports an unowned existing folder, stop and choose another
   Session folder or remove the conflicting folder outside Oysterun after you
   confirm it is safe.
5. If status is unavailable, retry from the same visible route after the
   Session and provider status finish loading.
6. If the login screen appears, sign in and reopen Session Setup or Session
   Profile before trying again.