Name: fyber
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

fyber

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

Quality

74%

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

Quality

Content

82%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 highly actionable with copy-paste Membrane CLI commands and a clear connect→discover→run workflow that includes state-polling validation. Its weaknesses are minor: a small amount of conceptual padding, inconsistent step numbering, and no destructive-operation caution for the proxy's DELETE method.

Suggestions

Add a brief validation/caution note before destructive proxy calls (e.g. DELETE/PUT), recommending a dry-run GET or confirmation for batch operations.

Fix the step numbering: either add a "1a"/"Step 1" header and a labeled "Step 2: Discover actions" section, or remove the dangling "Step 2" references.

Trim the opening "what is Fyber" paragraph and the "rather than auth plumbing" aside to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands with minimal prose, but includes minor padding such as the opening "Fyber is an advertising technology platform..." explainer and "so you can focus on the integration logic rather than auth plumbing", fitting the anchor for efficient content with minor over-explanation that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands throughout (`membrane login`, `membrane connection ensure`, `membrane action list/run`, `membrane request`) plus a flags table for the proxy, with concrete examples covering the common install/auth/connect/discover/run cases, matching the fully-executable anchor.	5 / 5
Workflow Clarity	The connect workflow has explicit validation checkpoints (poll `--wait` until state leaves BUILDING; handle CLIENT_ACTION_REQUIRED then re-poll), but step numbering is inconsistent ("1b" with no "1a", references to "Step 2" with no Step 2 header) and there is no caution/validation around destructive proxy methods like DELETE, fitting the anchor for a clear sequence with minor validation gaps.	4 / 5
Progressive Disclosure	The file is well-organized into clear sections (Overview, Working with Fyber, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested references, but at ~140 lines everything is inline with no content split to separate files, fitting the anchor for good structure with minor organization gaps rather than the well-signaled one-level-deep reference structure of a 5.	4 / 5
	Total	17 / 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 clearly identifies a distinct niche (Fyber) and includes an explicit 'Use when' trigger, satisfying both the what and when requirements. Its main weakness is generic action verbs ('manage data, records') that under-specify Fyber's actual capabilities and limited trigger-term coverage.

Suggestions

Replace generic verbs with Fyber-specific capabilities, e.g. "Manage ad campaigns, bidders, organizations, users, and reports."

Broaden trigger terms to natural user phrasing such as "Use when the user wants to manage Fyber ad campaigns, bids, or reporting data."

Mention concrete entities (campaigns, bidders, reports) so the description doubles as a trigger-term surface.

Dimension	Reasoning	Score
Specificity	Quotes "Manage data, records, and automate workflows" name the Fyber domain plus a few actions, but the actions are generic ("manage data", "manage records") rather than Fyber-specific concrete capabilities like campaigns, bidders, or reports, matching the anchor that lists 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It explicitly states both what ("Fyber integration. Manage data, records, and automate workflows.") and when ("Use when the user wants to interact with Fyber data."), but the 'when' is a single trigger phrase and the 'what' is generic rather than the concrete multi-trigger phrasing of the 5 anchor, so it sits at 4.	4 / 5
Trigger Term Quality	The phrase "Use when the user wants to interact with Fyber data" provides a natural trigger keyword ("Fyber", "Fyber data"), but coverage is limited to those two terms and misses common variations a user might say (ad campaigns, monetization, reports, bids), fitting the anchor for some relevant keywords missing common synonyms.	3 / 5
Distinctiveness Conflict Risk	"Fyber integration" names a specific advertising platform with a distinct trigger ("interact with Fyber data"), giving it a clear niche with minimal overlap risk against other skills, matching the anchor for a clear niche with distinct triggers.	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/fyber/SKILL.md
Commit: f484c82

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