Profile My skills Saved My plugins Edit profile Submit a skill

all publishers

paymog

@paymog source repo

3 published skills

  1. ▌
    Blacksmith CLI · paymog
    Invoke the `bs` CLI to query a blacksmith.sh org's dashboard backend — CI/Actions usage and metrics (core-usage, jobs, workflows, runs, docker builds, sticky disks), monitoring (failure histograms, repo/workflow/job/step health, rules), billing (invoices, unpaid, payment method), settings (codesmith/MCP/skills, SSH, log ingestion, max timeout, branch protection), integrations (slack, linear), team, and assistant sessions. Blacksmith has NO public API or API keys, so `bs` replays the private dashboard backend using imported browser session cookies. Use whenever a task needs data from blacksmith.sh, such as "what's my blacksmith core usage", "how many vCPUs am I using", "show CI job metrics for repo X", "which workflows are failing", "blacksmith invoice amount", "list my blacksmith runner types", "is autofix enabled", "blacksmith team members". Covers cookie auth import, org resolution, the --query/--body flags, and how to regenerate the command catalog from a HAR.
    4 installs
  2. ▌
    Cloudzero CLI · paymog
    Invoke the `cloudzero` CLI to drive the CloudZero API — billing costs/dimensions, billing connections (AWS/Azure/GCP/AnyCost), budgets, CostFormation definition versions/namespaces/publish-jobs, insights + comments, optimization recommendations + comments + recommendation types, roles + permission sets, views, engineering events, telemetry (allocation + unit metric streams), and internal dashboard endpoints (cost data over time, grouped costs, clusters, groups, SSO integrations, notifications, Looker reports, realized savings). Uses the public key-authenticated API (hand-crafted commands) plus internal dashboard (Bearer JWT) commands generated from captured HARs, hand-curated internal endpoints, and a `raw` escape hatch for any un-codified path. Use whenever a task needs CloudZero data or actions, such as "list our insights", "get billing costs", "create a budget", "send telemetry", or "list recommendations".
    4 installs
  3. ▌
    Groundcover CLI · paymog
    Invoke the `groundcover` Go CLI to manage Groundcover resources (dashboards, monitors, silences, connected apps, notification routes, API keys, policies, integrations, pipelines, workflows) AND to answer production observability questions by querying logs, traces, metrics, k8s inventory, and k8s events. Use whenever a task needs an authenticated call against the Groundcover API or whenever the user is debugging a prod issue and asks things like "why is X erroring in prod", "show me logs for service Y", "what's the p99 latency on Z", "what pods are crashlooping", "search traces for slow requests", "any k8s events for namespace N", "is service S receiving traffic", "list groundcover monitors", "create a silence", "update notification route", "hit a groundcover endpoint". Covers required env vars, the SDK-backed vs raw command split, and concrete request-body templates for logs/traces/metrics/k8s so the CLI can be driven from anywhere.
    4 installs