Name: kibana
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

kibana

Kibana integration. Manage data, records, and automate workflows. Use when the user wants to interact with Kibana data.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/kibana/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable commands and a strong connection state-machine, but it carries some unnecessary explanation and is a single inlined file rather than progressively disclosed. Trimming the padding and splitting the dense reference material would raise conciseness and progressive disclosure.

Suggestions

Remove the introductory sentence explaining what Kibana is and who uses it, plus the "so you can focus on the integration logic" padding, to tighten conciseness.

Move the connection state-machine details and the proxy flags table into separate reference files (e.g. CONNECTION_STATES.md, PROXY_REFERENCE.md) referenced one level deep from the overview.

Add an explicit validation step after running actions (e.g. check the output/error fields before proceeding) to strengthen the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command-driven content, but includes explanation Claude already knows ("Kibana is a data visualization dashboard for Elasticsearch data...") and padding ("so you can focus on the integration logic rather than auth plumbing"), fitting the score-3 anchor.	3 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (membrane connection ensure, action run with --input, request) plus a comprehensive proxy flags table covering the common cases, matching the score-5 anchor.	5 / 5
Workflow Clarity	A clear install->auth->connect->poll->search->run->proxy sequence with an explicit state-machine feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll); the minor gap is no result-validation step and the steps are not a single cohesive numbered list.	4 / 5
Progressive Disclosure	Well-organized into clear sections with a good overview, but monolithic: no bundle files exist, and the detailed state machine and proxy reference that could live in separate files are inlined, fitting the score-4 anchor.	4 / 5
	Total	16 / 20 Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a solid third-person statement with an explicit "Use when..." clause and a clear product niche, but its action list is generic and its trigger coverage lacks common synonyms. Strengthening the verbs and adding natural variations would lift the mid-range dimensions.

Suggestions

Replace generic verbs with concrete Kibana actions, e.g. "Search data, build dashboards, create visualizations, and manage alerts" instead of "Manage data, records, and automate workflows".

Add common user-facing synonyms to the trigger clause, e.g. "Use when the user wants to work with Kibana, dashboards, visualizations, or Elasticsearch data."

List a couple more concrete capabilities to push specificity from 3 toward 5.

Dimension	Reasoning	Score
Specificity	Names the Kibana domain and lists 2-3 actions ("Manage data, records, and automate workflows"), but the verbs are generic rather than concrete, matching the score-3 anchor of 1-2 actions without comprehensive coverage.	3 / 5
Completeness	Both "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Kibana data") are present; the single trigger phrase keeps it just below the score-5 bar of multiple concrete triggers.	4 / 5
Trigger Term Quality	The core term "Kibana" / "Kibana data" is present and "interact with Kibana data" is a natural trigger, but common synonyms (dashboards, visualizations, Elasticsearch) are missing, fitting the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	Kibana is a named product with a clear niche and distinct triggers, giving minimal conflict risk with other skills.	5 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/kibana/SKILL.md
Commit: f484c82

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.