Skip to content
Agentmart
Submit a tool

orca-context

Resolve ambiguous recent-work references by identifying the actual artifact, app, or screen context first.

Skill by henryvn27

IndexedMIT★ 5
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/henryvn27-orca-context

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Resolve ambiguous recent-work references by identifying the actual artifact, app, or screen context first.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/orca-context

What's inside

Skill name
orca-context
Description
Resolve ambiguous recent-work references by identifying the actual artifact, app, or screen context first.
License
MIT
Instructions
56 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# ORCA Framework Context

## What This Skill Is

An ambiguity-resolution workflow for cases where the user means a concrete thing but has not named it precisely.

## Trigger

Use when the request points at recent or visible context rather than a clearly named artifact.

## Do Not Trigger

Do not use when the target file, app, issue, or artifact is already explicit.

## Required Inputs

- ambiguous reference

## Optional Inputs

- recent artifacts
- active harness
- screen or history tooling when available

## Exact Workflow

1. Check repo-local and textual evidence first.
2. If Chronicle or equivalent screen-history tooling is available, confirm it is currently running and that the capture timestamp is fresh before trusting it.
3. Use screen or history tools only to identify the likely target.
4. Use OCR only as a search aid.
5. Upgrade quickly to the stronger source of truth once identified.
6. State freshness and confidence.
7. Route into the correct next ORCA command.

## Expected Outputs

- resolved target
- evidence note
- next-step recommendation

## Quality Bar

The workflow should reduce ambiguity without treating OCR or screenshot hints as stronger than the real artifact.

## Common Failure Modes

- over-relying on screen evidence
- failing to say when confidence is weak
- continuing the whole task from screenshots instead of pivoting to the artifact itself
- treating stale screen history as if it reflects the current target

## Relationship To Other ORCA Framework Skills And Commands

Pairs with `orca-controller-mode`, `orca-runtime-adaptation`, and `orca-explain`.

From henryvn27/orca-framework, MIT.

More from henryvn27/orca-framework

Signals

Stars
5
Forks
1
Open issues
0
Last commit (this folder)
Jun 3, 2026 (4 months ago)
Last release
Jul 18, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from henryvn27

Cite this page

orca-context skill. Agent Mart. https://agentmart.dev/skills/henryvn27-orca-context (last updated 2026-10-24)