# How to install and use an Oysterun Skill

Find, install or update, verify, and safely use an eligible Oysterun Skill in a Claude or Codex Session.

Use this guide when you want a Claude or Codex Session to perform an Oysterun product task through an installed Skill. You will find the current Skill state, install or update the eligible Oysterun set, verify it from visible UI, and use one Skill for a read-only task.

The short rule:

install and update entries act immediately when selected; product-Skill helper entries only insert a reference into your draft. Always read the entry and the draft before deciding what happens next.

## Before you start

- You are signed in to Oysterun and have a live Session open.
- The Session uses **Claude** or **Codex**. Those are the supported provider Skill folders.
- An ordinary new eligible Session currently starts with the Oysterun-managed Skill set already provisioned. The visible menu state—not the Session's age—decides whether installation is needed.
- The Session is using the folder where you want this Oysterun Skill set to be available.
- No private credentials, local paths, or unrelated Session content will be included in screenshots or shared evidence.

**Starting screen:** the Chat view for the exact live Session you want the Skill to help. The message composer must be visible.

Scope:

installation applies to this provider and Session folder. It does not sign the provider in, grant new Oysterun authority, change other Session folders, or prove that a later provider response used the correct Skill.

## 1. Find the current Skill state

![Complete desktop composer menu showing the current Oysterun update action and product Skill helpers.](../assets/publication/skill-state-menu.jpg)

Visible checkpoint: the current Session menu shows the installed-state

/update_oysterun_skill

action together with the Oysterun product-Skill helpers.

1. Click the message composer.
1. Type **/** and wait for **Commands and Prompts**.
1. Read the entries under **Oysterun**. Do not select an install or update entry until you intend to perform it.

**Expected ordinary state:** a new eligible Claude or Codex Session normally shows **/update_oysterun_skill** and the product-Skill helpers because the managed set was auto-provisioned. Do not assume a newly created Session must be missing the set; follow the state actually shown.

Visible entry or status

Meaning

Next step

/install_oysterun_skill

The eligible Oysterun set is actually missing.

Use conditional step 2 only when this entry is visible.

/update_oysterun_skill

and product-Skill helpers

The Oysterun-managed set is installed. This is the ordinary state for a new eligible Session.

Skip step 2. Verify or use it; update only when intended.

Oysterun skill folder is not managed

An existing folder is not owned by Oysterun.

Stop; Oysterun will not overwrite it.

Oysterun skills unavailable

This provider does not expose a supported Skill folder.

Use a Claude or Codex Session.

Oysterun commands unavailable

The status check failed.

Use the bounded recovery in step 8.

Checkpoint:

the menu gives one unambiguous missing, installed, unmanaged, unsupported, or unavailable state for this Session.

## 2. Install only when the menu shows a missing set

This is a state-dependent recovery route, not the promised setup route for every fresh Session. Follow it only when the actual menu offers **/install_oysterun_skill**. If update and helper entries are already present, skip this step.

1. Select **/install_oysterun_skill**.
1. The selection runs immediately as a local Oysterun action. It is not inserted as a draft and is not sent to Claude or Codex as an ordinary prompt.
1. Wait for the result in the timeline. A successful missing-set install says Oysterun skills installed for this agent folder. Provider delivery suppressed.
1. Type **/** again. The menu should now offer **/update_oysterun_skill** and the product-Skill helpers.

Do not click twice.

If no result appears, do not repeat the install merely because the menu closed. Wait for the timeline result, then use the recovery section.

## 3. Update the managed set only when replacement is intentional

![Same Session timeline showing the terminal result of an intentional managed Skill update.](../assets/publication/skill-update-result.jpg)

Visible checkpoint: this is the terminal timeline result of the Skill update action; it is not a menu label or a second update instruction.

If the menu shows **/update_oysterun_skill** and the helpers, the managed set is already installed. Skip step 2. The current supported update path is the composer entry, and selecting it immediately replaces the managed set for this provider and Session folder:

