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

Blog Docs Log in Get started

wb

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

Quality

65%

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

Quality

Content

67%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 a well-structured, mostly executable guide to driving W&B via the Membrane CLI with a solid connection/polling workflow. Trimming the background intro and resolving the dangling "Step 2" reference would sharpen it.

Suggestions

Delete or condense the opening paragraph explaining what W&B is and who uses it — Claude already knows this; lead directly with the integration task.

Define "Step 2" explicitly (the doc skips from READY/Step 2 to "Searching for actions") or remove the dangling cross-reference so the workflow is unambiguous.

Move the proxy flags table and the nested clientAction state details into a separate reference file to slim the main SKILL.md overview.

Dimension	Reasoning	Score
Conciseness	The intro paragraph ("Weights & Biases (W&B) is a platform for tracking and visualizing machine learning experiments... improve model reproducibility.") over-explains what W&B is — background Claude already knows — and the "rather than auth plumbing" commentary is padded, though the command reference itself is tight.	3 / 5
Actionability	Provides concrete, executable commands (npm install, membrane login, connection ensure, action run, request) with a flags table; minor gaps are placeholders like CONNECTION_ID, <actionId>, and intent=QUERY that the user must substitute.	4 / 5
Workflow Clarity	The connect step is sequenced with an explicit poll/state-check feedback loop (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR → re-poll), but the referenced "Step 2" is undefined and numbering ("1b") is loose, leaving a minor clarity gap.	4 / 5
Progressive Disclosure	A single self-contained file with clear section headers and no nested references; at ~140 lines the dense inline clientAction detail and proxy flags table could be split into a reference file, but overall organization is good.	4 / 5
	Total	15 / 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 answers both what and when and anchors on a distinct platform (W&B), but its actions and trigger terms are generic and narrow. Adding concrete W&B verbs and synonyms (runs, metrics, experiments, wandb) would lift it.

Suggestions

Replace generic verbs with concrete W&B actions, e.g. "Track experiment runs, log metrics, and manage artifacts" instead of "Manage data, records, and automate workflows".

Broaden the trigger clause to include natural synonyms users say, e.g. "Use when the user wants to track experiments, log metrics, compare runs, or interact with Weights & Biases (W&B / wandb)."

Dimension	Reasoning	Score
Specificity	Quotes "Manage data, records, and automate workflows" name the W&B domain and list a few actions, but the verbs are generic ("manage", "automate") rather than concrete W&B operations like tracking runs or logging metrics.	3 / 5
Completeness	States the "what" ("W&B integration. Manage data, records, and automate workflows.") and an explicit "when" ("Use when the user wants to interact with W&B data."), though the trigger is narrow and could name more scenarios.	4 / 5
Trigger Term Quality	Uses the natural term "W&B data" but misses common synonyms and variations a user might say, such as "Weights & Biases", "experiments", "runs", "metrics", or "wandb".	3 / 5
Distinctiveness Conflict Risk	Names a specific platform niche (W&B) with a distinct trigger term, giving low conflict risk; minor overlap comes from the generic "data, records" wording.	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/wb/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.