Use prompts and installed skills

1. Find a prompt in Desktop

1. Open Prompts in Desktop's left menu. Search by task or choose a category, then open a prompt card.
2. Read its description, required inputs, and tips. Sign in if requested and follow the access options shown for your account.
3. When the body is available, review it before choosing Copy or Start a new chat.

The current Prompt Store offers one taste per prompt to free accounts and subscription access with bookmark saving. Check your account's displayed access state; viewing or saving a prompt does not include model execution or guarantee a result.

2. Start with the required inputs

Copy places the available body on the clipboard. Paste it into the intended conversation and adapt its inputs, output, and permissions to your job. If copying fails, select the body directly or check clipboard access.

Start a new chat creates a One conversation. A prompt without required attachments can be sent automatically on arrival. If the prompt lists required attachments, review the Required attachments dialog; its new conversation starts with the prompt prepared so you can attach the files and send it yourself.

Inspect the selected model and actual result. If chat creation fails, keep the prompt open and use the displayed retry; do not consume another taste just to recover the same start attempt.

3. Save a prompt reference

When your account allows it, use Save on the card and confirm Saved appears. This is a bookmark to the prompt, not an installed agent. If the app says the save result is unknown, refresh the saved state before applying the same action again.

4. Inspect and use a skill

1. In Desktop, open Setup (MCP, etc.) → MCP, Plugin. Use the skill or plugin view to inspect the available skill and its installation state.
2. Open the skill to read its instructions and referenced files. Review its purpose and setup requirements before adding its plugin or skill bundle.
3. In an external host, use that host's installed skill or command picker. Use the exact name it shows; for example, Codex exposes $hephaestus-build while Claude Code uses /hep-build after the appropriate Agentlas OS installation.

A skill is instructions, not an account connection or permission grant. Required programs, MCP connections, browser sign-in, keys, and writable folders still need their own setup. A skill shown in a catalog is not proof that the current host can execute it.

5. Package a repeatable job

If a prompt and skill combination becomes a repeated workflow, use Build to create an agent with clear inputs, output criteria, and supporting references. Review the proposed tool connections and test the generated package. Building a package does not automatically install every external dependency or authorize public distribution.