Name: signalfx
Rating: 59.2 (1 reviews)
Author: membranedev

signalfx

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

Quality

68%

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/signalfx/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 content is a solid, mostly executable guide to driving SignalFx through the Membrane CLI, with a clear workflow and good command coverage. Its main weaknesses are a slightly misleading "Popular actions" section, a broken "Step 2" cross-reference, and minor verbosity in the intro and auth sections.

Suggestions

Fix the navigation: either label the workflow steps (Step 1, Step 2) or remove the "skip to Step 2" reference and the orphaned "1b" heading.

Populate the "Popular actions" section with concrete example actions (e.g. retrieve a dashboard, search metrics, list detectors) instead of only repeating the discovery command.

Trim marketing-style phrasing like "so you can focus on the integration logic rather than auth plumbing" and consider moving the proxy flag table to a separate reference file.

Dimension	Reasoning	Score
Conciseness	The body is command-focused and largely lean, but contains minor padding such as "so you can focus on the integration logic rather than auth plumbing" and a one-line restatement of what SignalFx is that Claude could largely infer.	4 / 5
Actionability	It provides copy-paste-ready membrane commands with flags and a proxy-option table, but the "Popular actions" section only repeats the discovery command instead of listing actual popular actions, leaving a minor gap.	4 / 5
Workflow Clarity	The install→auth→connect→search→run sequence is clear and the connection state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/ERROR) includes polling feedback loops, but the text references a "Step 2" that is never labeled, and section numbering ("1b" with no "1"/"2") is inconsistent.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clear sections with no nested references and no bundle files, though some content (the proxy flag table, the full connection state machine) could arguably live in separate reference files for a cleaner overview.	4 / 5
	Total	16 / 20 Passed

Description

62%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 clearly targeted at SignalFx and includes an explicit use-trigger, but its action language is generic and it misses the domain-specific terms (dashboards, detectors, metrics, alerts) that users would naturally say. It sits comfortably above average but lacks the concreteness of a top-tier description.

Suggestions

Replace generic verbs with concrete SignalFx operations, e.g. "Create and manage dashboards, charts, detectors, and events; search metrics and trigger alerts."

Expand the trigger clause to include natural synonyms: "Use when the user wants to monitor SignalFx metrics, view or edit dashboards, manage detectors, or investigate events."

Add file-format or entity keywords (detectors, charts, SignalFx events) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the SignalFx domain and lists a few actions ("Manage data, records, and automate workflows"), but the verbs are generic rather than concrete SignalFx operations like dashboards, charts, detectors, or events.	3 / 5
Completeness	It provides both a "what" (manage data, records, automate workflows) and an explicit "Use when..." trigger, though the "what" is vague and the "when" could name more concrete SignalFx scenarios.	4 / 5
Trigger Term Quality	It includes "SignalFx" and "interact with SignalFx data" as natural triggers, but omits the common terms a user would actually say such as monitoring, metrics, dashboards, detectors, or alerts.	3 / 5
Distinctiveness Conflict Risk	SignalFx is a specific branded niche with a distinct trigger ("interact with SignalFx data"), giving minimal conflict risk, though the generic "manage data, records, and automate workflows" phrasing could loosely overlap with other data skills.	4 / 5
	Total	14 / 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/signalfx/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.