Name: jobnimbus
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

jobnimbus

Jobnimbus integration. Manage Organizations, Pipelines, Users, Filters. Use when the user wants to interact with Jobnimbus data.

Quality

61%

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

Quality

Content

56%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 delivers strong, executable Membrane CLI guidance with a well-sequenced connection workflow and helpful state-handling checkpoints. Its chief drawback is the bloated, partly-duplicated entity list that wastes tokens and the absence of any split-out reference material.

Suggestions

Remove or drastically trim the ~120-item entity list, including the duplicated "Report", "Integration", and "Forecast" entries; keep only entities the skill meaningfully acts on.

Move the full popular-actions table and entity catalog into a separate reference file (e.g. ACTIONS.md) referenced from the body, so SKILL.md stays a lean overview.

Tighten the intro paragraph that explains what JobNimbus is, since Claude can infer CRM basics, and reserve detail for Jobnimbus-specific behavior.

Dimension	Reasoning	Score
Conciseness	The ~120-item bulleted entity list ("Contact", "Job", "Estimate", ... "Web App") with duplicated entries ("Report", "Integration", "Forecast" each appear twice) is a large padded section that adds little actionable value, making the body noticeably verbose despite lean CLI instructions.	2 / 5
Actionability	Concrete, copy-paste-ready commands appear throughout ("npm install -g @membranehq/cli@latest", "membrane connection ensure 'https://www.jobnimbus.com/' --json", "membrane action run <actionId> --connectionId=CONNECTION_ID --input '{\"key\": \"value\"}' --json"), with only minor gaps such as unfilled placeholders.	4 / 5
Workflow Clarity	The install → authenticate → connect → search → run/proxy sequence is clear, with real checkpoints (poll until state is READY, handle CLIENT_ACTION_REQUIRED, inspect CONFIGURATION_ERROR/SETUP_FAILED), though it stops short of a fully explicit validate-fix-retry checklist.	4 / 5
Progressive Disclosure	Section headers give reasonable structure, but with no bundle files present the large inlined entity list and full popular-actions table are content that would be better split into separate reference files, leaving organization only partly realized.	3 / 5
	Total	13 / 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 names the product, lists a few manageable entities, and includes an explicit "Use when" trigger, giving it solid completeness and strong distinctiveness. Its main weakness is limited action specificity and sparse trigger-term variety.

Suggestions

Replace the generic verb "Manage" with the concrete operations the skill actually performs (e.g., "Create, update, list, and retrieve" Organizations, Pipelines, Users, Filters) to raise specificity.

Expand the trigger clause with natural phrasings a user would say, e.g., "Use when the user wants to query Jobnimbus contacts, jobs, or tasks, or interact with Jobnimbus CRM data."

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Pipelines, Users, Filters" names the domain and several entities, but the single generic verb "Manage" applied across four nouns offers only modest action specificity rather than a comprehensive set of concrete operations.	3 / 5
Completeness	It states both a "what" ("Manage Organizations, Pipelines, Users, Filters") and an explicit "when" ("Use when the user wants to interact with Jobnimbus data"), but the trigger clause is somewhat generic and could be more concrete, landing above the midpoint rather than at the top.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Jobnimbus data" supplies a natural trigger phrase around the product name, but coverage is thin with no synonyms or variant phrasings a user might actually say.	3 / 5
Distinctiveness Conflict Risk	"Jobnimbus" is a specific named product with a clearly defined niche, so the description is highly distinct and unlikely to trigger for an unrelated skill.	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/jobnimbus/SKILL.md
Commit: f484c82

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