groundcover-cli
Investigate Groundcover Production Issues
Production investigations require correlated logs, traces, metrics, and Kubernetes context. This skill provides Groundcover CLI workflows for querying telemetry and managing observability resources.
Установить с помощью моего Агента
Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.
Review the Skillstore skill "groundcover-cli" from https://skillstore.io/skills/paymog-groundcover-cli.md and its manifest at https://skillstore.io/api/skills/paymog-groundcover-cli/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.
Ресурсы для AI-агентов
Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.
Протестировать
Использование «groundcover-cli». Summarize a service incident after reviewing its telemetry.
Ожидаемый результат:
- Illustrative summary: Error logs show repeated upstream timeouts during the selected window.
- Slow traces overlap with elevated latency metrics.
- The available evidence suggests an upstream dependency issue, but does not establish the root cause.
- No production settings were changed.
Использование «groundcover-cli». Review a proposed dashboard change before applying it.
Ожидаемый результат:
- Illustrative review: Preserve the current revision and existing widgets.
- Place stat panels at the top level and check every panel against the 24-column grid.
- Validate each metric expression with a range query.
- The change remains unapplied pending approval; visual rendering has not been verified.
Аудит безопасности
БезопасноAll 244 static findings were adjudicated; three overlapping detections confirm one unverified remote-installer execution risk. Other detections concern Markdown, documented authentication, standard input, or application identifiers. No evidence found of prompt injection, covert exfiltration, or malicious intent in the supplied skill text; external implementations were not reviewed.
Пункты проверки возможностей (3)
Это реальные локальные возможности, которые могут ожидаться для этого навыка, поэтому они требуют проверки, но не считаются подтверждённым вредоносным поведением.
Факторы риска
⚙️ Внешние команды (50)
🌐 Доступ к сети (5)
📁 Доступ к файловой системе (22)
🔑 Переменные окружения (4)
Поделиться и цитировать этот отчет
Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.
Копировать ссылку на отчёт
https://skillstore.io/skills/paymog-groundcover-cli/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportЗначок Markdown
[](https://skillstore.io/skills/paymog-groundcover-cli?utm_source=security_passport_badge)Значок HTML
<a href="https://skillstore.io/skills/paymog-groundcover-cli?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/paymog-groundcover-cli/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Встраиваемая карточка
<iframe src="https://skillstore.io/embed/skills/paymog-groundcover-cli.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Академические ссылки (APA · BibTeX · CFF)
Цитата APA
paymog. (2026). groundcover-cli security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/paymog-groundcover-cli/audits/1Цитата BibTeX
@techreport{paymog-paymog-groundcover-cli-2026,
author = {paymog},
title = {groundcover-cli security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/paymog-groundcover-cli/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "groundcover-cli security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "paymog"
date-released: "2026-10-19"
url: "https://skillstore.io/skills/paymog-groundcover-cli/audits/1"
identifiers:
- type: other
value: "skillstore:paymog-groundcover-cli:audit:1"
description: "Skillstore immutable audit report identifier"
Оценка Skillstore
Почему такая оценка Достоверность доказательств: СреднийЧто вы можете построить
Investigate Production Errors
Correlate service error logs, slow traces, latency metrics, and Kubernetes warnings within a defined incident window.
Validate Service Telemetry
Discover available metrics and labels, then compare request latency and error patterns for an application service.
Maintain Observability Dashboards
Inspect dashboard presets, prepare revision-aware changes, and validate queries and layout constraints before deployment.
Попробуйте эти промпты
Explain how to check my Groundcover profile and authentication status without printing tokens. Do not install software or create credentials.
Using my authorized profile, inspect error logs for service api over the last hour. Summarize recurring errors without exposing sensitive log values.
Investigate api latency over the last 30 minutes using traces, PromQL range queries, and Kubernetes warnings. Separate observations from hypotheses; make no changes.
Inspect dashboard <uuid> and propose p99 panels. Preserve its revision and existing widgets. Validate queries and layout; request approval before applying changes.
Лучшие практики
- Use authorized, least-privilege profiles and confirm the tenant and destination before querying or changing resources.
- Use narrow UTC windows and discriminating filters; remove secrets and personal data from shared findings.
- Preserve current revisions and complete settings; obtain approval before writes, alert silences, or software installation.
Избегать
- Executing the remote installer without reviewing it and verifying a pinned artifact.
- Printing API tokens or copying unredacted production logs into reports.
- Silencing alerts or overwriting production dashboards without explicit approval and a recovery plan.