CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bearer

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

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/bearer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 body is a solid, executable operational guide — its state-machine handling of connection readiness is a highlight. Its main defects are the dangling "Step 2" references that break the workflow's continuity and a few filler sections that dilute an otherwise efficient document.

Suggestions

Fix the broken step numbering: either add a labeled "Step 2" section (discover and run actions) or rewrite the two "skip to Step 2" references to point at the real section names, since currently no Step 2 exists.

Standardize on one CLI invocation form (`membrane` vs `npx @membranehq/cli`) or briefly explain when each applies, and drop the content-free 'Bearer Overview' entity list and "Use action names and parameters as needed." line.

Merge the 'Popular actions' section into 'Searching for actions' — it currently repeats the same discovery command without adding anything.

DimensionReasoningScore

Conciseness

The body is mostly lean and command-driven (install, login, connection ensure, the proxy flag table), with only minor trimmable filler: the bare entity bullet list under 'Bearer Overview', "Use action names and parameters as needed.", and the Agent Types aside. Not 5 because those tokens don't earn their place; not 3 because there is no explanation of concepts Claude already knows.

4 / 5

Actionability

Concrete, copy-paste-ready commands cover the common cases (membrane login, connection ensure/get with --wait, action list --intent, action run --input, request with flags). Not 5 because of minor gaps: `membrane` and `npx @membranehq/cli` invocations are mixed without explanation, and the `connection ensure` output fields are referenced but never shown.

4 / 5

Workflow Clarity

A rough sequence exists (install → login → connect → poll state → discover → run → proxy) with genuinely good state-branching for CLIENT_ACTION_REQUIRED, but "skip to **Step 2**" appears twice while no Step 2 section exists — the numbering jumps from an unlabeled step to "#### 1b", leaving the intended flow incoherent at exactly the point it matters. Not 4 because of this dangling reference; not 2 because the sequence and state validation checkpoints are present.

3 / 5

Progressive Disclosure

This is a single-file skill (no references/, scripts/, or assets/ directories exist), and the body is well-sectioned with clear headers, keeping content appropriately inline. Not 5 because at ~145 lines it exceeds the simple-skill threshold and the 'Popular actions' section merely duplicates the 'Searching for actions' command with no added value.

4 / 5

Total

15

/

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 has the right skeleton — domain name plus an explicit "Use when..." clause — but wastes it on generic filler verbs. A user reading only this description would not learn what Bearer actually does (monitor third-party API integrations, track API usage, detect anomalies, alert on incidents).

Suggestions

State Bearer's actual purpose in the 'what' clause, e.g. 'Monitor third-party API integrations: track API usage, detect anomalies, and manage incidents and logs.'

Replace the generic 'Manage data, records, and automate workflows' with concrete Bearer actions (list integrations, view log events, acknowledge incidents) to raise specificity from 2.

Add natural trigger terms such as 'API integrations', 'integration monitoring', 'anomaly detection', or 'Bearer alerts' so users who describe the problem rather than naming the tool still match.

DimensionReasoningScore

Specificity

The description names the domain ("Bearer integration") but its actions are entirely generic ("Manage data, records, and automate workflows"), matching the anchor 'Names the domain but actions are minimal or generic'. It never states a concrete Bearer-specific capability such as monitoring integrations, tracking API usage, or anomaly alerts, so it cannot reach 3.

2 / 5

Completeness

An explicit "when" is present ("Use when the user wants to interact with Bearer data"), but the "what" is vague — it never says Bearer monitors third-party API integrations. This sits between anchor 2 (vague what, no when) and anchor 4 (both present): the explicit when keeps it above 2, the unclear what keeps it below 4.

3 / 5

Trigger Term Quality

"Bearer", "data", and "records" provide the distinctive product keyword plus a trigger clause, but coverage misses the natural phrases a user would say ("API integrations", "integration monitoring", "anomalies", "alerts"). Not 4 because the keyword set is thin and the trigger is circular ("interact with Bearer data").

3 / 5

Distinctiveness Conflict Risk

"Bearer integration" carves a niche when the user names the product, but "Manage data, records, and automate workflows" is broad enough to overlap with any data-management or automation skill. Distinctiveness rests solely on the product name, matching 'Somewhat specific but could still overlap with similar skills'.

3 / 5

Total

11

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

Revision

f484c82

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill