Name: blackfire
Rating: 49.6 (1 reviews)
Author: membranedev

blackfire

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

Quality

54%

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/blackfire/SKILL.md

Quality

Content

63%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 concrete, executable Membrane/Blackfire CLI guide with a clear multi-step workflow and a genuine state-based validation checkpoint for connection readiness. It loses points for some padded explanation, placeholder-only examples, a couple of dangling step references, and a monolithic structure with no progressive disclosure.

Suggestions

Tighten or remove non-instructive framing (e.g. the auth-plumbing sentence and the loosely written agent-types line) to respect token budget.

Resolve the dangling 'skip to Step 2' references by labeling the downstream steps (Searching for actions / Running actions) as Step 2 and Step 3.

Consider moving the full proxy options table and CLI command catalog into a one-level-deep reference file so SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete CLI commands and an options table, but includes unnecessary explanation such as the framing 'Membrane handles authentication... so you can focus on the integration logic rather than auth plumbing' and the loosely written agent-types sentence, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened.'	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure, polling, action list/run, and proxying plus a full options table, but relies on placeholders (CONNECTION_ID, actionId, agentType) rather than concrete worked examples, matching 'mostly executable guidance with minor gaps.'	4 / 5
Workflow Clarity	The install → authenticate → connect → poll-until-ready → search → run/proxy sequence is clear, and the connection state machine (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) acts as an explicit checkpoint with feedback ('poll again after the user completes the action'), though dangling 'skip to Step 2' references are a minor gap.	4 / 5
Progressive Disclosure	The body is well sectioned but monolithic at ~147 lines with no bundle files and no external references; material such as the full CLI command catalog and proxy options table is all inlined rather than split into one-level-deep references, fitting 'some structure but content that should be separate is inline.'	3 / 5
	Total	14 / 20 Passed

Description

45%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 pairs the Blackfire product name with generic Membrane integration boilerplate, providing an explicit trigger but no concrete profiling-specific actions or trigger terms. It is distinguishable mainly by name rather than by capability.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with Blackfire-specific actions such as 'Profile PHP applications, inspect call graphs, and analyze performance bottlenecks.'

Add natural trigger terms users would actually say, e.g. 'Use when the user wants to profile PHP code, find performance bottlenecks, or analyze Blackfire call graphs.'

Differentiate from other Membrane integration skills by foregrounding the profiling/performance-analysis purpose rather than the shared data-management phrasing.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the integration domain but the actions are minimal and generic, with no concrete profiling/performance actions stated, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	Both a 'what' and a 'when' clause exist, but the 'what' ("Manage data, records, and automate workflows") is generic boilerplate rather than a clear concrete statement of what the skill does, so it falls below the 'both what and when, when could be more explicit' level.	3 / 5
Trigger Term Quality	The product name "Blackfire" is a strong natural keyword and a 'Use when the user wants to interact with Blackfire data' trigger is present, but task-specific terms users would actually say (profile, profiler, performance, bottleneck, PHP) are missing, so it sits at 'some relevant keywords but missing common variations.'	3 / 5
Distinctiveness Conflict Risk	The "Blackfire" name gives it a niche, but the action phrasing ("Manage data, records, and automate workflows") is shared generic Membrane boilerplate used across many integration skills, creating real overlap risk with similar skills.	3 / 5
	Total	11 / 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/blackfire/SKILL.md
Commit: f484c82

Reviewed: 8 minutes 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.