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

Blog Docs Log in Get started

bearer

Bearer integration. Manage data, records, and automate workflows. Use when the user wants to interact with Bearer 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/bearer/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 highly actionable with concrete, executable CLI commands and a well-sequenced connection workflow that includes validation via state polling. It loses some conciseness to explanatory padding and a duplicated section, and could split some inline reference material into separate files.

Suggestions

Remove the intro paragraph defining what Bearer is and trim motivational phrases ('so you can focus on the integration logic') that assume Claude lacks context.

Delete or merge the redundant 'Popular actions' section, which repeats the 'membrane action list' guidance already given under 'Searching for actions'.

Move the proxy request flags table and clientAction field breakdown into a dedicated references file (e.g., reference.md) and link to it from the body.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes an unnecessary intro paragraph explaining what Bearer is, mild fluff ('so you can focus on the integration logic rather than auth plumbing'), and a redundant 'Popular actions' section that duplicates the search guidance.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands for connection setup, action search/run, JSON parameters, and a proxy flags table covering the common cases.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with a state-machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and an explicit poll-again feedback loop, though a referenced 'Step 2' is not explicitly labeled, a minor gap.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized with clear section headers and no external bundle files to navigate, though ~145 lines of inline proxy-flag and clientAction detail could be split into separate references.	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 covers both what the skill does and when to use it with a clear, distinct trigger tied to the Bearer product. Its main weakness is generic action language ('manage data, records') that lacks concrete, specific capabilities.

Suggestions

Replace generic verbs with concrete Bearer capabilities (e.g., 'monitor API integrations, track API usage, detect anomalies, manage incidents and log events').

Add natural trigger synonyms to the 'Use when' clause, such as 'when the user mentions API monitoring, integration incidents, or Bearer logs'.

Mention the connection/action workflow briefly so the 'what' reflects the actual operations the skill performs.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Bearer integration') and a few actions ('Manage data, records, and automate workflows'), but these are generic verbs rather than concrete operations like 'extract tables' or 'fill forms'.	3 / 5
Completeness	Both 'what' (Bearer integration that manages data, records, and workflows) and an explicit 'when' clause are present, though the 'when' is generic and could be more specific.	4 / 5
Trigger Term Quality	It includes one natural trigger phrase ('Use when the user wants to interact with Bearer data') but misses common variations or synonyms a user might say.	3 / 5
Distinctiveness Conflict Risk	It targets a clear niche tied to a named product ('Bearer integration', 'interact with Bearer data') with minimal overlap risk against 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/bearer/SKILL.md
Commit: f484c82

Reviewed: ~2 hours 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.