1. In the same Session composer, type **/** and wait for **Commands and Prompts**.
1. Confirm that **/update_oysterun_skill** is the visible installed-state action for the intended Session and folder.
1. Only when replacement is intentional, select **/update_oysterun_skill** once. The selection runs immediately as a local Oysterun action; it is not inserted as a draft and there is no second confirmation dialog.
1. Wait for the timeline result. A completed composer update says Oysterun skills updated for this agent folder. Provider delivery suppressed.
1. Do not select the entry again merely because the menu closed. Reopen **/** only after the timeline result appears.

Review before acting:

if you need more state context, open

More Options

>

Session Profile

>

Oysterun Skills

and read

Provider Skill Set

. Reading that state does not update the set. Return to the composer and use

/update_oysterun_skill

only when overwrite is already intentional.

## 4. Verify before asking the provider to use a Skill

1. Return to the same live Session and type **/**.
1. Wait for the status check to finish.
1. Confirm that **/update_oysterun_skill** and the product-Skill helper entries are present.
1. If you selected the update in step 3, require both its completed timeline result and this refreshed installed-state menu before treating the update as verified.

Checkpoint:

a success message by itself is not the final proof. The refreshed menu must show the installed-state helpers for this exact Session.

## 5. Choose the helper that matches the task

![Complete desktop composer draft with the Codex sessions Skill reference and a read-only status and URL request before send.](../assets/publication/skill-helper-draft.jpg)

Visible checkpoint: selecting

/oysterun_sessions_skill

inserted the provider-correct Codex reference, and the complete read-only request is still a draft before send.

Helper

Use it for

/oysterun_sessions_skill

Session lists, status, URLs, profiles, start, resume, rename, restart, interrupt, or stop

/oysterun_session_chat_skill

Session messages, search, sending, or in-Session Loops

/oysterun_find_context_skill

Bounded message context around one known event

/oysterun_scheduler_skill

Host schedules and their runs or logs, not in-Session Loops

/oysterun_mail_skill

Oysterun Mail

/oysterun_notifications_skill

Notification status or an explicitly authorized send

/oysterun_website_skill

Website status, setup, validation, URL, or access

/oysterun_telegram_skill

Telegram status or per-Session Telegram setup

Choose by the user's goal.

A Host schedule and an in-Session Loop are different stores. A truthful empty schedule list does not prove that a Loop is absent.

## 6. Use one Skill for a read-only task

![Same Session terminal Codex response reporting the current Session status and URL and stating that no changes were made.](../assets/publication/skill-read-only-result.jpg)

Visible checkpoint: after the exact read-only request was sent once, the same Session's terminal provider response reports its current status and URL and confirms

No changes made.

1. In the same composer, type **/oysterun_sessions_skill**.
1. Select the matching helper. Oysterun inserts the correct Claude- or Codex-relative Skill reference into the draft. This does not send or run anything.
1. After the inserted reference, add: Show this current Session's status and URL. Do not change anything.
1. Review the complete draft, then select **Send message** once.
1. Wait for the provider's terminal response. Confirm that it reports the current Session's status and URL rather than a generic explanation or another Session.

Finished:

the helper selected the eligible Skill, the provider returned the requested read-only product result, and the result matches the Session you started from.

## 7. Keep Claude and Codex behavior aligned

- The same eight Oysterun helper names are available for both supported providers.
- There is no separate capability-selection step in this journey. An eligible installed Oysterun set exposes its helpers by default, while every selected Skill still keeps its own safety and authorization rules.
- Let the menu insert the provider-correct Skill reference. Do not copy a reference from a Claude Session into Codex or the reverse.
- Changing the Session provider or Session folder changes the Skill-status target. Reopen **/** and check the new state instead of assuming the prior install applies.
- Installation makes the Skill files available; the provider still has to follow the selected Skill and return the requested result.

## 8. Recover without forcing an overwrite or duplicate action

- **Loading Oysterun commands...**: wait for it to settle. If it does not, reload the same Session once and reopen **/**.
- **Oysterun commands unavailable**: preserve the visible error, confirm the Session is still live, and retry the status check once.
- **Oysterun skill folder is not managed**: stop. Do not use update and do not delete the existing folder from this flow.
- **Oysterun skills unavailable**: stop this path and use a Claude or Codex Session with the intended folder.
- **Install or update failed**: do not repeat blindly. Preserve the visible result and reopen **Session Profile** to read the current **Provider Skill Set** state.
- **Installed, but helpers are absent**: reopen the composer menu once after the status refresh. If they remain absent, stop with the visible status and do not claim verification.
- **The provider returns the wrong task or route**: do not treat installation as proof of Skill use. Repeat the exact helper and read-only request once; if the result is still wrong, preserve it and stop.

Safe stop point:

an unmanaged folder, unsupported provider, ambiguous Session target, missing installed-state helpers, failed local outcome, or wrong provider result remains unresolved. Do not work around it with manual paths, repeated clicks, or a broader mutation.