Name: splunk
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

splunk

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

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

61%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 skill is actionable with concrete CLI commands and a well-structured connection workflow, but it spends tokens explaining Splunk basics and omits validation checkpoints for destructive proxy/action operations.

Suggestions

Remove the opening paragraph defining what Splunk is and the filler line "Use action names and parameters as needed" to tighten token usage.

Add a validation/verification checkpoint after `membrane request` and `membrane action run` (e.g. inspect the `output`/error fields and confirm state before proceeding) to support destructive and batch operations.

Fill out or drop the bare "Splunk Overview" bullet list (Search / Saved Search) so it does not read as an unfinished placeholder.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient concrete commands, but it opens by explaining what Splunk is and includes filler like "Use action names and parameters as needed" and "This is the fastest way to get a connection" that Claude does not need.	3 / 5
Actionability	Provides copy-paste-ready membrane commands with explicit flags (login, connection ensure, action list/run, request) and a proxy flag table, with only minor gaps like the CONNECTION_ID placeholder.	4 / 5
Workflow Clarity	The connection setup has a strong state-based feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED polling), but action execution and the destructive-capable proxy (DELETE) lack validation/verification checkpoints, capping the score.	3 / 5
Progressive Disclosure	The body is well organized into clear sections (Install, Authentication, Connecting, Searching, Proxy, Best practices) with no nested references, though the thin "Splunk Overview" section adds little and no external references are used.	4 / 5
	Total	14 / 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 correctly pairs a what/when structure and targets a distinct, low-conflict niche, but relies on generic action verbs and a thin set of trigger keywords rather than concrete Splunk terminology.

Suggestions

Replace generic verbs with concrete Splunk actions, e.g. "Search logs, run saved searches, and run Splunk actions via Membrane."

Expand trigger terms to natural phrasings users say: "Use when the user wants to search Splunk logs, run SPL queries, or trigger saved searches."

Dimension	Reasoning	Score
Specificity	Names the Splunk domain and lists a few actions ("Manage data, records, and automate workflows"), but the verbs are generic rather than concrete operations like searching logs or running SPL queries.	3 / 5
Completeness	Both a clear "what" (manage data, records, automate workflows) and an explicit "when" ("Use when the user wants to interact with Splunk data") are present, though the trigger could be more specific.	4 / 5
Trigger Term Quality	"Splunk" and "Splunk data" are the relevant keywords, but common natural variations users would say (logs, search, queries, SPL) are missing.	3 / 5
Distinctiveness Conflict Risk	"Splunk integration" targets a clearly distinct platform niche with explicit Splunk-specific 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/splunk/SKILL.md
Commit: f484c82

Reviewed: 4 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.