CtrlK
BlogDocsLog inGet started
Tessl Logo

bundleiq

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

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/bundleiq/SKILL.md
SKILL.md
Quality
Evals
Security

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 body is highly actionable with executable CLI commands and a well-handled connection state machine including polling feedback loops. Its main weaknesses are an unnecessary introductory paragraph and inconsistent step numbering that slightly muddies the workflow sequence.

Suggestions

Trim or remove the opening "BundleIQ is a knowledge management platform..." paragraph; it explains concepts Claude already knows and adds no integration guidance.

Fix the workflow numbering: renumber the connection steps consistently (1, 2, 3...) and resolve the orphaned "1b" heading so "Step 2" references are unambiguous.

Replace the generic "Use action names and parameters as needed." under BundleIQ Overview with a concrete pointer to the "membrane action list" discovery step below.

DimensionReasoningScore

Conciseness

Mostly efficient CLI command blocks, but the opening paragraph explaining what BundleIQ is and who uses it pads content Claude does not need, fitting the mostly-efficient-but-could-be-tightened anchor.

3 / 5

Actionability

Provides fully executable, copy-paste-ready commands for connect, action discovery, action run, and proxy requests plus a concrete flag table, covering the common cases.

5 / 5

Workflow Clarity

The connection flow has clear state handling and polling feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED, re-poll after action), but inconsistent step numbering (an orphaned "1b" and a referenced "Step 2" without numbered steps) leaves minor sequencing gaps.

4 / 5

Progressive Disclosure

No bundle files exist; the single-file skill is organized into clear sections (Overview, Working with BundleIQ, Popular actions, Best practices) with action details appropriately deferred to "membrane action list", though some inlined material could be separated.

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 product niche. Its weakness is generic verb choices ("Manage data, records, automate workflows") that lack concrete, natural-sounding capabilities and trigger synonyms.

Suggestions

Replace generic verbs with concrete BundleIQ capabilities the user would actually name (e.g., "search and retrieve records", "create and tag documents", "query workspaces").

Add natural trigger phrases and synonyms a user would say, such as "BundleIQ records", "search BundleIQ", or "query BundleIQ data".

Tighten the "Use when" clause to concrete triggers like "Use when the user wants to search, retrieve, or manage BundleIQ records and documents."

DimensionReasoningScore

Specificity

Names the BundleIQ domain and a couple of actions ("Manage data, records, and automate workflows"), but the verbs are generic rather than concrete capabilities, matching the 1-2 actions-but-not-comprehensive anchor.

3 / 5

Completeness

Provides both a clear "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with BundleIQ data"), though the trigger is somewhat generic rather than concrete.

4 / 5

Trigger Term Quality

Includes some relevant keywords ("data", "records", "workflows", "BundleIQ data") but lacks natural user phrases and format/synonym variations, fitting the some-relevant-keywords-but-missing-variations anchor.

3 / 5

Distinctiveness Conflict Risk

"BundleIQ integration" targets a named product niche with mostly distinct triggers and only minor overlap risk with general data-management skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.