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

Blog Docs Log in Get started

moco

MOCO integration. Manage Organizations. Use when the user wants to interact with MOCO data.

Quality

72%

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

Quality

Content

82%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 content is a strong, actionable integration guide with executable commands and a well-designed connection state-machine workflow. Its main weaknesses are minor conciseness padding, a broken 'Step 2' cross-reference, and the absence of any external reference files for a skill that is moderately long.

Suggestions

Fix or remove the dangling 'skip to Step 2' reference and reconcile the inconsistent section numbering (e.g., the '1b' heading without a '1a' or '2') so the workflow sequence is unambiguous.

Trim the introductory paragraph explaining what MOCO is to one line, since Claude can infer the tool's purpose from the action list and API docs link.

Consider extracting the proxy flag table and full action-overview list into a reference file to improve progressive disclosure and reduce SKILL.md length.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and tight flag tables, but includes a few sentences explaining what MOCO is and minor explanatory padding that could be trimmed, matching the 'efficient; minor instances of over-explanation' anchor; not a 5 because of the introductory paragraph and occasional restatements.	4 / 5
Actionability	Provides copy-paste ready, fully executable commands throughout (install, login, connection ensure/get with --wait, action list/run with --input, request with a complete flag table) covering the common cases, matching the 'fully executable; copy-paste ready' anchor; not a 4 because guidance is concrete and complete rather than having notable gaps.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with a state machine (ensure -> poll --wait -> handle CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR -> READY) including feedback loops, matching the 'clear sequence with most checkpoints present' anchor; not a 5 because of the dangling 'skip to Step 2' reference (no labeled Step 2) and inconsistent '1b' numbering, and not a 3 because validation checkpoints are genuinely present.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections (install, auth, connecting, searching, running, proxy, best practices) with no nested references and manageable inline material, matching the 'good structure; most content appropriately placed' anchor; not a 5 because at ~156 lines some sub-topics could be split into reference files, and no bundle files are provided.	4 / 5
	Total	17 / 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 is functional, naming the MOCO domain with a clear 'Use when' trigger clause, but it is thin on concrete capabilities and natural trigger terms. Expanding the action list and trigger synonyms would lift specificity, trigger quality, and distinctiveness.

Suggestions

Replace the generic 'Manage Organizations' with the skill's actual concrete capabilities (e.g., time tracking, timesheet entries, projects, tasks, users) to improve specificity.

Add natural trigger phrases and synonyms users would say, such as 'MOCO time tracking', 'log hours', 'timesheet entries', or 'MOCO projects' to broaden trigger term coverage.

Tighten the 'Use when' clause with concrete triggers (e.g., 'Use when the user wants to track time, manage timesheets, or query MOCO projects and tasks') to reduce conflict risk with other org-management skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('MOCO integration') and one concrete action ('Manage Organizations'), but coverage is minimal and not comprehensive, matching the 'names domain and 1-2 concrete actions' anchor; not a 2 because it does state a concrete action rather than only naming the domain.	3 / 5
Completeness	Explicitly answers both 'what' ('MOCO integration. Manage Organizations.') and 'when' ('Use when the user wants to interact with MOCO data.'), but the 'when' is generic and could be more specific, matching the 'has both what and when; when could be more explicit' anchor; not a 5 because trigger phrases are not concrete and comprehensive.	4 / 5
Trigger Term Quality	Relevant keywords ('MOCO', 'MOCO data', 'Organizations') appear but common natural variations users would say (time tracking, projects, invoices, timesheets) are missing, matching the 'some relevant keywords but missing common variations' anchor; not a 4 because keyword coverage is thin.	3 / 5
Distinctiveness Conflict Risk	The named app 'MOCO' makes it mostly distinct with minor overlap risk, though 'Manage Organizations' is generic and could overlap with other org-management skills; not a 5 because the trigger ('interact with MOCO data') is broad and the action phrasing is generic.	4 / 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/moco/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.