Name: mojotxt
Rating: 61.6 (1 reviews)
Author: membranedev

mojotxt

MojoTxt integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with MojoTxt data.

Quality

73%

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

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.

A highly actionable integration skill with copy-paste Membrane CLI commands and a clear connect→discover→run workflow including state-based branching. It is well-structured and mostly lean, with some inferable padding and no explicit validation feedback loop for the destructive proxy operations it exposes.

Suggestions

Trim inferable commentary such as 'so you can focus on the integration logic rather than auth plumbing' and the prose restating what each clientAction subfield means.

Add an explicit validation/checkpoint for proxy requests that mutate data (POST/PUT/DELETE) — e.g., verify the response status and confirm with the user before destructive calls — to satisfy the destructive-operation feedback-loop expectation.

Move the connection-state field walkthrough (clientAction.type sub-bullets) into a short reference table to tighten the main workflow.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes explanatory padding Claude could infer (e.g., 'Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing') and a somewhat lengthy clientAction field walkthrough.	3 / 5
Actionability	Provides copy-paste-ready, executable commands throughout (install, login, connection ensure, action list/run, proxy requests) with concrete flags and a parameter table covering the common cases.	5 / 5
Workflow Clarity	Clear sequenced flow from install → authenticate → connect → search/run with explicit state-based branching (READY/BUILDING/CLIENT_ACTION_REQUIRED) and polling guidance, though no explicit validate-then-retry feedback loop for the destructive proxy POST/DELETE requests it enables.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Overview, Working with MojoTxt, Popular actions, Best practices) with the body acting as a navigable overview; no bundle files exist so detail is appropriately inline, with only minor bulk that could be split out.	4 / 5
	Total	16 / 20 Passed

Description

71%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.

A solid, third-person description that names the domain and enumerates concrete managed entities with an explicit 'Use when' trigger. It is distinct and unlikely to conflict, though the trigger phrasing could be richer in natural user terms.

Suggestions

Add a few natural user-facing trigger phrases beyond the brand name (e.g., 'Use when the user wants to send SMS campaigns, manage contacts, or track keyword replies').

Replace the noun-list 'Manage Persons, Organizations, Deals, Leads, Projects, Activities' with verb-led actions (e.g., 'create, update, and search persons, deals, and campaigns') to sharpen specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (MojoTxt) and several concrete managed entities ('Persons, Organizations, Deals, Leads, Projects, Activities'), covering multiple specific actions, though the actions are nouns rather than verbs.	4 / 5
Completeness	Explicitly states both what ('Manage Persons, Organizations, Deals, Leads, Projects, Activities and more') and when ('Use when the user wants to interact with MojoTxt data'), with the 'when' present though somewhat generic.	4 / 5
Trigger Term Quality	Includes 'interact with MojoTxt data' as a trigger phrase, but relies heavily on the product name and generic terms; missing common synonyms or user-natural phrasing beyond the brand.	3 / 5
Distinctiveness Conflict Risk	The brand-specific 'MojoTxt' trigger carves a clear niche with minimal overlap risk against other skills; unlikely to fire for the wrong skill.	5 / 5
	Total	16 / 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/mojotxt/SKILL.md
Commit: f484c82

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