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.
Installer avec mon Agent
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
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.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Ressources lisibles par les agents
Utilisez ces liens lorsquâun Agent IA, un crawler ou un script a besoin dâun contexte propre au lieu de lire toute la page.
Tester
Utilisation de « groundcover-cli ». Summarize a service incident after reviewing its telemetry.
Résultat attendu:
- 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.
Utilisation de « groundcover-cli ». Review a proposed dashboard change before applying it.
Résultat attendu:
- 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.
Audit de sécurité
SûrAll 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.
ĂlĂ©ments dâĂ©valuation des capacitĂ©s (3)
Il sâagit de capacitĂ©s locales rĂ©elles qui peuvent ĂȘtre attendues pour cette compĂ©tence ; elles nĂ©cessitent donc un examen, mais ne sont pas comptabilisĂ©es comme comportement malveillant confirmĂ©.
Facteurs de risque
âïž Commandes externes (50)
đ AccĂšs rĂ©seau (5)
đ AccĂšs au systĂšme de fichiers (22)
đ Variables dâenvironnement (4)
Partager et citer ce rapport
Partagez le rapport dâĂ©valuation versionnĂ©, le badge neutre, la carte intĂ©grable et les citations. Skillstore prĂ©sente les preuves sans dĂ©cider si ce Skill est sĂ»r.
Copier le lien du rapport
https://skillstore.io/skills/paymog-groundcover-cli/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/paymog-groundcover-cli?utm_source=security_passport_badge)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>Carte intégrable
<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>Citations académiques (APA · BibTeX · CFF)
Citation APA
paymog. (2026). groundcover-cli security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/paymog-groundcover-cli/audits/1Citation 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"
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: MoyenCe que vous pouvez créer
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.
Essayez ces 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.
Bonnes pratiques
- 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.
Ăviter
- 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.