Name: bigid
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

bigid

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

Quality

64%

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/bigid/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 body is highly actionable with concrete, copy-paste Membrane CLI commands and a solid connection-readiness workflow. Its main weaknesses are the bloated inlined entity enumeration that burns tokens and the absence of any progressive-disclosure references to offload that bulk.

Suggestions

Move the ~200-line entity/"Data Source *" enumeration into a separate references/ file (e.g. ENTITIES.md) and link to it from the body, restoring token efficiency.

Add an explicit validation/feedback step for destructive or batch BigID operations (e.g. dry-run, confirm count, verify result) to lift workflow clarity toward 5.

Dimension	Reasoning	Score
Conciseness	The ~200-line enumerated entity/"Data Source *" bullet list is heavy padding that does not earn its tokens, even though the prose command sections are reasonably efficient; this matches 'noticeably verbose with padded sections' rather than the lean 4-5 anchors.	2 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every common case (install, login, connection ensure/get, action list/run, request proxy) plus a flags table, matching the 'fully executable, covers common cases' anchor.	5 / 5
Workflow Clarity	There is a clear install->auth->connect->search->run sequence with state-polling checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a --wait feedback loop, but no explicit validate-fix-retry checklist for destructive data operations, so it falls just short of 5.	4 / 5
Progressive Disclosure	The file has section headers and decent organization, but the large entity list is inlined content that clearly belongs in a separate reference file and there are no external references at all, matching 'some structure but content that should be separate is inline'.	3 / 5
	Total	14 / 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 is third-person, names the BigID domain, and includes an explicit 'Use when' trigger clause, so it clears the completeness bar. Its weakness is generic, non-concrete action language and thin keyword coverage beyond the product name.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete BigID-specific actions like 'discover and classify sensitive data, manage DSARs, and run retention workflows'.

Add natural trigger phrases and synonyms users actually say, e.g. 'Use when the user mentions BigID, data discovery, data subject access requests, or data privacy compliance.'

Dimension	Reasoning	Score
Specificity	Names the BigID domain and a few actions ('Manage data, records, and automate workflows'), but the actions are high-level and generic rather than concrete, so it is not comprehensive enough for a 4.	3 / 5
Completeness	It states both what it does ('Manage data, records, and automate workflows') and when to use it ('Use when the user wants to interact with BigID data'); the 'when' is explicit but could be more specific, so 4 rather than 5.	4 / 5
Trigger Term Quality	It includes the relevant terms 'BigID' and 'BigID data' in the trigger clause, but offers no natural synonyms or variations a user might say, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	BigID is a specific named product with a distinct trigger ('interact with BigID data'), giving it a clear niche with minimal conflict risk against other skills.	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/bigid/SKILL.md
Commit: f484c82

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