Agent skill

Loki Logs

A skill your agent uses when investigating production behaviour from logs — a 500/error in prod, a failing or stuck Celery task, tracing one request/traceid/user across services, or confirming a…

MITAuto-check: notesDevOps & Cloud

Install Loki Logs

skills CLI

$ npx skills add letsrevel/revel-backend --skill loki-logs -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install letsrevel/revel-backend loki-logs --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/letsrevel/revel-backend.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/loki-logs .claude/skills/loki-logs && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "loki-logs" agent skill from https://github.com/letsrevel/revel-backend/tree/main/.claude/skills/loki-logs into .claude/skills/loki-logs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loki-logs", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/letsrevel/revel-backend/tree/main/.claude/skills/loki-logs

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add letsrevel/revel-backend --skill loki-logs -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install letsrevel/revel-backend loki-logs --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/letsrevel/revel-backend.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/loki-logs .agents/skills/loki-logs && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "loki-logs" agent skill from https://github.com/letsrevel/revel-backend/tree/main/.claude/skills/loki-logs into .agents/skills/loki-logs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loki-logs", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add letsrevel/revel-backend --skill loki-logs -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install letsrevel/revel-backend loki-logs --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/letsrevel/revel-backend.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/loki-logs .cursor/skills/loki-logs && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "loki-logs" agent skill from https://github.com/letsrevel/revel-backend/tree/main/.claude/skills/loki-logs into .cursor/skills/loki-logs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loki-logs", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/letsrevel/revel-backend.git --path .claude/skills/loki-logs

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add letsrevel/revel-backend --skill loki-logs -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install letsrevel/revel-backend loki-logs --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/letsrevel/revel-backend.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/loki-logs .gemini/skills/loki-logs && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "loki-logs" agent skill from https://github.com/letsrevel/revel-backend/tree/main/.claude/skills/loki-logs into .gemini/skills/loki-logs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loki-logs", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install letsrevel/revel-backend loki-logs

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add letsrevel/revel-backend --skill loki-logs -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/letsrevel/revel-backend.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/loki-logs .github/skills/loki-logs && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "loki-logs" agent skill from https://github.com/letsrevel/revel-backend/tree/main/.claude/skills/loki-logs into .github/skills/loki-logs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loki-logs", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add letsrevel/revel-backend --skill loki-logs -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install letsrevel/revel-backend loki-logs --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/letsrevel/revel-backend.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/loki-logs .opencode/skills/loki-logs && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "loki-logs" agent skill from https://github.com/letsrevel/revel-backend/tree/main/.claude/skills/loki-logs into .opencode/skills/loki-logs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loki-logs", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: loki-logs
GitHub stars: 109
Token cost: ~918 tokens
SKILL.md length: 312 words
Files: 1
Skills in repo: 5
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when investigating production behaviour from logs — a 500/error in prod, a failing or stuck Celery task, tracing one request/traceid/user across services, or confirming a…

Works in 4 steps: Start broad: web --level error --since… → Grab the trace_id/request_id from the… → Re-query by that id with --forward to… → …
Investigating production behaviour from logs — a 500/error in prod
SKILL.md covers Tool, What you can filter on, Recipes and Workflow when debugging from a…, plus 1 more section
Calls python; needs GRAFANA_TOKEN

What it does

Loki Logs is an agent skill from letsrevel/revel-backend. Use when investigating production behaviour from logs — a 500/error in prod, a failing or stuck Celery task, tracing one request/traceid/user across services, or confirming a deploy's runtime effect. Pulls real Loki logs from the live stack (web, celerydefault, beat, telegram) via Grafana.

Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Background jobs and Monitoring and alerting. It works with Grafana, Telegram, Python and Django. The repository describes itself as: Open-source event management, ticketing and membership platform for communities, clubs, independent venues and independent artists. The licence is MIT.

When your agent uses it

Investigating production behaviour from logs — a 500/error in prod
Stuck Celery task
Tracing one request/traceid/user across services
Confirming a deploys runtime effect

Example prompts

“/loki-logs”

Requirements

Python 3
A credential in GRAFANA_TOKEN
Pre-approved tools (allowed-tools): Bash(python:*), Bash(.venv/bin/python:*), Read, Grep

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Start broad: web --level error --since to find the failure.
Grab the trace_id/request_id from the metadata line.
Re-query by that id with --forward to read the full request in order,
Use --print-query to inspect/borrow the LogQL; use --json when you need

What it can do on your machine

Read from SKILL.md and the folder at commit 8333099. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Bash(python:*)
- Bash(.venv/bin/python:*)
- Read
- Grep
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- GRAFANA_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Loki Logs loads about 918 tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 312 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~76
When it runs · the whole SKILL.md, loaded when a task matches: ~918

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:23

