Skills orca-cli
📦

orca-cli

Content revision r1 High Risk ⚙️ External commands🌐 Network access

Manage Orca Worktrees and Terminals

Orca projects often span worktrees, terminals, automations, and embedded browser tabs. This skill gives agents a precise CLI workflow for managing those Orca surfaces.

Supports: Claude Codex Code(CC)
⚠️ 38 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "orca-cli" from https://skillstore.io/skills/stablyai-orca-cli.md and its manifest at https://skillstore.io/api/skills/stablyai-orca-cli/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "orca-cli". Check my Orca workspace status.

Expected outcome:

Orca is running. The active worktree has two terminals, one idle agent session, and no browser tab requiring attention.

Using "orca-cli". Hand this bug investigation to another agent.

Expected outcome:

Created an independent Orca worktree for the investigation and started a Codex terminal with the task brief. I stopped monitoring after the handoff.

Using "orca-cli". Review the embedded browser state before continuing.

Expected outcome:

The active browser tab is loaded and has current element references. A fresh snapshot is available before any click or form action.

Security Audit

High Risk
v3 • 7/9/2026 Open versioned report

No prompt injection or malicious exfiltration language was found in SKILL.md. Many static hits are Markdown formatting false positives, but several examples are real Orca CLI workflows that create worktrees, launch agents, send terminal input, schedule automations, and control browser or emulator state. These capabilities are legitimate for the skill and should require explicit user intent and narrow scoping.

1
Files scanned
308
Lines analyzed
26
Review items
0
False positives ignored

Confirmed security concerns (2)

