ワンクリックでManusで任意のスキルを実行

kibana-elasticsearch

スター17

フォーク2

更新日2026年7月25日 12:31

Use when querying Elasticsearch through the Kibana console proxy, especially for log investigations, field-based filtering, or error triage from job or application logs.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

l-lin

l-lin/dotfiles

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

関連職種SOC

SOC 職業分類に基づく

ネットワーク・コンピュータシステム管理者コンピュータ・数学職·SOC 15-1244

ファイルエクスプローラー

2 ファイル

SKILL.md

readonly

name	kibana-elasticsearch
description	Use when querying Elasticsearch through the Kibana console proxy, especially for log investigations, field-based filtering, or error triage from job or application logs.

Check access first. Verify ES_API_KEY and KIBANA_URL are set without printing their values. If Cloudflare Access may apply, verify cloudflared is available and authenticated. If access is missing, stop and ask the user to fix it before querying.
Discover fields first. On an unfamiliar index or pattern, fetch mappings before writing queries. Do not guess field names, nested paths, or text versus keyword variants.
Query narrowly first. Start with the smallest useful time window, explicit _source fields, and sorted timestamps. Prefer wildcard index patterns like logs* or jobs*. Remember the proxy path must URL-encode / as %2F.
Prove the result. Report the index pattern, time window, decisive fields, and a small excerpt or count that supports the conclusion. If nothing matches, say whether access, mappings, time range, or filters are the likely gap.
Reach for the reference. Use references/COMMANDS.md for access checks, proxy command templates, mapping discovery, and query patterns.

このリポジトリの他の Skills

同じリポジトリ

devils-advocate

l-lin/dotfiles

Use when pressure-testing a plan, architecture, code change, or AI-generated proposal before committing, especially when hidden assumptions, production risks, or failure modes may be underexplored.

2026-07-2517

crafting-skills

l-lin/dotfiles

Use when creating or updating skills in `~/.config/ai/skills`, especially when a `SKILL.md` has a weak trigger, tangled structure, poor steering, or bloated wording.

2026-07-2517

datadog-pup

l-lin/dotfiles

Use when interacting with Datadog resources using the `pup` CLI, especially for APM traces, metrics, monitors, notebooks, and synthetic tests.

2026-07-2517

code-simplifier

l-lin/dotfiles

Use when simplifying recently touched code without changing behavior, especially when asked to "simplify code", "clean up code", "refactor for clarity", or "improve readability".

2026-07-2517

ingest-url

l-lin/dotfiles

Ingest a URL into the patient account wiki. Use when the user provides a URL (Atlassian/Confluence, web articles, documentation) and wants to add it to their research wiki. Handles fetching, markdown conversion, asset extraction, and runs the full wiki ingest workflow. Triggers on "ingest <url>", "add this to the wiki", or when user shares a URL in the context of wiki research.

2026-07-2417

journal

l-lin/dotfiles

Use at session start, after context compaction, and before session end. Owns session journals in `.sandbox/journals/`: when to create one, what prior context to read, what to log, and how to leave a resumable handoff

2026-07-1117

name	kibana-elasticsearch
description	Use when querying Elasticsearch through the Kibana console proxy, especially for log investigations, field-based filtering, or error triage from job or application logs.

Check access first. Verify ES_API_KEY and KIBANA_URL are set without printing their values. If Cloudflare Access may apply, verify cloudflared is available and authenticated. If access is missing, stop and ask the user to fix it before querying.
Discover fields first. On an unfamiliar index or pattern, fetch mappings before writing queries. Do not guess field names, nested paths, or text versus keyword variants.
Query narrowly first. Start with the smallest useful time window, explicit _source fields, and sorted timestamps. Prefer wildcard index patterns like logs* or jobs*. Remember the proxy path must URL-encode / as %2F.
Prove the result. Report the index pattern, time window, decisive fields, and a small excerpt or count that supports the conclusion. If nothing matches, say whether access, mappings, time range, or filters are the likely gap.
Reach for the reference. Use references/COMMANDS.md for access checks, proxy command templates, mapping discovery, and query patterns.