Name: authbridge
Rating: 55.2 (1 reviews)
Author: membranedev

authbridge

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

Quality

63%

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/authbridge/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 strong, executable CLI integration guide with a clear connection-setup workflow and validation feedback loop. Its main weaknesses are minor redundancy/filler, the absence of post-action verification, and no progressive disclosure to separate reference files despite the length.

Suggestions

Remove the thin "Authbridge Overview" bullet list and the duplicated "Popular actions" section, or merge them into a single concise "Discover actions" step.

Add a verification step after running actions (e.g. check the `output`/error fields and confirm expected state), especially for write or batch operations.

Move the detailed proxy flags table and connection state-machine reference into a separate `references/cli.md` linked once from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable commands, but the "Authbridge Overview" bullet list plus "Use action names and parameters as needed" is vague filler, and "Searching for actions" / "Popular actions" repeat the same discovery command, so it could be tightened.	3 / 5
Actionability	Provides concrete, copy-paste bash commands throughout (install, login, connection ensure, action run, request) plus a flags table, with only minor gaps from generic placeholders (CONNECTION_ID, QUERY) and no fully worked end-to-end example.	4 / 5
Workflow Clarity	The install → authenticate → ensure connection → poll-until-READY sequence is clearly ordered with an explicit state-machine feedback loop (BUILDING/READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but there is no validation step after actually running actions.	4 / 5
Progressive Disclosure	The body is well-sectioned with no broken or nested references, but at 140+ lines all content (the proxy flags table, the connection state machine, best practices) is inlined in a single file with no one-level-deep references to split the bulk.	3 / 5
	Total	14 / 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 correctly pairs a "what" with an explicit "Use when…" trigger and names a distinct platform, but its action verbs and trigger terms are generic. Adding concrete capabilities and natural synonyms (KYC, background checks, verification) would lift it from good to strong.

Suggestions

Replace generic verbs with concrete actions, e.g. "Run identity verifications, background checks, and KYC lookups via Authbridge actions."

Expand the trigger clause with natural user phrases: "Use when the user wants to verify identities, run background checks, KYC, or interact with Authbridge data."

Add file/extension or domain synonyms users actually say (e.g. "identity verification", "screening") to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the Authbridge domain and several actions ("Manage data, records, and automate workflows"), but the verbs are generic rather than concrete, matching the anchor that lists 1-2 actions without comprehensive coverage.	3 / 5
Completeness	Answers both "what" (manage data, records, automate workflows) and "when" ("Use when the user wants to interact with Authbridge data"), but the trigger clause is generic rather than listing concrete trigger phrases, fitting the anchor where "when" could be more explicit.	4 / 5
Trigger Term Quality	Includes "Authbridge" and "data, records, workflows" but omits the natural terms users would say (KYC, background check, identity verification, screening), so keyword coverage has relevant but incomplete terms.	3 / 5
Distinctiveness Conflict Risk	"Authbridge" is a named platform giving it a clear niche with low conflict risk, though the generic "Manage data, records, automate workflows" verbs leave minor overlap with adjacent data-integration 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/authbridge/SKILL.md
Commit: f484c82

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