observal
Finds and loads the organization's approved resources for the task at hand, and operates the Observal CLI for authentication, configuration, setup diagnosis, teamspaces, inbox work, scans, update checks, and API access. Use when starting any substantive coding task, including code or security reviews, writing tests or documentation, querying a database or service, or running untrusted code: run observal discover search first and load an approved match before working from scratch or saying a capa
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 2987
- Лиценз
- Apache-2.0
- Последна проверка на записа
- 22.09.2026 г.
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add Observal/ObservalСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
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.
- Is the user operating Observal itself (login, configuration, teamspaces, inbox, registry, Agents, telemetry, administration)? Follow Route the task below. Stop here.
- Is the capability already present? Look at the tools and skills loaded in this session, then run
observal scan --output jsonfor 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 successfulobserval outdated --no-report --output jsonresult 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. - 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.