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

bizimply

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

Quality

64%

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

Quality

Content

63%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 highly actionable with concrete Membrane CLI commands and a clear connection workflow, but it is dragged down by a verbose inlined entity catalog and missing validation feedback for run actions. Splitting the catalog into a reference file and adding post-run verification would meaningfully improve it.

Suggestions

Move the ~150-entity catalog into a separate reference file (e.g. references/entities.md) and keep SKILL.md as an overview pointing to it, cutting the inlined bulk.

Add an explicit validate/verify step after 'membrane action run' (e.g. re-query or check the output state) so destructive/batch operations have a feedback loop.

Make the 'Popular actions' section name a few concrete high-value actions instead of restating the discovery command, and fix the 'Step 2' cross-reference so the workflow numbering is coherent.

Dimension	Reasoning	Score
Conciseness	Most of the operational guidance is efficient, but the ~150-item bulleted entity catalog (Locations through Custom Reports) is heavy token padding that Claude could discover via 'membrane action list', matching 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the lean level-4.	3 / 5
Actionability	Concrete, copy-paste-ready bash commands cover install, login, connection ensure, polling, action list/run, and proxy requests with a flag table — mostly executable, with minor gaps such as unresolved CONNECTION_ID/actionId placeholders and a 'Popular actions' section that just restates the list command instead of naming actions.	4 / 5
Workflow Clarity	The connect-to-run sequence is clearly laid out with state checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and polling guidance; minor gaps include the dangling 'Step 2' reference and no explicit validate-after-run feedback loop, so it sits at level 4 rather than 5.	4 / 5
Progressive Disclosure	Headers give reasonable structure, but with no bundle files the large entity catalog is inlined bulk content that would be better placed in a separate reference file, and the only external pointer is the docs URL — matching 'some structure but could be better organized; content that should be separate is inline'.	3 / 5
	Total	14 / 20 Passed

Description

66%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 identifies a distinct niche (Bizimply) and answers both what and when in third person, but the capability phrasing is generic and trigger-term coverage is thin. Tightening the action list and adding synonym/file-extension triggers would lift specificity and trigger quality.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Bizimply actions such as 'create schedules, pull time-and-attendance records, and run payroll' to raise specificity.

Broaden the 'Use when...' clause with natural synonyms users actually say, e.g. 'Use when the user wants to manage Bizimply schedules, attendance, payroll, or HR data'.

Keep the third-person voice but make the 'when' more explicit by listing the concrete scenarios that should trigger the skill.

Dimension	Reasoning	Score
Specificity	Names the domain (Bizimply) and a couple of actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete — closer to the 1-2-concrete-actions-but-not-comprehensive anchor than to level 4's several specific actions.	3 / 5
Completeness	It has both a 'what' ('Bizimply integration. Manage data, records, and automate workflows') and a 'when' ('Use when the user wants to interact with Bizimply data'), but the 'when' could be more explicit/specific, matching the level-4 anchor rather than the fully concrete level-5.	4 / 5
Trigger Term Quality	The only natural trigger phrase is 'Bizimply data' in the 'Use when the user wants to interact with Bizimply data' clause; relevant but missing common variations or synonyms, so it does not reach level 4's 'good keyword coverage'.	3 / 5
Distinctiveness Conflict Risk	Bizimply is a specifically named platform with distinct triggers ('interact with Bizimply data'), giving a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	15 / 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/bizimply/SKILL.md
Commit: f484c82

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