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.
Mit meinem Agent installieren
Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.
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.Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.
Agent-lesbare Ressourcen
Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.
Testen
„groundcover-cli“ wird verwendet. Summarize a service incident after reviewing its telemetry.
Erwartetes Ergebnis:
- 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“ wird verwendet. Review a proposed dashboard change before applying it.
Erwartetes Ergebnis:
- 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.
Sicherheitsaudit
SicherAll 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.
Elemente der Fähigkeitsprüfung (3)
Dies sind echte lokale Fähigkeiten, die für diese Fähigkeit erwartet werden können; daher müssen sie überprüft werden, werden jedoch nicht als bestätigtes bösartiges Verhalten gezählt.
Risikofaktoren
⚙️ Externe Befehle (50)
🌐 Netzwerkzugriff (5)
📁 Dateisystemzugriff (22)
🔑 Umgebungsvariablen (4)
Diesen Bericht teilen & zitieren
Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.
Berichtslink kopieren
https://skillstore.io/skills/paymog-groundcover-cli/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown-Badge
[](https://skillstore.io/skills/paymog-groundcover-cli?utm_source=security_passport_badge)HTML-Badge
<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>Einbettungskarte
<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>Wissenschaftliche Zitate (APA · BibTeX · CFF)
APA-Zitat
paymog. (2026). groundcover-cli security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/paymog-groundcover-cli/audits/1BibTeX-Zitat
@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-Score
Warum dieser Score Evidenzvertrauen: MittelWas Sie erstellen können
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.
Diese Prompts ausprobieren
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.
Bewährte Praktiken
- 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.
Vermeiden
- 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.