CtrlK
BlogDocsLog inGet started
Tessl Logo

morningmate

Morningmate integration. Manage Users, Organizations. Use when the user wants to interact with Morningmate data.

61

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/morningmate/SKILL.md
SKILL.md
Quality
Evals
Security

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 a tight, executable CLI integration guide with strong actionability and a well-checkpointed connection workflow. Minor conciseness padding and a dangling 'Step 2' reference keep it just short of top marks, and the self-contained single-file structure is well organized.

DimensionReasoningScore

Conciseness

The body is mostly lean command-and-code-driven prose with only minor over-explanation such as 'so you can focus on the integration logic rather than auth plumbing', matching the 'efficient; minor instances of over-explanation that could be trimmed' anchor rather than the fully lean 5.

4 / 5

Actionability

It provides copy-paste-ready, executable commands throughout (npm install, membrane login, connection ensure, action list/run, request with a full flag table), covering the common cases, matching the 'fully executable; copy-paste ready' anchor.

5 / 5

Workflow Clarity

The connection workflow is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and polling guidance, but the dangling 'Step 2' reference and absent validation feedback loop for action runs leave minor gaps, matching 'clear sequence with most checkpoints present' rather than the explicit-loop 5.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections (Overview, Authentication, Connecting, Searching, Popular actions, Best practices) in a single self-contained file with no nested references, matching 'good structure; most content appropriately placed' though slightly above the simple-skill threshold.

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 pairs a clear 'what' with an explicit 'Use when' trigger and a distinct app name, but its action vocabulary ('Manage') is generic and its trigger/entity coverage is narrower than the body suggests. It lands in the mid-to-upper range across all four dimensions.

Suggestions

Replace the generic verb 'Manage' with specific verbs (e.g. 'Create, list, and update Users and Organizations').

Expand the trigger to mirror the body's scope, e.g. 'Use when the user wants to interact with Morningmate data such as tasks, reminders, habits, or routines.'

Add concrete trigger phrases users would say (e.g. 'Morningmate', 'morning routine', 'habits', 'journal entries') to improve keyword coverage.

DimensionReasoningScore

Specificity

The phrase 'Manage Users, Organizations' names the domain (Morningmate) and two concrete entity targets, but 'Manage' is a generic verb and coverage is narrow rather than comprehensive, matching the 'names domain and 1-2 concrete actions' anchor.

3 / 5

Completeness

It states both the 'what' ('Morningmate integration. Manage Users, Organizations.') and an explicit 'when' ('Use when the user wants to interact with Morningmate data'), but the trigger could be more specific, matching the 'has both what and when; when could be more explicit' anchor rather than the fully concrete 5.

4 / 5

Trigger Term Quality

It offers the natural phrase 'Use when the user wants to interact with Morningmate data' plus app/entity terms ('Morningmate', 'Users', 'Organizations'), but misses common variations or synonyms and the broad body-level concepts (tasks, habits, routines), fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The named app 'Morningmate' gives it a clear niche with low conflict risk, though the generic 'Manage Users, Organizations' actions leave minor overlap risk with other user-management skills, matching 'mostly distinct; minor overlap risk' rather than the fully-distinct 5.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.