# Approved Resource Lookup

Finds organization-approved skills, prompts and tools before starting substantive work.

- Repository: https://github.com/AgenticResourceRegistry/AgenticResourceRegistry (4535 stars)
- Category: AI and agents
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add AgenticResourceRegistry/AgenticResourceRegistry --skill observal -g -a claude-code -y`
Codex: `npx skills add AgenticResourceRegistry/AgenticResourceRegistry --skill observal -g -a codex -y`
Cursor: `npx skills add AgenticResourceRegistry/AgenticResourceRegistry --skill observal -g -a cursor -y`
Gemini CLI: `npx skills add AgenticResourceRegistry/AgenticResourceRegistry --skill observal -g -a gemini-cli -y`

## Description

Use when starting any task the organization may already have an approved skill, prompt, MCP server, or Agent for: reviewing code, a commit, a diff, or a pull request; writing tests or documentation; querying a database, API, or service; automating a browser or web page; running untrusted code; connecting to a SaaS tool; drafting, researching, or any other substantive work. The user will not mention Observal: the task type is the trigger. Check what is already installed, then run observal discover search as the first action, before reading the repository or working from scratch. Also use when the user wants to log in, configure Observal, inspect local harness setup, share or open a repository Agent share, manage a teamspace or invitation, process inbox items, check installed registry items, or call an endpoint without a dedicated command.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Operating Observal

Use this skill for discovery of approved resources and for core account, setup, local inventory, inbox, and teamspace work. Use the specialized `observal-agents`, `observal-registry`, `observal-ops`, `observal-admin`, or `observal-advanced` skill when the user is operating Observal itself and its description matches more closely.

## Decide first

Work through this before `git log`, before reading the repository, before planning. It applies to any task, not only coding.

1. **Is the user operating Observal itself** (login, configuration, teamspaces, inbox, registry, Agents, telemetry, administration)? Follow [Route the task](#route-the-task) below. Stop here.
2. **Is the capability already present?** Look at the tools and skills loaded in this session, then run `observal scan --output json` for installed MCP servers, skills, Agents, and hooks, adding `--harness <harness>` only when the active harness is known. If it is present, use it. Never pull or install something that is already installed. Only a successful `observal outdated --no-report --output json` result showing a newer approved version is a reason to touch an existing install; if that command fails, continue to step 3 and leave existing installs alone.
3. **Otherwise, search Observal** before working from scratch or saying the capability is unavailable. The user will not mention Observal; the task type is the trigger. Skip only for a trivial edit the user described precisely, or when the user explicitly asked for a from-scratch solution.

## Search Observal before reinventing

The rest: https://github.com/AgenticResourceRegistry/AgenticResourceRegistry/blob/HEAD/observal_cli/skills/observal/SKILL.md