Name: moskit
Rating: 67.2 (1 reviews)
Author: membranedev

moskit

Moskit integration. Manage Organizations, Activities, Notes, Files, Pipelines, Users and more. Use when the user wants to interact with Moskit data.

Quality

81%

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

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 body is highly actionable with executable commands and a well-sequenced, validation-aware connection workflow. The main weaknesses are a small amount of marketing prose that could be trimmed and slightly loose step numbering ("Step 2"/"1b") that hurts navigation.

Suggestions

Trim the opening "Moskit is a session replay..." marketing paragraph to one sentence or remove it, since Claude does not need the product pitch to use the integration.

Fix the step labeling: either number the workflow sections consistently (1, 2, 3) or remove the dangling "skip to Step 2" / "1b" references so navigation is unambiguous.

Add a short verification cue before running actions (e.g., confirm the returned connection is READY and the actionId resolves) to strengthen the feedback loop for destructive/batch operations.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, executable command blocks, but the opening marketing paragraph ("Moskit is a session replay and product analytics tool... improve product adoption") and lines like "so you can focus on the integration logic rather than auth plumbing" are minor over-explanation that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands covering the full workflow (install, login, connection ensure/get with --wait, action list/run, request proxy) plus a concrete options table, satisfying the common cases.	5 / 5
Workflow Clarity	The install → authenticate → connect → poll-until-ready → handle client actions → search → run/proxy sequence has explicit validation checkpoints (state checks, --wait polling, error-state handling), but the "skip to Step 2" and "1b" labels reference headers that are not clearly numbered, leaving minor navigation gaps.	4 / 5
Progressive Disclosure	No bundle files exist and all content lives in one ~145-line file, but it is well-organized into clear sections (Overview, Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices); some inline material (the detailed clientAction state machine, proxy options) could optionally move to references but reads fine inline.	4 / 5
	Total	17 / 20 Passed

Description

80%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 clearly answers both "what" and "when" and is highly distinct, but it relies on a single generic verb and a narrow set of trigger terms. Expanding action verbs and natural-language synonyms would lift specificity and trigger quality.

Suggestions

Replace the single verb "Manage" with a few distinct concrete actions (e.g., "Create and update Organizations, log Activities and Notes, manage Pipelines and Users") to broaden specificity.

Add natural trigger synonyms users might say beyond just "Moskit data", such as "Moskit CRM", "contacts", "deals", or "sales pipeline".

Consider naming the "and more" tail concretely instead of leaving it open-ended, so the scope is unambiguous.

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Activities, Notes, Files, Pipelines, Users and more" lists several concrete entity types, but they all sit under the single generic verb "Manage", leaving minor coverage gaps versus fully distinct actions.	4 / 5
Completeness	It explicitly states both what it does ("Manage Organizations, Activities, Notes, Files, Pipelines, Users...") and when to use it ("Use when the user wants to interact with Moskit data"), with a concrete trigger phrase.	5 / 5
Trigger Term Quality	The only natural trigger keyword is "Moskit" ("Use when the user wants to interact with Moskit data"); common variations a user might say (CRM, contacts, sales pipeline, deals) are missing.	3 / 5
Distinctiveness Conflict Risk	"Moskit integration" tied to "interact with Moskit data" carves a clear niche around a specific proprietary tool with minimal overlap risk against other skills.	5 / 5
	Total	17 / 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/moskit/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.