sandipb
- 5 skills
- 0 followers
- 7 hours ago last updated
- ▌ Tech Blog · sandipb bundleCompose, edit, or review reader-oriented technical articles from supplied authoritative context. Use for technical blog posts and explanatory articles that may need stronger restructuring, pacing, explanation, or information selection than work-oriented documentation permits.
- ▌ Grafana Loki · sandipb bundleUse this skill for any task involving Grafana Loki — writing or debugging LogQL queries, running logcli commands, querying logs via Loki's HTTP API, investigating errors or performance issues in logs stored in Loki, troubleshooting slow or timed-out Loki queries, cardinality problems, and Loki cluster configuration. Always use this skill when the user wants to find, filter, or analyze logs and the context implies Loki (e.g., they mention logcli, LogQL, a Loki endpoint URL, or X-Scope-OrgID / tenant ID). Also use when the user asks about log streams, label selectors like {app="..."} or {namespace="..."}, line filters, log parsers (json/logfmt), or metric queries over logs (rate, count_over_time, quantile_over_time). Triggers on: "/grafana-loki", "loki", "logql", "logcli", "log query", "query logs", "grafana loki", "label cardinality", "log streams", "loki endpoint", "orgid", "X-Scope-OrgID".
- ▌ Technical Docs · sandipb bundleCompose, edit, or review work-oriented technical documentation from supplied authoritative context while preserving technical meaning and distinct information. Use for READMEs, runbooks, procedures, reports, design documents, API documentation, PR descriptions, commit messages, warnings, and code comments.
- ▌ Fireworks Billing · sandipb bundleExport and summarize Fireworks AI billing usage by date range, model, and usage type with the official firectl CLI. Use for Fireworks billing metrics, token usage, accelerator usage, or spend-related investigation. This reports usage rather than currency charges.
- ▌ Technical Writing · sandipb bundleCompose, edit, or review concise technical prose while preserving supported claims, terminology, certainty, conditions, causality, commands, identifiers, and values. Use directly for technical notes, comments, issues, explanations, and other small technical-writing tasks; use technical-docs or tech-blog for substantive workflows.