graylog-cli
Skill8 starsChanged 6 months agoApache-2.0View on GitHub
Perform Graylog operations using the Graylog HTTP API via curl. Use for searching logs, and inspecting streams, dashboards, and alerts.
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use the instance and rules below when constructing all Graylog API commands.
- Distinctive: line 12
Update the table below with your Graylog instance URLs and credential file paths:
- Distinctive: line 19
If the target instance is unclear, ask the user before running any command.
- Distinctive: line 78
NEVER target any Graylog instance not listed in the instance table above.
- Distinctive: line 79
NEVER print, display, log, or store the contents of any token file.
- Very specific: line 80
Always read the token inline with $(cat <TOKEN_FILE>) — never hardcode a token value in a command.
- Very specific: line 81
Always include the X-Requested-By header on every request — Graylog rejects requests without it.
- Very specific: line 82
Always pass -s (silent) to curl and pipe through jq for readable output.
- Distinctive: line 83
NEVER run DELETE endpoints without explicit user instruction — these are irreversible.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Graylog CLI Skill
Use the instance and rules below when constructing all Graylog API commands.
Instances
Update the table below with your Graylog instance URLs and credential file paths:
| Environment | Base URL | Token File |
| Production | https://<your-graylog-prod-url> | ~/.graylog/prod.token |
| Staging | https://<your-graylog-staging-url> | ~/.graylog/staging.token |
If the target instance is unclear, ask the user before running any command.
Prerequisites (one-time setup by user)
Generate a Graylog API token (System → Users → Edit Tokens) for each instance and save it to the corresponding token file. Never print or display token values. Do not perform these steps yourself.
mkdir -p ~/.graylog && echo "<your-api-token>" > <TOKEN_FILE> && chmod 600 <TOKEN_FILE>Command Format
Graylog uses the API token as the username with token as the password:
curl -s -u "$(cat <TOKEN_FILE>):token" -H "X-Requested-By: cli" \
"<BASE_URL>/api/<endpoint>" | jq .Available API Endpoints
Read-only (safe, no confirmation needed)
| Endpoint | Method | Description |
/api/search/universal/relative | GET | Run a relative-time search query |
/api/streams | GET | List streams |
/api/streams/<id> | GET | Get a specific stream |
/api/dashboards | GET | List dashboards |
/api/alerts | GET | List triggered alerts |
/api/system/indices/index_sets | GET | List index sets |
/api/system/cluster/node | GET | Show cluster node info |
Example — search query
curl -s -u "$(cat <TOKEN_FILE>):token" -H "X-Requested-By: cli" \
"<BASE_URL>/api/search/universal/relative?query=<query>&range=3600&limit=50" | jq .Mutating operations (confirm with user before running)
| Endpoint | Method | Description |
/api/streams | POST | Create a stream |
/api/streams/<id> | PUT | Update a stream |
/api/dashboards | POST | Create a dashboard |
/api/streams/<id>/pause / /resume | POST | Pause or resume a stream |
Never run — requires explicit human approval
| Endpoint | Method | Reason |
/api/streams/<id> | DELETE | Irreversible stream deletion |
/api/dashboards/<id> | DELETE | Irreversible dashboard deletion |
/api/system/indices/index_sets/<id> | DELETE | Irreversibly deletes an index set and its data |
Rules
- NEVER target any Graylog instance not listed in the instance table above. If a URL references a different host, stop and ask the user to confirm.
- NEVER print, display, log, or store the contents of any token file.
- Always read the token inline with
$(cat <TOKEN_FILE>)— never hardcode a token value in a command. - Always include the
X-Requested-Byheader on every request — Graylog rejects requests without it. - Always pass
-s(silent) tocurland pipe throughjqfor readable output. - NEVER run DELETE endpoints without explicit user instruction — these are irreversible.
- For search queries, always set a bounded
rangeand a reasonablelimit— an unbounded search can be slow and return excessive data.
In this repository54 other files it gives its agents.
- alibabacloud-cliSkill
- ansible-cliSkill
- appdynamics-cliSkill
- argocd-cliSkill
- aws-cliSkill
- aws-cloudwatch-cliSkill
- azure-cliSkill
- bash-lintingSkill
- betterstack-cliSkill
- bitbucket-cliSkill
- chef-cliSkill
- code-reviewSkill
- commit-codeSkill
- create-dockerfileSkill
- create-terraform-helm-upgrade-planSkill
- datadog-cliSkill
- digitalocean-cliSkill
- dockerfile-lintingSkill
- dynatrace-cliSkill
- elasticsearch-cliSkill
- gcp-cliSkill
- github-cliSkill
- gitlab-cliSkill
- go-lintingSkill
- grafana-cliSkill
- grafana-loki-cliSkill
- helm-cliSkill
- hetzner-cliSkill
- huaweicloud-cliSkill
- jaeger-cliSkill
- jenkins-cliSkill
- jira-and-confluence-cliSkill
- kibana-cliSkill
- kubernetes-cliSkill
- loggly-cliSkill
- maintenance-check-aws-eksSkill
- maintenance-create-ticket-on-jiraSkill
- ms-teams-cliSkill
- mysql-cliSkill
- newrelic-cliSkill
- oci-cliSkill
- packer-cliSkill
- papertrail-cliSkill
- postgresql-cliSkill
- prometheus-cliSkill
- python-lintingSkill
- rollbar-cliSkill
- salesforce-cliSkill
- sentry-cliSkill
- slack-cliSkill
- splunk-cliSkill
- terraform-cliSkill
- terraform-lintingSkill
- vault-cliSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.