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.
Instalar con mi Agente
Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.
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.Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.
Recursos legibles por agentes
Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.
Pruébalo
Usando "groundcover-cli". Summarize a service incident after reviewing its telemetry.
Resultado esperado:
- 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.
Usando "groundcover-cli". Review a proposed dashboard change before applying it.
Resultado esperado:
- 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.
Auditoría de seguridad
SeguroAll 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.
Elementos de revisión de capacidades (3)
Estas son capacidades locales reales que pueden esperarse para esta habilidad, por lo que requieren revisión, pero no se cuentan como comportamiento malicioso confirmado.
Factores de riesgo
⚙️ Comandos externos (50)
🌐 Acceso a red (5)
📁 Acceso al sistema de archivos (22)
🔑 Variables de entorno (4)
Compartir y citar este informe
Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.
Copiar enlace del informe
https://skillstore.io/skills/paymog-groundcover-cli/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportInsignia Markdown
[](https://skillstore.io/skills/paymog-groundcover-cli?utm_source=security_passport_badge)Insignia 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>Tarjeta para insertar
<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>Citas académicas (APA · BibTeX · CFF)
Cita APA
paymog. (2026). groundcover-cli security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/paymog-groundcover-cli/audits/1Cita 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"
Puntuación de Skillstore
Por qué esta puntuación Confianza de la evidencia: MedioLo que puedes crear
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.
Prueba estos prompts
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.
Mejores prácticas
- 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.
Evitar
- 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.