Name: moesif
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

moesif

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

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/moesif/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.

The content is highly actionable with executable commands and a well-sequenced connection workflow that includes state-based validation checkpoints. Its main weaknesses are minor redundancy between action-listing sections and broken step numbering that slightly undermines workflow clarity.

Suggestions

Fix the step numbering: either add an explicit 'Step 1a' header or relabel '1b' and define the referenced 'Step 2' so the 'skip to Step 2' pointer resolves.

Merge the 'Searching for actions' and 'Popular actions' sections, which both demonstrate `action list --intent`, to remove redundancy and save tokens.

Consider moving the full proxy flag table and the `clientAction` schema breakdown into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient commands and tables, but there is redundancy (the 'Searching for actions' and 'Popular actions' sections both demonstrate `action list --intent`), a sparse bullet 'Overview' list, and a轻度 explanatory intro about what Moesif is; matching 'mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	The body provides copy-paste-ready commands for install, login, connection ensure/get, action list/run, and request proxying, plus a complete flag table, covering the common cases with executable specifics.	5 / 5
Workflow Clarity	A clear install→auth→connect→search→run sequence exists with explicit state validation (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop, but the step numbering is broken ('skip to Step 2' with no Step 2, '1b' with no explicit '1a'), leaving a minor gap.	4 / 5
Progressive Disclosure	The single self-contained file is well-organized with clear section headers and no nested references, which is good structure; at over 50 lines some material (full proxy flag table, clientAction schema detail) could arguably live in a reference file, so it is not a clean 5.	4 / 5
	Total	16 / 20 Passed

Description

61%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 pairs a 'what' with an explicit 'Use when...' trigger and targets a distinct niche, but its capability verbs ('manage data, records, automate workflows') are generic and lack concrete, specific actions. It is solid but could be sharper on specificity and trigger-term coverage.

Suggestions

Replace generic verbs with concrete Moesif capabilities, e.g. 'Query API events, users, and companies; set up alerts and dashboards; automate workflows'.

Add natural trigger phrases users would say, such as 'API analytics', 'API monitoring', or 'debug API requests', to broaden trigger-term coverage.

Make the 'when' clause enumerate concrete scenarios (e.g. 'Use when analyzing API traffic, debugging integration errors, or building API dashboards') rather than the generic 'interact with Moesif data'.

Dimension	Reasoning	Score
Specificity	The domain (Moesif) is named and three action phrases appear ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete like 'extract' or 'fill'; this matches the anchor where actions are minimal or generic.	2 / 5
Completeness	Both 'what' (Moesif integration, manage data/records, automate workflows) and 'when' ('Use when the user wants to interact with Moesif data') are present, but the 'when' trigger is somewhat generic rather than enumerating concrete scenarios, fitting the 'both present, when could be more explicit' anchor.	4 / 5
Trigger Term Quality	'Moesif' plus 'data', 'records', 'workflows' gives some relevant keywords, but it misses common synonyms or natural phrasing variations users might say, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Moesif is a specific named product niche with a distinct trigger ('interact with Moesif data'), giving minimal conflict risk with other skills, matching the clear-niche anchor.	5 / 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/moesif/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.