Installation

Version 0.1.0 is a public release. These instructions describe the intended install paths. This project has not observed a fresh-host installation on Codex or Claude.

Artifact paths on this page are relative to the root of the assembled public release. See Package reference for its exact topology.

Before you install

  1. Choose one host artifact.
  2. Confirm that the skill folder contains SKILL.md directly.
  3. Compare the artifact against SHA256SUMS.txt in the assembled kit.
  4. Preserve any existing skill with the same name before replacing it.

On Windows PowerShell, inspect a file hash with:

Get-FileHash -Algorithm SHA256 -LiteralPath path\to\file

The GL4SS drop-in patches are a separate maintainer handoff. Do not install them as an agent skill.

Install for Codex

Artifact:

codex/omniview-looking-glass/

Codex local skills live under:

$CODEX_HOME/skills/

When CODEX_HOME is not customized, the default is:

~/.codex/skills/

Place the complete omniview-looking-glass directory there. The resulting topology is:

$CODEX_HOME/
  skills/
    omniview-looking-glass/
      SKILL.md
      NOTICE.md
      LICENSE.md
      package-manifest.yaml
      agents/
      assets/
      evals/
      references/

Start a new Codex task. Restart the host if it does not refresh skill discovery automatically.

Check Codex discovery

Ask:

Use omniview-looking-glass to open a prompt-only view onto Uruk around 3200 BC at first light.

A useful discovery check must demonstrate that the installed skill was selected. A plausible historical answer by itself is not discovery evidence.

This release has no qualified Codex selection receipt yet. Treat discovery as awaiting fresh-host qualification unless the host exposes an observable selection record.

The package includes Codex-facing metadata that permits implicit selection. Qualify explicit selection before testing implicit selection.

Install for Claude

Artifact:

claude/omniview-looking-glass.zip

The ZIP contains exactly one top-level omniview-looking-glass folder with SKILL.md directly beneath it.

Claude skill upload

Anthropic’s current skill-upload flow requires Code execution and file creation:

  1. Open Customize > Skills.
  2. Select +, then Create skill.
  3. Select Upload a skill.
  4. Choose omniview-looking-glass.zip.
  5. Confirm that OmniView appears in the skill list and is enabled.

See Anthropic’s Use skills in Claude and How to create custom skills for the current host flow and ZIP requirements.

Claude Code project skill

For a project-local Claude Code installation, extract or copy the skill folder so the project contains:

.claude/
  skills/
    omniview-looking-glass/
      SKILL.md
      NOTICE.md
      LICENSE.md
      package-manifest.yaml
      assets/
      evals/
      references/

Claude’s current documentation identifies .claude/skills/<name>/SKILL.md as the project skill location. Start a new Claude Code session, then invoke the skill explicitly before testing automatic selection.

Check Claude discovery

Ask:

Use OmniView to open a prompt-only view onto Uruk around 3200 BC at first light.

For Claude Code, you may also inspect the available custom commands or skills and invoke the installed name explicitly if the host exposes it that way.

First-value acceptance check

Use this exact request:

Open a prompt-only view at Point Nemo in AD 1500 at 23:30 local time. The year is all I know.

The response should:

This is a behavioral acceptance check. It does not prove installation unless the host also shows that the installed skill supplied the behavior.

Update or remove

Before updating, move the existing omniview-looking-glass folder or ZIP record to a clearly named backup. Install the replacement as a complete unit; do not mix files from different versions.

To remove a local installation, move the complete skill folder out of the host’s skill directory and start a new session. In Claude’s uploaded-skill interface, disable or remove the skill through Customize > Skills.

If discovery or behavior is unclear, stop before replacing more files and use Troubleshooting.