A_TOKEN` via decouple (from the project `.env` or the environment).

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from letsrevel/revel-backend at commit 8333099, republished under its MIT licence (© letsrevel). 312 words, ~918 tokens.

Download SKILL.mdSave it as .claude/skills/loki-logs/SKILL.md (or your agent's skills folder).

name: loki-logs
description: Use when investigating production behaviour from logs — a 500/error in prod, a failing or stuck Celery task, tracing one request/trace_id/user across services, or confirming a deploy's runtime effect. Pulls real Loki logs from the live stack (web, celery_default, beat, telegram) via Grafana.
allowed-tools: Bash(python:*), Bash(.venv/bin/python:*), Read, Grep

Loki Logs

Query the production logs from Loki, the live log store. Loki itself is not publicly reachable; the script asks Grafana (grafana.letsrevel.io) to proxy LogQL to its Loki datasource using a service-account token.

Tool

bash

.venv/bin/python scripts/loki_logs.py [SERVICE] [filters] [--since DUR] [-n LIMIT]

SERVICE is one of web, celery_default, beat, telegram (omit to search all). Default window is the last 1h, newest first, 100 lines. Run --help for the full flag list. Use the venv interpreter — the script imports python-decouple.

Auth: reads GRAFANA_TOKEN via decouple (from the project .env or the environment). If it errors with "GRAFANA_TOKEN is not set", it isn't configured yet — tell the user; do not guess.

What you can filter on

Kind	Flags	LogQL
Stream labels	`SERVICE`, `--level error` (repeatable), `--env production`	indexed, cheap
Line content	`--grep TEXT`, `--exclude TEXT`, `--regex RE` (all repeatable)	substring / regex
Request metadata	`--trace-id`, `--request-id`, `--user-id`, `--method`, `--path`, `--status-code`, `--ip`, `--user-agent`	structlog fields
Raw escape hatch	`--query '{service_name="web"} \| status_code="500"'`	any LogQL

Logs are structlog JSON; the displayed line is the event message, with a metadata line beneath it (suppress with --no-meta, get raw JSON with --json).

Recipes

bash

# Errors in the API in the last hour
.venv/bin/python scripts/loki_logs.py web --level error

# Follow one request end-to-end across every service
.venv/bin/python scripts/loki_logs.py --request-id <uuid> --since 6h --forward

# Celery failures mentioning a traceback, last day
.venv/bin/python scripts/loki_logs.py celery_default --since 1d --grep Traceback

# All 5xx responses, last 2h
.venv/bin/python scripts/loki_logs.py web --status-code 500 --since 2h

# Everything a user triggered
.venv/bin/python scripts/loki_logs.py --user-id <uuid> --since 12h

# Everything from one client IP (e.g. chasing a scraper/429 burst)
.venv/bin/python scripts/loki_logs.py web --ip <ip> --since 6h

# Discover what labels/values exist
.venv/bin/python scripts/loki_logs.py --labels
.venv/bin/python scripts/loki_logs.py --label-values service_name

Workflow when debugging from a symptom

Start broad: web --level error --since <window> to find the failure.
Grab the trace_id/request_id from the metadata line.
Re-query by that id with --forward to read the full request in order, spanning web → celery_default if work was dispatched.
Use --print-query to inspect/borrow the LogQL; use --json when you need exact timestamps or fields the pretty output omits.

Notes

Retention is 30 days; queries older than that return nothing.
A query needs at least one matcher — with no SERVICE/--level the script defaults to {service_name=~".+"} (all app streams).
Hitting --limit prints a stderr hint; narrow --since or raise -n.
--ip/--user-agent only match lines ingested after the Alloy config that promotes ip_address/user_agent; older lines won't match those filters.
Read-only. The token is Viewer-scoped; this cannot modify anything.

Files

Just SKILL.md in .claude/skills/loki-logs of letsrevel/revel-backend.

Open the folder on GitHubat commit 8333099

Compare with similar skills

Loki Logs next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Loki Logs compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Loki Logs this skillletsrevel/revel-backend	109	—	~918	Automated safety check: Notes	MIT	yesterday
Opentelemetrygrafana/skills	279	—	~1.7k	Automated safety check: Pass	Apache-2.0	2 days ago
Pyroscopegrafana/skills	279	—	~1.2k	Automated safety check: Pass	Apache-2.0	2 days ago
Agento11y Experimentsgrafana/agento11y	127	—	~2k	Automated safety check: Pass	Apache-2.0	yesterday
Sentry Python SDKgetsentry/sentry-for-ai	268	—	~4.1k	Automated safety check: Pass	Apache-2.0	yesterday
Admingrafana/skills	279	—	~1.5k	Automated safety check: Pass	Apache-2.0	2 days ago

Similar skills

Opentelemetry
grafana/skills
Official
Instrument any app with OpenTelemetry and ship metrics / logs / traces to Grafana Cloud or self-hosted Mimir / Loki / Tempo / Pyroscope.
279 GitHub stars~1.7k tokensUpdated 2 days ago
DevOps & CloudAuto-check passed
Pyroscope
grafana/skills
Official
Continuously profile applications with Grafana Pyroscope and read the result as flame graphs.
279 GitHub stars~1.2k tokensUpdated 2 days ago
DevOps & CloudAuto-check passed
Agento11y Experiments
grafana/agento11y
Official
Run any Python LLM agent as an Agent Observability experiment using the public agento11y.experiments package: define a test suite, run an existing agent through typed trials, bind or record…
127 GitHub stars~2k tokensUpdated yesterday
DevOps & CloudAuto-check passed
Sentry Python SDK
getsentry/sentry-for-ai
Official
Full Sentry SDK setup for Python. An agent skill from getsentry/sentry-for-ai.
268 GitHub stars~4.1k tokensUpdated yesterday
Backend & APIsAuto-check passed
Admin
grafana/skills
Official
Manage Grafana Cloud accounts — organizations, stacks, RBAC roles and assignments, SSO/SAML/OAuth/GitHub auth, service accounts for CI/CD, user invites, team membership, and API-driven provisioning.
279 GitHub stars~1.5k tokensUpdated 2 days ago
DevOps & CloudAuto-check passed
Cloud Infra Supply Chain
zhaji2333/CkSKILLS
当目标涉及云资产（对象存储/云元数据/Serverless）、容器/K8s、运维面板（宝塔/Grafana/Zabbix/Jenkins/GitLab/Nacos等）、消息队列/缓存中间件、CI/CD流水线、第三方回调集成、依赖组件CVE、信息泄露配置时调用。负责未授权访问、弱口令、云配置错误、供应链漏洞与敏感信息挖掘。
113 GitHub stars~688 tokensUpdated 24 days ago
DevOps & CloudAuto-check: warnings

Questions about Loki Logs

What does Loki Logs do?

A skill your agent uses when investigating production behaviour from logs — a 500/error in prod, a failing or stuck Celery task, tracing one request/traceid/user across services, or confirming a…. Loki Logs is an agent skill from letsrevel/revel-backend. Use when investigating production behaviour from logs — a 500/error in prod, a failing or stuck Celery task, tracing one request/traceid/user across services, or confirming a deploy's runtime effect.

When should I use Loki Logs?

Loki Logs fits situations like: investigating production behaviour from logs — a 500/error in prod; stuck Celery task; tracing one request/traceid/user across services; confirming a deploys runtime effect.

How do I install Loki Logs in Claude Code?

Run `npx skills add letsrevel/revel-backend --skill loki-logs -a claude-code`. Or copy the skill folder (.claude/skills/loki-logs in letsrevel/revel-backend) into .claude/skills/loki-logs in your project. Claude Code loads it when a task matches its description.

How do I install Loki Logs in Codex?

Run `npx skills add letsrevel/revel-backend --skill loki-logs -a codex`. Or copy the skill folder (.claude/skills/loki-logs in letsrevel/revel-backend) into .agents/skills/loki-logs in your project. Codex loads it when a task matches its description.

Can I use Loki Logs in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add letsrevel/revel-backend --skill loki-logs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/loki-logs, .gemini/skills/loki-logs, .github/skills/loki-logs and .opencode/skills/loki-logs in your project.

What does Loki Logs need to run?

Going by SKILL.md and its folder, Loki Logs needs the command-line tools its instructions call (python) and credentials named GRAFANA_TOKEN. Our summary lists: Python 3; A credential in GRAFANA_TOKEN. Its frontmatter pre-approves these tools: Bash(python:*), Bash(.venv/bin/python:*), Read, Grep.

Does Loki Logs access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Loki Logs safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Loki Logs use?

Loki Logs is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Loki Logs use?

About 918 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Loki Logs?

Skills that share tags, products or a category with Loki Logs: Opentelemetry (grafana/skills, 279 stars), Pyroscope (grafana/skills, 279 stars), Agento11y Experiments (grafana/agento11y, 127 stars) and Sentry Python SDK (getsentry/sentry-for-ai, 268 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Loki Logs?

letsrevel (a GitHub organization) maintains it in letsrevel/revel-backend, which has 109 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 7, 2026.

Source: letsrevel/revel-backend on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Loki Logs

Install Loki Logs

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Loki Logs

Tool

What you can filter on

Recipes

Workflow when debugging from a symptom

Notes

Files

Compare with similar skills

Similar skills

Opentelemetry

Pyroscope

Agento11y Experiments

Sentry Python SDK

Admin

Cloud Infra Supply Chain

More from letsrevel/revel-backend

Silk Debug

Update Changelog

Whats New

Updating Deps

Questions about Loki Logs

Install Loki Logs

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Loki Logs

Tool

What you can filter on

Recipes

Workflow when debugging from a symptom

Notes

Files

Compare with similar skills

Similar skills

More from letsrevel/revel-backend

Related

Questions about Loki Logs