observal-admin
Administers Observal users, settings, diagnostics, review queues, security events, audit logs, SAML, SCIM, local server services, upgrades, rollback, and database migrations. Use when the user needs privileged governance, submission decisions, identity configuration, security investigation, or server operations.
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 2987
- Лиценз
- Apache-2.0
- Последна проверка на записа
- 22.09.2026 г.
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add Observal/ObservalСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
Administering Observal
Core administration requires an admin role. Review actions also work for authorized global reviewers and teamspace owners or reviewers.
Execution contract
- Execute commands with a 60 second timeout, except documented long-running server and migration operations.
- Use machine output by default: add
--output jsonwhenever supported. Parse list results fromitemsand pagination fields. - Run
--helpbefore acting when a path, role requirement, confirmation flag, or destination option is uncertain. - Read current state before privileged mutations. Use the smallest required authority.
- Supply
--forceor another documented confirmation flag for noninteractive destructive operations. - Verify review decisions, role changes, identity settings, server upgrades, rollback, and imports.
- Never repeat generated passwords, SCIM tokens, certificates, submitted headers, database URLs, environment values, or sensitive audit content.
- Fail openly. Do not bypass the CLI through direct database changes or hand-written migration SQL.
- Never blindly retry privileged mutations. Read resulting state after an uncertain failure.
Choose the workflow
| User intent | Read |
|---|---|
| Users, settings, diagnostics, reviews, security, audit, SAML, or SCIM | Governance and identity |
| Local services, versions, upgrades, rollback, reset, or data migration | Server operations |
Read the selected reference completely before executing.
Safety rules
- Permission denial is a result, not a reason to escalate automatically. Report the required role.
- Review only the returned UUID requested by the user. Never act on table position or an unrelated queue item.
- Treat one-time password and token responses as secrets from the moment they are returned.
- Export and import destinations must be explicit. Validate an archive before import.
- Use the project's migration commands. Never replace them with ad hoc SQL.
- A server command is successful only when the final status confirms the requested service or version state.
Completion
Report the affected resource by safe identifier, resulting state, request ID for failures, and any required follow-up. Redact secret values even when the command returned them successfully.