Name: companyhub
Rating: 52 (1 reviews)
Author: membranedev

companyhub

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

Quality

57%

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

Quality

Content

57%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 provides concrete, executable Membrane CLI commands and a clear connection-state workflow with feedback loops. It is held back by an unnecessary CRM intro, an inlined entity dump, a dangling Step 2 reference, and missing validation guidance for destructive record operations.

Suggestions

Remove the introductory paragraph explaining what CompanyHub/CRM is, and move the long entity list into a separate reference file that SKILL.md points to.

Add a validation/verification checkpoint for destructive batch operations (e.g. confirm record IDs and dry-run before `delete-records`, then verify the deletion count).

Fix the dangling "skip to Step 2" reference by labeling the action-search/run sections as Step 2, or remove the cross-reference.

Dimension	Reasoning	Score
Conciseness	The CLI instruction sections are lean and actionable, but the opening paragraph explaining what a CRM is and the ~45-item inlined entity list are unnecessary padding Claude does not need, matching the "mostly efficient but includes some unnecessary explanation" anchor.	3 / 5
Actionability	Copy-paste ready commands (npm install, membrane login, connection ensure, action list/run, request) cover the common cases with a popular-actions table, with only minor gaps such as no concrete parameterized example for filter-records.	4 / 5
Workflow Clarity	The connection setup has explicit state branching and a poll-again feedback loop, but the "skip to Step 2" reference dangles (no Step 2 header), and destructive/batch operations like delete-records have no validation/verification guidance, which caps this at 3 per the rubric.	3 / 5
Progressive Disclosure	Section structure is present and coherent, but at ~205 lines all content (including the long entity list and action reference table) is inlined with no external references that could offload the bulk, matching the "some structure but content that should be separate is inline" anchor.	3 / 5
	Total	13 / 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 correctly identifies the named product and includes an explicit Use-when clause, satisfying both what and when. It is weakened by generic action verbs and missing natural CRM trigger terms (contacts, deals, leads).

Suggestions

Replace generic verbs with concrete CRM actions, e.g. "Create and update contacts, manage deals and pipelines, automate sales workflows."

Add natural trigger terms users would say, such as "contacts", "deals", "leads", "CRM", or "sales pipeline".

Make the Use-when clause more specific, e.g. "Use when the user wants to manage CompanyHub contacts, deals, companies, or sales pipelines."

Dimension	Reasoning	Score
Specificity	The description names the domain (CompanyHub) but the actions "Manage data, records, and automate workflows" are generic verbs rather than concrete CRM actions like create leads or update deals, matching the anchor where actions are minimal or generic.	2 / 5
Completeness	Both the "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with CompanyHub data") are present, though the trigger clause is somewhat generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	"CompanyHub" is a relevant keyword but the surrounding terms ("data", "records", "workflows") are generic, and common natural CRM terms like contacts, deals, leads, or pipeline are missing.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "CompanyHub" gives it a clear niche with minimal conflict risk against other skills, though the generic action verbs leave slight overlap with broad data-management skills.	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/companyhub/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.