Name: credit-repair-cloud
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

credit-repair-cloud

Credit Repair Cloud integration. Manage Users, Clients, Affiliates, Providers, Disputes, Products and more. Use when the user wants to interact with Credit Repair Cloud 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/credit-repair-cloud/SKILL.md

Quality

Content

56%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 skill delivers strong executable CLI guidance and a clear connection-setup workflow, but it is dragged down by a hugely padded, partially nonsensical entity list that wastes context. Tightening that list and moving bulk reference material to a separate file would substantially raise quality.

Suggestions

Remove or collapse the degenerate repeated-phrase entity list (lines 96-167); keep only genuine top-level entities and reference the full action catalog via 'membrane action list' rather than inlining it.

Add a short validation/verification step after 'membrane action run' for destructive or batch actions (e.g. confirm the returned output state or re-fetch the record) to satisfy the workflow feedback-loop expectation.

Expand the 'Popular actions' table beyond Affiliate and Lead/Client CRUD to reflect the breadth of entities advertised, or explicitly note that the table is illustrative and discovery via 'action list --intent' is the primary path.

Dimension	Reasoning	Score
Conciseness	The ~145-line entity list degenerates into absurd recursive repetitions ('Client Credit Report Item Analysis Result Analysis Result Analysis Result Analysis...'), burning tokens on strings Claude cannot meaningfully use.	2 / 5
Actionability	It provides copy-paste-ready CLI commands (install, login, connection ensure, action list/run, request proxy) with a flags table, covering the common workflow concretely.	4 / 5
Workflow Clarity	The connection setup is a clear sequenced state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED) with polling and recovery guidance, though action execution lacks an explicit post-run validation checkpoint.	4 / 5
Progressive Disclosure	It is a single self-contained file with reasonable section headers, but the massive inlined entity list is content that obstructs navigation rather than being organized or referenced out.	3 / 5
	Total	13 / 20 Passed

Description

71%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 the product and lists concrete entities while providing an explicit 'Use when' trigger, giving it solid completeness and distinctiveness. It loses points on trigger-term variety and on the generic 'Manage' verb that under-specifies the actual actions.

Dimension	Reasoning	Score
Specificity	Lists several concrete managed entities ('Users, Clients, Affiliates, Providers, Disputes, Products'), though the verb 'Manage' is generic rather than enumerating distinct actions per entity.	4 / 5
Completeness	It answers both 'what' (manage Users, Clients, Affiliates, etc.) and 'when' ('Use when the user wants to interact with Credit Repair Cloud data'), though the 'when' could be more specific.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with Credit Repair Cloud data' surfaces the product name as a natural trigger, but it lacks common synonyms or variations users might say.	3 / 5
Distinctiveness Conflict Risk	The named product 'Credit Repair Cloud' with its explicit trigger forms a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	16 / 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/credit-repair-cloud/SKILL.md
Commit: f484c82

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