본문으로 건너뛰기
cccskills
무료GitHub에 공개

observal-registry

Searches, recommends, bulk-submits, installs, forks, edits, versions, archives, restores, transfers, and manages co-authors for Observal MCP servers, skills, hooks, prompts, sandboxes, and registered remote A2A agents. Use when the user wants to find components, publish one or many they control, install them into a harness, or manage their lifecycle.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Observal/Observal
연동 도구Gmail
설치 방법 보기

포함된 파일(4)

  • SKILL.md3.7 KB
  • references/component-submission.md6.5 KB
  • references/discovery-and-installation.md5.7 KB
  • references/registry-lifecycle.md10.0 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Managing Registry Components

Execution contract

  1. Execute commands with a 60 second timeout.
  2. Use machine output by default: add --output json whenever supported. Parse list results from items and pagination fields.
  3. Run the leaf command's --help when any path, flag, enum, or payload shape is uncertain.
  4. Supply all required inputs and confirmation flags. Do not leave an agent waiting at a prompt.
  5. Reuse returned UUIDs and qualified_name values. Never automate with row numbers or ambiguous bare names.
  6. Verify installs, submissions, edits, versions, ownership changes, and lifecycle transitions.
  7. Submit or modify only components the user owns or is authorized to manage.
  8. Never expose environment values, headers, tokens, private source data, or submitted secret fields.
  9. Mutations are sent once. After an uncertain transport failure, read component state before retrying.
  10. Authentication is optional for approved public content when the server setting deployment.public_registry_enabled is enabled; it is disabled by default on self-hosted deployments. Public list, show, install, and prompt render commands use https://public.observal.io by default. Authenticate before submitting, editing, reviewing, rating, or accessing private team content.

Choose the workflow

User intentRead
Find, inspect, recommend, or install componentsDiscovery and installation
Submit one component or a mixed bulk file, or register a remote A2A agentComponent submission
Fork, edit, version, archive, restore, transfer, or manage co-authorsRegistry lifecycle

Read only the selected reference, and read it completely before executing.

Registry rules

  • Search with the user's natural-language terms, then narrow by type, namespace, team, harness, or category only when useful.
  • Open-ended requests such as "what am I missing?" use personalized recommendations before keyword search.
  • personalized: false means popularity fallback, not a personal recommendation.
  • Team members can see authorized private teamspace items. Use TEAM_HANDLE/ITEM_SLUG for direct references.
  • Draft, pending, rejected, and approved items have different edit behavior. Read status before mutating.
  • Forks copy only currently approved sources and approved releases into independent drafts. Do not disclose source identity if the API reports forked_from.available: false.
  • A successful submit can still be pending review. Report the returned status instead of saying it is published.
  • Bulk files are structurally validated before mutation. Inspect every per-entry result and verify uncertain retries by canonical identity.
  • Prefer an existing installed dependency or native CLI path. Do not invent wrappers or telemetry variables.

Completion

Report component type, canonical identity, version, status, target harness or scope when applicable, warnings, and any review or setup step still required.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

observal

무료

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Observal/Observal4.6천2026년 10월 19일 업데이트

observal-admin

무료

Administers Observal users, settings, diagnostics, review queues, security events, audit logs, SAML, SCIM, the local Observal server, its upgrades and rollback, and its own PostgreSQL and ClickHouse schema migrations. Use when the user needs privileged governance, submission decisions, identity configuration, security investigation, or Observal server operations. Not for querying a database or any work outside Observal administration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Observal/Observal4.6천2026년 10월 19일 업데이트

observal-advanced

무료

Recovers Observal session ingestion, manages CLI upgrades, downgrades and rollback, and performs explicit local Agent fallback when the server is unavailable. Use when the user asks to reconcile missed sessions, repair CLI version state, or continue locally after a confirmed connection or configuration failure.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Observal/Observal4.6천2026년 10월 19일 업데이트

observal-agents

무료

Creates, forks, authors, validates, publishes, updates, versions, pulls, archives, restores, transfers, and manages co-authors for Observal Agents. Use when the user wants to build or install an Agent, change an Agent definition, publish a draft, release a version, or manage Agent ownership.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Observal/Observal4.6천2026년 10월 19일 업데이트

observal-ops

무료

Inspects Observal traces, sessions, rankings, feedback, telemetry health, logs, and Agent insight reports. Use when the user wants operational evidence, current activity, telemetry diagnosis, ratings, report generation, regression analysis, or recommendations grounded in Agent usage.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Observal/Observal4.6천2026년 10월 19일 업데이트

release

무료

Cut and maintain Observal release branches, prepare alpha, beta, RC, stable, and patch releases, backport merged main PRs, inspect release status, verify published artifacts, and recover failed release operations. Use for Observal maintainer release tasks and release-process changes, not for installing or upgrading an existing Observal deployment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Observal/Observal4.6천2026년 10월 19일 업데이트

Observal의 스킬 모두 보기

이 스킬의 문제 신고