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

boloforms

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

Quality

Content

68%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 comprehensive executable Membrane CLI commands and a strong connection-state workflow, but it carries some padded prose and omits validation/verification steps for destructive action runs and proxy calls. Organization is good for a single-file skill.

Suggestions

Add a validation/verification step before and after destructive actions and proxy writes (e.g. confirm the action's outputSchema, dry-run reads before writes, verify the returned output) to satisfy the destructive-operations feedback-loop requirement.

Trim rhetorical padding such as "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection" to improve token efficiency.

Optionally move the popular-actions table and proxy flag reference into separate reference files linked from the overview to strengthen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command- and table-based instruction, but padded sentences like "so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection", and "This will burn less tokens and make communication more secure" could be trimmed.	3 / 5
Actionability	Fully executable, copy-paste-ready commands cover install, login, connection ensure/wait, action list, action run (with JSON input), and proxy requests, plus a table of popular actions with concrete keys.	5 / 5
Workflow Clarity	The connection setup has a clear sequence with state-based polling checkpoints and feedback loops, but running or proxying potentially destructive/outward-facing actions (e.g. send-template-for-signing, POST/DELETE) lacks validation or verification steps, capping clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	A single well-organized SKILL.md with clear section headers and no nested references; content is appropriately inline for a single integration skill, though the popular-actions and proxy-flag tables could optionally live in separate reference files.	4 / 5
	Total	15 / 20 Passed

Description

61%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 "Use when" trigger and names a distinct product, but its capability list is generic ("manage data, records, automate workflows") rather than concrete Boloforms-specific actions. Tightening the action verbs would lift specificity and trigger-term quality.

Suggestions

Replace generic verbs with concrete Boloforms capabilities, e.g. "Create forms and surveys, retrieve form responses, send templates for e-signature, and list documents."

Add natural trigger terms users would say, such as "forms", "form responses", "templates", and "signing".

Keep the explicit "Use when..." clause but tie the trigger to those concrete nouns rather than the vague "interact with Boloforms data".

Dimension	Reasoning	Score
Specificity	Names the domain (Boloforms) but the listed actions — "Manage data, records, and automate workflows" — are minimal and generic rather than concrete capabilities like create forms or collect responses.	2 / 5
Completeness	Both a "what" (manage data, records, automate workflows) and an explicit "when" ("Use when the user wants to interact with Boloforms data") are present, though the what is generic and could be more specific.	4 / 5
Trigger Term Quality	Includes the specific app name and phrase "interact with Boloforms data", but lacks common natural variations users would say such as forms, responses, templates, or signing.	3 / 5
Distinctiveness Conflict Risk	Boloforms is a specific named product with a dedicated trigger ("interact with Boloforms data"), giving it a clear niche with minimal overlap risk against other skills.	5 / 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/boloforms/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.