Name: brilliant-directories
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

brilliant-directories

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

Quality

61%

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/brilliant-directories/SKILL.md

Quality

Content

57%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 is highly actionable with strong connection/action command examples and good auth-state checkpoints, but it carries an undifferentiated entity list, lacks destructive-operation validation, and keeps reference material inline instead of splitting it into bundle files.

Suggestions

Add an explicit confirmation/validation step before running delete actions (e.g. verify the record exists and confirm with the user before delete-user/delete-post).

Move the full entity-type list and the popular-actions table into a references/ file (e.g. ACTIONS.md) and link to it from SKILL.md, keeping only the quick-start flow inline.

Trim the bare entity bullet list or annotate each entry; an undifferentiated 40-item list adds tokens without actionable guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly operational, but the ~40-item undifferentiated entity bullet list ("Member", "Form", "Page", ...) with no descriptions and prose restating how Membrane auth works add padding that could be trimmed.	3 / 5
Actionability	Concrete copy-paste commands cover install, login, connection ensure, action list/run, and proxy requests with real flags, plus a popular-actions table; minor gaps remain (CONNECTION_ID/QUERY placeholders, no example --input payload for a real action).	4 / 5
Workflow Clarity	The connection flow is well-sequenced with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED), but destructive actions (delete-user, delete-post, delete-lead, delete-review) are listed with no validation or confirmation step, which caps workflow clarity at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	Sections are clearly headed, but everything is inlined into SKILL.md with no bundle files; the large entity list and full actions table are reference-grade content that should live in separate files with clearly signaled links.	3 / 5
	Total	13 / 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 cleanly answers both what and when in third person and is highly distinct, but its action verbs are generic and it omits the natural synonyms (members, listings, posts) users would actually invoke.

Suggestions

Replace generic verbs with concrete actions the skill performs, e.g. "search, create, update, and delete members, posts, leads, and reviews".

Expand the trigger clause with natural user phrasings like "when the user mentions Brilliant Directories, directory members, listings, posts, or reviews".

Tighten the trigger to mention the directory/membership-website context that distinguishes this from a generic data skill.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Brilliant Directories domain plus 2-3 actions, but those actions are generic ("manage", "automate") rather than the concrete CRUD/listing verbs the skill actually supports, so coverage is not comprehensive.	3 / 5
Completeness	It states both what ("Brilliant Directories integration. Manage data, records, and automate workflows.") and when ("Use when the user wants to interact with Brilliant Directories data") with an explicit trigger clause; the 'when' is present but could name more concrete triggering scenarios.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Brilliant Directories data" plus "Brilliant Directories integration" give the core natural term, but common variations (members, listings, posts, directory website) that users would actually say are missing.	3 / 5
Distinctiveness Conflict Risk	"Brilliant Directories" is a distinct named platform with a clear niche (directory/membership websites) and a platform-specific trigger, so conflict with other skills is minimal.	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/brilliant-directories/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.