Name: bloom-credit
Rating: 62.4 (1 reviews)
Author: membranedev

bloom-credit

Bloom Credit integration. Manage data, records, and automate workflows. Use when the user wants to interact with Bloom Credit 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/bloom-credit/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 executable Membrane CLI commands and a state-driven connection workflow that includes validation checkpoints. Its main gaps are a duplicated action-discovery section, a dangling "Step 2" reference, and inlined reference material that could live in a separate file.

Suggestions

Fix the dangling navigation: the body says "skip to Step 2" and "Step 2" but no such labeled section exists — either add the Step 2 section or reword the cross-references.

Merge "Searching for actions" and "Popular actions" to remove the repeated `membrane action list` example and reduce token overhead.

Move the entity overview list and the proxy-options flag table into a separate REFERENCE.md, keeping SKILL.md as a concise overview with a one-level-deep pointer.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven with little padding, though the opening paragraph explains what Bloom Credit is and the "Popular actions" section partially duplicates "Searching for actions". Not 5 because a few sentences (the product overview, the repeated action-list command) could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure/get, action list/run, and proxy requests, with concrete flags and a parameters example. These cover the common integration cases fully, matching the top anchor.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with state-based checkpoints (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and re-polling after user action. It is not 5 because the text references a labeled "Step 2" that does not exist, leaving one navigation gap.	4 / 5
Progressive Disclosure	The skill is a single well-sectioned file with no external bundle files, and the structure is clear and navigable. It is not 5 because the entity overview list and proxy-options table are inlined rather than split into a reference file, a minor organization gap for a body of this length.	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 names a distinct niche and includes an explicit Use-when clause, which keeps it solid. Its weakness is vague capability language ("manage data, records, automate workflows") and missing natural credit-domain trigger terms.

Suggestions

Replace generic verbs with concrete Bloom Credit capabilities, e.g. "Pull credit reports, verify identity, and assess applicant risk."

Add natural trigger terms users actually say, such as "credit reports", "credit scores", "credit checks", or "loan applications".

Tighten the Use-when clause to name the triggering intent, e.g. "Use when the user wants to pull credit data or automate Bloom Credit workflows."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Bloom Credit domain plus a couple of actions, but the actions are generic rather than a comprehensive list of concrete capabilities. It does not reach 4 because it lacks several specific actions (e.g. pull credit reports, verify identity) and is not bare enough for 2.	3 / 5
Completeness	It states both a what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Bloom Credit data"). It falls short of 5 because the what-side actions are vague rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	It surfaces relevant keywords ("Bloom Credit", "data", "records", "workflows") but omits common natural variations users would say, such as "credit reports", "credit scores", or "lending". Not 4 because coverage is incomplete rather than strong-with-few-gaps.	3 / 5
Distinctiveness Conflict Risk	"Bloom Credit integration" tied to the explicit trigger "interact with Bloom Credit data" carves out a clear, named niche with minimal risk of firing for an unrelated skill. It is not 4 because no meaningful overlap with sibling skills exists.	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/bloom-credit/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.