High
Sensitive Browser Control Surface
The skill documents embedded browser commands that can evaluate JavaScript, read cookies, capture screenshots, inspect network data, upload files, and use exec passthrough. These are legitimate Orca features, but they can expose session data or perform unintended page actions without explicit user intent.
The listed browser commands include eval, cookie get, network capture, upload, screenshot, and exec. The context is legitimate tooling, but the sensitive capabilities are explicit.
Medium
Scheduled Agent Automations Can Run Later
The skill documents creating and running scheduled Orca prompts against repos or existing workspaces. This can start future agent activity that modifies workspace state after the initial request.
The automation examples include create, edit, run, provider selection, repo or workspace targeting, and reuse-session behavior. This clearly describes delayed agent execution.
Capability review items (26)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High
Ruby/shell backtick execution
```bash
The browser command block includes navigation, uploads, JavaScript eval, cookie access, screenshots, network capture, and exec passthrough. These can expose sensitive page data or perform unintended actions.
High
Ruby/shell backtick execution
- Less common workflows can use typed commands above or `orca exec --command "<agent-browser command
The line allows passthrough to orca exec for less common browser workflows. Passthrough command execution is powerful and can bypass safer typed commands.
Medium
Ruby/shell backtick execution
```bash
The code block instructs running Orca CLI commands that inspect local Orca status, worktrees, and terminals. This is legitimate setup behavior, but it is real external command execution against local application state.
Medium
Ruby/shell backtick execution
```bash
The code block starts Orca and checks status through the CLI. This is expected for the skill, but it can launch or change local application state.
Medium
Ruby/shell backtick execution
```bash
The example creates a new Orca worktree and launches Codex with a user prompt. That can change repository state and delegate work to another agent.
Medium
Ruby/shell backtick execution
`worktree create --agent codex --prompt ...` launches the known Codex agent but does not accept Code
The prose describes launching Codex through Orca and passing prompts to a new worktree. This is a legitimate workflow, but it controls external agent execution.
Medium
Ruby/shell backtick execution
```bash
The code block creates a worktree, starts a Codex terminal, waits for it, and sends a prompt. These commands can alter local workspace state and start agent activity.
Medium
Ruby/shell backtick execution
```bash
The command sends text into an existing terminal. Direct terminal input can execute commands or drive an agent, so the external command risk is real.
Medium
Ruby/shell backtick execution
```bash
The command block manages Orca repos and worktrees, including adding repos, changing metadata, and force-removing worktrees. These are local side effects, not passive documentation.
Medium
Ruby/shell backtick execution
```bash
The command block creates worktrees and can launch agents or run setup behavior. This is expected for Orca, but it performs external operations.
Medium
Ruby/shell backtick execution
- `--agent <id>` launches that agent in the first terminal; `--prompt <text>` sends initial work to
The documented flags launch an agent and send an initial prompt to it. That is real agent execution controlled through the CLI.
Medium
Ruby/shell backtick execution
- `--setup run|skip|inherit` controls repo setup hooks. Default is `inherit`, which follows the repo
The setup option can follow repository setup policy and run project-defined hooks. Running setup hooks is security-relevant even when intended.
Medium
Ruby/shell backtick execution
- `--run-hooks` is a legacy alias for `--setup run`; it also reveals/activates the new worktree.
The legacy run-hooks flag can activate setup hooks for a worktree. That may execute repository-defined commands and should remain a confirmed risk.
Medium
Ruby/shell backtick execution
- `--agent`, `--activate`, and `--run-hooks` reveal the new worktree. Plain create stays in the back
The static finding appears in a CLI-focused skill and may indicate actionable external command guidance. Kept with low confidence because the local context is documentation rather than source code.
Medium
Ruby/shell backtick execution
- If an older installed CLI rejects `--agent`, `--prompt`, or `--setup`, create the worktree normall
The fallback instructions tell the agent to create a terminal and send a prompt manually. That is direct control over a CLI session.
Medium
Ruby/shell backtick execution
- `worktree create` creates a new checkout. For a fresh agent in the current checkout, use `orca ter
The line distinguishes creating a checkout from launching a fresh agent in the current checkout. Both are external Orca terminal or worktree operations.
Medium
Ruby/shell backtick execution
```bash
The command updates an Orca worktree comment through the CLI. It is a low-impact local state change, but still an external command.
Medium
Ruby/shell backtick execution
```bash
The terminal command block reads, sends input, creates, splits, stops, switches, and closes terminals. These actions can control shell or agent sessions.
Medium
Ruby/shell backtick execution
- Use `terminal send` only for direct terminal input or one-off prompts where no task state, inbox,
The rule authorizes terminal send for direct input or one-off prompts. Sending terminal input can run commands or alter an agent session.
Medium
Ruby/shell backtick execution
- For structured coordination, invoke the `orchestration` skill; it uses `orca orchestration ...` co
The static finding appears in a CLI-focused skill and may indicate actionable external command guidance. Kept with low confidence because the local context is documentation rather than source code.
Medium
Ruby/shell backtick execution
- Use `terminal create --worktree active --command "<agent>"` for a fresh agent in the current workt
The line instructs creating a terminal that runs an agent command. Launching an agent process is real external command execution.
Medium
Ruby/shell backtick execution
```bash
The automation commands create, edit, run, and remove scheduled Orca prompt runs. Automated agent runs can execute later and affect workspaces.
Medium
Ruby/shell backtick execution
These commands control only Orca's embedded browser tabs. For external Chrome/Safari/webviews or Orc
The prose establishes control over Orca embedded browser tabs and references desktop control through Orca computer commands. Browser control can mutate page state.
Medium
Ruby/shell backtick execution
```bash
The code block navigates, snapshots, and clicks in the embedded browser. These are external UI actions with page-side effects.
Medium
Ruby/shell backtick execution
The mobile emulator surface is workspace-scoped like browser tabs (active per worktree for unqualifi
The prose directs agents to use Orca emulator commands for simulator control. This is safer than raw tools, but still controls local emulator state.
Medium
Ruby/shell backtick execution
```sh
The emulator command block lists actions such as attach, tap, type, gesture, exec, and kill. These are external device-control operations with local side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/stablyai-orca-cli/audits/3?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/stablyai-orca-cli/security.svg)](https://skillstore.io/skills/stablyai-orca-cli?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/stablyai-orca-cli?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/stablyai-orca-cli/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/stablyai-orca-cli.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

stablyai. (2026). orca-cli security audit report (audit version 3) [Author version unspecified]. Skillstore. https://skillstore.io/skills/stablyai-orca-cli/audits/3

BibTeX citation

@techreport{stablyai-stablyai-orca-cli-2026, author = {stablyai}, title = {orca-cli security audit report (audit version 3)}, institution = {Skillstore}, year = {2026}, number = {3}, url = {https://skillstore.io/skills/stablyai-orca-cli/audits/3}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "orca-cli security audit report (audit version 3)" version: "unspecified" type: report authors: - name: "stablyai" date-released: "2026-07-09" url: "https://skillstore.io/skills/stablyai-orca-cli/audits/3" identifiers: - type: other value: "skillstore:stablyai-orca-cli:audit:3" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
55
Architecture
85
Maintainability
87
Content
65
Community
83
Spec Compliance

What You Can Build

Hand Off Coding Work

Create a clean Orca worktree, start an agent, and pass a focused task brief with the right lineage.

Inspect Active Agent Sessions

List terminals, read recent output, wait for idle state, and send the next prompt only when appropriate.

Automate Orca Workspace Tasks

Create scheduled prompts for repo reviews, issue triage, or workspace summaries with clear provider choices.

Try These Prompts

Check Orca State
Use Orca CLI to check whether Orca is running, then list my active worktrees and terminals. Summarize what is available.
Create a Handoff Worktree
Create an independent Orca worktree for this task and start Codex there. Send a concise task brief and report the new worktree details.
Review Terminal Progress
Find the active Orca terminal, read its latest output, wait for idle state if needed, and tell me whether it needs a follow-up prompt.
Coordinate Browser and Automation Work
Use Orca CLI to inspect embedded browser tabs and scheduled automations for this workspace. Recommend the narrowest safe next command for each surface.

Best Practices

  • Run a status check before choosing worktree, terminal, automation, browser, or emulator commands.
  • Use JSON output and the narrowest Orca selector that matches the requested scope.
  • Read terminal or browser state before sending input unless the next action is explicit.

Avoid

  • Using raw git worktree, Playwright, simctl, or ad hoc terminal control when Orca state is required.
  • Sending terminal input, browser eval, cookie reads, uploads, or emulator exec commands without explicit user intent.
  • Monitoring a full handoff after ownership has moved to another agent or worktree.

Frequently Asked Questions

What does this skill control?
It controls Orca-managed worktrees, terminals, repos, automations, embedded browser tabs, and emulator surfaces through Orca CLI commands.
Does it require Orca?
Yes. Most workflows require the Orca CLI and a running Orca app or Orca-managed workspace.
Can it start other AI agents?
Yes. It documents how to create Orca terminals or worktrees that launch Codex, Claude, or Claude Code sessions.
Can it control normal browser windows?
No. Browser commands are for Orca embedded tabs. External browsers or desktop UI need other tools.
Is it safe for automated use?
Use caution. It can run commands, send terminal input, schedule prompts, and control browser or emulator state.
When should I use another skill?
Use orchestration or emulator companion skills when you need advanced task coordination or detailed mobile simulator control.

Developer Details

Author

stablyai

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Ref

3e4b6c31a74a3bd1a291c98cf585d720cb9fbc88

Maintenance freshness

7/18/2026

Usage

3 downloads · 0 views

File structure

📄 SKILL.md

More from stablyai

View all
View all