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

Blog Docs Log in Get started

bics

BICS integration. Manage data, records, and automate workflows. Use when the user wants to interact with BICS 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/bics/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 delivers concrete, mostly-executable Membrane CLI guidance with a well-sequenced connection workflow and state-based checkpoints. Its main weaknesses are an undefined 'Step 2' reference and a monolithic single-file structure with no progressive disclosure into reference docs.

Suggestions

Define or link the referenced 'Step 2' (the action-discovery/running flow) so the connection -> usage handoff is unbroken.

Move the proxy flag reference table and the full clientAction schema into a separate REFERENCE.md, keeping SKILL.md as a lean overview with one-level-deep links.

Add an explicit verification step after running actions (e.g. check the output/HTTP status) to strengthen the feedback loop for batch or destructive operations.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands and tables with little concept over-explanation, though lines like 'so you can focus on the integration logic rather than auth plumbing' add mild padding that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready CLI commands with concrete flags and a flag reference table, but relies on placeholders like CONNECTION_ID and leaves some steps implied, keeping it just short of fully executable across all common cases.	4 / 5
Workflow Clarity	The connection flow is sequenced with explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop, but it references a 'Step 2' that is never defined, a navigation gap.	4 / 5
Progressive Disclosure	Content is well-organized under clear headers in a single SKILL.md with no bundle files, but the ~140-line body mixes overview, auth, and reference material that could be split into referenced files for cleaner navigation.	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 cleanly answers both what the skill does and when to use it, anchored to a distinct named platform, but relies on generic verbs ('manage', 'automate') and lacks concrete trigger variations or synonyms. It is solid but not exemplary.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Query BICS datasets, build dashboards, and automate data-flow schedules'.

Add natural trigger synonyms and formats users would actually say, e.g. 'Use when the user mentions BICS dashboards, datasets, schedules, or analytics reports'.

Tighten the 'when' clause with specific BICS objects (Analysis, Dashboard, Data flow) to reduce overlap with other data skills.

Dimension	Reasoning	Score
Specificity	The description names the domain and three verbs ('Manage data, records, and automate workflows'), but the actions are generic verbs rather than concrete capabilities, matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor.	3 / 5
Completeness	It states both a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with BICS data'), though the 'when' trigger is generic rather than concrete.	4 / 5
Trigger Term Quality	It includes 'BICS data' and 'interact with BICS data', but lacks synonyms, natural variations, or file/format triggers, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	BICS is a specific named platform with a distinct niche ('interact with BICS data'), giving low conflict risk, though the generic 'manage data/records' phrasing leaves minor overlap risk.	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/bics/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.