Tessl • The management layer for AI agent skills

The content is a solid, largely executable guide to driving BICS through the Membrane CLI, with good state-machine handling for connection setup. Its main weaknesses are a padded overview section and an inconsistent step-numbering scheme that references a nonexistent "Step 2".

Suggestions

Cut the "BICS Overview" bullet tree and the platform-introduction paragraph; replace with one sentence, since the actionable value is all in the CLI workflow.

Fix the broken "skip to **Step 2**" cross-references by labeling the actual following sections (e.g. "Step 2: Discover and run actions") or removing the numbering.

Merge "Popular actions" into "Searching for actions" — it currently duplicates the same `membrane action list` invocation without adding examples.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI guidance, but the opening "BICS is a communication platform used by international mobile operators. It facilitates global data and voice services, enabling roaming and interconnectivity." and the "BICS Overview" bullet tree capped by "Use action names and parameters as needed." are padded sections that add no executable value and could be trimmed.	3 / 5
Actionability	Concrete, mostly copy-paste-ready commands throughout ("membrane connection ensure \"https://www.bics.com/\" --json", "membrane action run <actionId> --connectionId=CONNECTION_ID --input '{\"key\": \"value\"}' --json", plus a proxy flags table). Minor gaps: "skip to Step 2" points at a step that is never defined, and "membrane login --tenant --clientName=<agentType>" leaves --tenant without a value.	4 / 5
Workflow Clarity	A clear sequence (install → login → connection ensure → poll → search actions → run) with explicit state-based checkpoints (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a re-poll feedback loop after user action. Not 5 because the "Step 2" cross-reference is broken, leaving the sequence slightly inconsistent; no destructive/batch operations apply to cap it at 3.	4 / 5
Progressive Disclosure	A single well-sectioned SKILL.md with no bundle files, no nested references, and clear section headers; "Popular actions" merely restates the already-shown "membrane action list" command, a minor organization gap that keeps it below 5.	4 / 5
	Total	15 / 20 Passed

Description

57%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 has an explicit when-clause and a distinctive product name, but describes the capability in generic boilerplate ("Manage data, records, and automate workflows") rather than concrete BICS-specific actions. It reads like a template applied across many integrations rather than a description tailored to BICS.

Suggestions

Replace the generic actions with concrete BICS capabilities (e.g. roaming reports, voice/data interconnect queries, messaging records) so the what-clause is specific.

Expand trigger terms beyond the product name to include natural synonyms a user would say, such as roaming, interconnect, or international carrier messaging.

Make the when-clause more specific than "interact with BICS data" — e.g. "Use when the user asks about BICS roaming, interconnect, or carrier messaging data".

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the BICS domain but the actions are generic placeholders, not concrete BICS operations — matching the anchor "Names the domain but actions are minimal or generic" (e.g. "Processes PDF files"). Not 3 because no specific, concrete action is actually described.	2 / 5
Completeness	Both parts are explicitly present: the what ("BICS integration. Manage data, records, and automate workflows.") and the when ("Use when the user wants to interact with BICS data."), with the when somewhat generic — matching "Has both 'what' and 'when'; 'when' could be more explicit or specific". Not 5 because the trigger phrases are not concrete, and not 3 because the when-clause is explicit rather than implied.	4 / 5
Trigger Term Quality	"BICS" is a relevant, distinctive keyword, but common variations and synonyms (roaming, interconnect, telecom messaging) are missing, and "data", "records", "workflows" are generic rather than natural trigger phrases — fitting "Some relevant keywords but missing common variations or synonyms". Not 4 because keyword coverage beyond the product name is thin.	3 / 5
Distinctiveness Conflict Risk	"BICS" carves out a clear niche with minimal conflict, but the generic tail "Manage data, records, and automate workflows" could fire on generic data-management requests that overlap other integration skills — matching "Mostly distinct; minor overlap risk". Not 5 because of that residual overlap from the generic action list.	4 / 5
	Total	13 / 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
Revision: f484c82

Reviewed: 16 days ago

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.

bics

Table of Contents

Is this your skill?