Name: bigml
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

bigml

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

Quality

68%

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

Quality

Content

75%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 concrete Membrane CLI commands and a clear connection workflow including state-based polling, but it carries some padded introductory prose and an inline actions table that would benefit from extraction. Strong, executable guidance overall.

Suggestions

Trim the introductory paragraph explaining what BigML is and the bare Overview resource list; Claude already knows this and it adds tokens without guidance value.

Fix the broken step numbering ('skip to Step 2' references a non-existent Step 2 header) so the workflow sequence is unambiguous.

Move the large popular-actions table into a separate reference file (e.g. references/actions.md) and link to it from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and tables, but the opening paragraph ('BigML is a Machine Learning platform as a service...') and the bare Overview resource list explain things Claude already knows, so it could be tightened.	3 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) with flags explained and a popular-actions table, fully covering the common cases.	5 / 5
Workflow Clarity	The connect-then-poll-then-search-then-run sequence is clear with a state-based feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED), but the step numbering is broken ('skip to Step 2' with no Step 2 header) and post-run validation is implicit.	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers and no nested references; however the skill is well over 50 lines with a large inline popular-actions table that could live in a separate reference file, leaving minor organization gaps.	4 / 5
	Total	16 / 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 is third-person, includes an explicit 'Use when' trigger, and is anchored to a distinct platform (BigML), but its capability verbs are generic and it lacks richer trigger synonyms. Solid but not exemplary.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete BigML-specific actions like 'create datasets, train models, run predictions, and evaluate ensembles'.

Expand trigger terms with natural variations users might say, e.g. 'BigML datasets, models, predictions, evaluations, or ensembles'.

Tie the 'when' clause to specific BigML resource types so the trigger is more precise.

Dimension	Reasoning	Score
Specificity	It names the domain (BigML) and a few actions ('Manage data, records, and automate workflows'), but the actions are generic and not comprehensive, matching the anchor for naming a domain with 1-2 concrete actions.	3 / 5
Completeness	Both 'what' (BigML integration managing data/records/workflows) and 'when' ('Use when the user wants to interact with BigML data') are present; the 'when' is explicit but the 'what' is somewhat generic, so it sits at 4 rather than 5.	4 / 5
Trigger Term Quality	'BigML' and 'interact with BigML data' are relevant natural terms, but common variations or synonyms are missing, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'BigML' is a specific named platform giving a clear niche with minimal conflict risk, though the generic 'manage data, records' verbs leave minor overlap risk, placing it at 4.	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/bigml/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.