connect-splunk-observability-cloud
/connect-splunk-observability-cloud
Otwiera lokalną kartę Splunk Observability Studio Cloud, w której użytkownik wpisuje URL i token dostępu do organizacji Splunk Observability Cloud poza kontekstem agenta.
- Autor
- signalfx ↗
- Repozytorium
- obstudio ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 27.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Otwiera lokalną kartę Splunk Observability Studio Cloud, w której użytkownik wpisuje URL i token dostępu do organizacji Splunk Observability Cloud poza kontekstem agenta.
Oryginalny opis (EN)
Open the already-running local Splunk Observability Studio Cloud tab so a user can connect an existing or newly ready Splunk Observability Cloud organization by entering its URL and access token outside agent context. Use when a user asks to connect, configure, or provide credentials for Splunk Observability Cloud, Splunk O11y, or SignalFx outside the Splunk Observability Studio IDE extension. Do not use this skill to create a Free Edition account.
Jak działa
- Guardrails
- Open the existing Cloud tab
Podgląd SKILL.md
--- name: connect-splunk-observability-cloud description: >- Open the already-running local Splunk Observability Studio Cloud tab so a user can connect an existing or newly ready Splunk Observability Cloud organization by entering its URL and access token outside agent context. Use when a user asks to connect, configure, or provide credentials for Splunk Observability Cloud, Splunk O11y, or SignalFx outside the Splunk Observability Studio IDE extension. Do not use this skill to create a Free Edition account. allowed-tools: mcp__obstudio__observer_status, mcp__obstudio__observer_splunk_connection_realm --- # Connect Splunk Observability Cloud Hand credential entry to the existing local Splunk Observability Studio Cloud UI. The agent must never collect or transmit the access token itself. ## Guardrails - Open the Cloud UI only after the user explicitly asks to connect or configure an organization. - Do not use this skill for signup. Use `$create-splunk-free-account` when the user still needs a Free Edition account. - Never ask the user to paste the Observability Cloud URL or access token into agent chat. If either value was already pasted, do not repeat it or pass it onward. - Never place an access token in an MCP or other tool argument, native agent form, shell command or process argument, environment assignment, URL path, query, or fragment, log, or telemetry. Do not call `observer_splunk_metrics_export_configure` with a raw token obtained through model context. - Do not call `observer_splunk_free_account_region_detect` or `observer_splunk_free_account_create` during this connection workflow. - Do not start, stop, or restart Splunk Observability Studio or launch another Splunk Observability Studio process. ## Open the existing Cloud tab 1. Call `observer_status` once with no arguments and read only `endpoints.rest`. 2. Require an `http` URL whose host is loopback. Normalize a wildcard listener host from `0.0.0.0` to `127.0.0.1` or from `::` to `::1`. Reject a non-loopback host for this local credential handoff. Remove any credentials, path, query, or fragment from the returned URL. 3. Append `/?tab=cloud` to the normalized origin. The normal standalone result is exactly: ```text http://127.0.0.1:17900/?tab=cloud ``` Use the port already reported by the running Splunk Observability Studio. Never allocate, probe for, or choose a new dynamic port. 4. When the current client exposes a host-provided browser or open-URL capability, use it to open the Cloud-tab URL. Do not shell out to platform-specific commands such as `open`, `xdg-open`, or `start`. 5. If no host-provided browser capability exists, provide the Cloud-tab URL as a clickable fallback. Do not launch an operating-system browser without the user's explicit approval. 6. Tell the user to enter both **Realm or Observability Cloud URL** and **Access token** directly in that local UI, then select **Connect**. Stop and wait while the user completes the form. 7. In the same handoff, explicitly state: `This connection applies to the current running standalone Splunk Observability Studio process and must be entered again after Splunk Observability Studio restarts.` 8. Also state that opening the tab only presents the credential-entry surface and does not mean the organization is connected. Connection success requires a later local Cloud UI or Splunk Observability Studio backend result. If `observer_status` is unavailable, `endpoints.rest` is missing or invalid, or the Cloud tab cannot be opened, explain the specific limitation and stop. An inconclusive browser render is not proof that Splunk Observability Studio is unhealthy. Do not claim the organization is connected merely because the page opened. If the user later asks to confirm the configuration, call `observer_splunk_connection_realm` with no arguments. A non-empty realm proves only that Splunk Observability Studio has a consistent local connection configuration; it does not prove remote token validity or that export is enabled. Never request the token to investigate an empty result.
Pliki w paczce (2)
- SKILL.md 4 KB
- agents/openai.yaml 1 KB
Wersje
W bazie nie ma innych skilli o nazwie connect-splunk-observability-cloud.
Identyczna treść występuje jeszcze w 1 innych folderach na GitHubie. Tu pokazujemy jedną, najlepiej ocenioną kopię.
Migawka bazy z 13.11.2026 · wersja paczki 3a14b9eab3ce (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100create-splunk-free-account
Składa po zgodzie użytkownika zgłoszenie rejestracji w Splunk Observability Cloud Free Edition w obsługiwanym regionie przez bezprzeglądarkowy backend MCP Splunk Observability Studio. - 100splunk-dashboard
Generuje Terraform dla dashboardów Splunk Observability Cloud z raportu otel-audit, grupując metryki w gotowe do zastosowania panele. - 100splunk
Obsługuje Splunk Enterprise i Splunk Cloud jako platformę logów i metryk: SPL, architekturę rozproszoną, ingest, dashboardy, alerty i koszty licencji. - 90splunk-app-conventions
Sprawdza, waliduje i wydaje aplikacje Splunk oraz skrypty wdrożeniowe zgodnie z konwencjami repozytorium. - 100superman-splunk
Pomaga w pracy ze Splunkiem: pisze zapytania SPL, konfiguruje indeksatory i dashboardy oraz diagnozuje wydajność. - 100manage-sc4s-splunk-metadata
Zarządza metadanymi Splunk w SC4S przez MCP: bezpiecznie sprawdza, dodaje, zmienia, usuwa i czyści nadpisania indeksu, źródła, sourcetype, hosta i sc4s_template w splunk_metadata.csv.