Name: businesslogic
Rating: 48.8 (1 reviews)
Author: membranedev

businesslogic

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

Quality

53%

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

Quality

Content

45%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 operational sections (CLI install, auth, connections, actions, proxy) are genuinely actionable with executable commands and a clear connection workflow, but the document is dominated by a large padded entity list that destroys token efficiency and leaves no progressive disclosure structure.

Suggestions

Remove the ~390-line bulleted 'entity' list (lines 23-412); it is pure padding unrelated to BusinessLogic actions and severely wastes the context window.

Add at least one fully worked end-to-end example showing an actual action invocation with real input parameters and the expected output JSON.

Move the action/schema reference detail into a separate reference file (or rely on `membrane action list` at runtime) and link to it from SKILL.md so the body stays a concise overview.

Dimension	Reasoning	Score
Conciseness	Roughly 390 lines (lines 23-412) are a padded bulleted list of pseudo-entities including nonsensical entries ('Love', 'Death', 'Zero', 'Everything', 'Nothing') that earn no information value, matching the 'severely verbose; heavily padded' anchor despite the lean operational sections elsewhere.	1 / 5
Actionability	Provides concrete, executable bash commands for install, login, connection ensure, action list/run, and proxy requests with a flags table, but lacks a fully worked end-to-end example with real parameters and output, keeping it below the top anchor.	4 / 5
Workflow Clarity	The connection setup is sequenced with explicit state checkpoints (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a polling feedback loop, but error recovery stops at 'check the error field' without a fix-and-retry cycle, so it falls short of the top anchor.	4 / 5
Progressive Disclosure	No bundle files exist and there are no references to separate files; the skill is a monolithic document whose bulk is an inlined 390-line list that does not belong inline, fitting the 'minimal structure; content inlined that should be separate' anchor.	2 / 5
	Total	11 / 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 a solid, third-person statement that covers both what the skill does and when to use it with an explicit trigger clause. Its main weakness is generic action verbs and limited keyword variation rather than a structural deficiency.

Dimension	Reasoning	Score
Specificity	Names the domain ('BusinessLogic integration') and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, matching the anchor that lists domain plus 1-2 actions without comprehensive coverage.	3 / 5
Completeness	Answers both what ('Manage data, records, and automate workflows') and when via an explicit 'Use when the user wants to interact with BusinessLogic data' clause; the 'what' is moderately specific rather than fully concrete, so it sits below the top anchor.	4 / 5
Trigger Term Quality	Includes relevant terms ('BusinessLogic', 'data', 'records', 'workflows') but is missing common variations, synonyms, or file extensions, fitting the anchor for some relevant keywords with gaps.	3 / 5
Distinctiveness Conflict Risk	The named product 'BusinessLogic' gives it a clear niche with minimal conflict risk, though the generic action verbs ('manage data') leave minor overlap risk with related data skills.	4 / 5
	Total	14 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (544 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: membranedev/application-skills
Path: skills/businesslogic/SKILL.md
Commit: f484c82

Reviewed: 4 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.