Name: schedule-it
Rating: 56.8 (1 reviews)
Author: membranedev

schedule-it

Schedule it integration. Manage Users, Roles, Organizations, Projects, Pipelines, Activities and more. Use when the user wants to interact with Schedule it data.

Quality

65%

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

Quality

Content

67%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 strongly actionable, well-sequenced integration guide with concrete Membrane CLI commands and a real connection-readiness feedback loop. It loses points mainly on conciseness (a padded intro and a duplicated command) and on progressive disclosure, since a fairly long single file inlines material that could be split out.

Suggestions

Cut the opening background paragraph ('Schedule It is a scheduling application...') and the explanatory Membrane auth prose; Claude already understands scheduling apps and credential refresh.

Remove the duplicate action-list command in 'Popular actions' (it already appears in 'Searching for actions') to save tokens and avoid drift.

Consider moving the proxy flags table and the connection-state reference into a separate REFERENCE.md linked one level deep, keeping SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	It is mostly command-driven, but opens with a background sentence Claude already knows ('Schedule It is a scheduling application that helps users manage appointments and events...'), explains Membrane's auth behavior in prose, and repeats the action-list command in two sections, so it could be tightened.	3 / 5
Actionability	It provides concrete, executable commands throughout (npm install, membrane login, connection ensure, action list/run, request) plus a proxy flags table, with only minor gaps such as no fully fleshed example of an action run with a real input payload.	4 / 5
Workflow Clarity	The connection lifecycle is clearly sequenced (install → login → ensure → wait → search → run) with state-based branching and polling feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), though error-recovery guidance is brief rather than a full checklist.	4 / 5
Progressive Disclosure	It is a single well-organized file with clear section headers and no nested references; structure is good, but the proxy flags table and connection-state handling are inlined content that, given the length, could justify separate reference files.	4 / 5
	Total	15 / 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 answers both what and when with an explicit 'Use when...' clause and names a specific app, which is a solid baseline. Its main weakness is that actions are reduced to one generic verb ('Manage') applied to a list of nouns, and trigger keywords lack synonyms.

Suggestions

Replace the generic 'Manage ... and more' with several distinct concrete verbs (e.g. create, update, list, delete) tied to specific objects so capabilities are unambiguous.

Add natural trigger synonyms and file/feature cues users would say, such as 'appointments', 'meetings', 'calendars', or 'events', not just 'interact with Schedule it data'.

Make the 'when' clause more concrete, e.g. 'Use when the user wants to create or update Schedule it meetings, calendars, users, or activities.'

Dimension	Reasoning	Score
Specificity	It names the domain and lists several concrete entities ('Manage Users, Roles, Organizations, Projects, Pipelines, Activities'), but the only action verb is the generic 'Manage ... and more' rather than several distinct concrete actions, so it does not reach level 4.	3 / 5
Completeness	It states both a clear 'what' (manage Users, Roles, Organizations, etc.) and an explicit 'when' ('Use when the user wants to interact with Schedule it data'), but the 'when' clause is somewhat generic and could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	It includes the natural app-name keyword 'Schedule it' and 'interact with Schedule it data', but offers no synonyms or common variations a user might actually say (e.g. appointments, meetings, calendars), keeping it at level 3.	3 / 5
Distinctiveness Conflict Risk	Tying triggers to the specific named app 'Schedule it' gives it a clear niche and mostly distinct triggers, though the lowercase phrase 'schedule it' is a common generic expression, creating minor overlap risk.	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/schedule-it/SKILL.md
Commit: f484c82

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