Name: dayschedule
Rating: 62.4 (1 reviews)
Author: membranedev

dayschedule

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

Quality

73%

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

Quality

Content

68%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-validated connection workflow, but it carries unnecessary marketing fluff and a low-value action table, and lacks validation guidance for the destructive/batch operations it advertises.

Suggestions

Remove or condense the opening product-description paragraph; Claude does not need DaySchedule explained, and it adds token cost with no actionable value.

Replace the 20-row popular-actions table whose entries all say "No description" with a shorter list of genuinely useful actions (or move it to a reference file) so each row earns its tokens.

Add a brief validation/verification step before running destructive actions (e.g. delete-user) — such as confirming the target ID or listing the record first — to satisfy the destructive-operation checkpoint and lift workflow clarity above the cap.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the opening marketing paragraph ("DaySchedule is a scheduling and planning application... from students to professionals") explains concepts Claude doesn't need, and the 20-row popular-actions table repeats "No description" with no informational value — both could be trimmed.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands across the common cases (install, login, connection ensure, polling, action search/run, proxy) with appropriate placeholders and a clear flags table — matching the anchor for complete, executable guidance.	5 / 5
Workflow Clarity	The connection setup has a strong validation/feedback loop (BUILDING polling, CLIENT_ACTION_REQUIRED handling, error-state checks), but the skill advertises destructive and batch operations (delete-user, list-*) with no pre-execution validation or verification guidance, which caps workflow clarity at 3 per the destructive/batch guideline.	3 / 5
Progressive Disclosure	A self-contained single file with no external bundle references, organized into clear, logically ordered sections (overview, install, auth, connect, search, run, proxy, best practices); the inline popular-actions table is compact enough to stay inline, with only minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

78%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.

A strong description that names the product, lists concrete managed entities, and includes an explicit "Use when" trigger. It could be sharpened with more specific trigger phrasing tied to DaySchedule's scheduling/booking use cases.

Dimension	Reasoning	Score
Specificity	Enumerates several concrete capabilities ("Manage Users, Roles, Organizations, Projects, Activities, Notes and more"), but a single generic verb ("Manage") covers what are really entity nouns, leaving minor coverage gaps via "and more" — above the 1-2 actions of a 3 but not the distinct multi-action breadth of a 5.	4 / 5
Completeness	Explicitly answers both "what" (Manage Users, Roles, etc.) and "when" ("Use when the user wants to interact with DaySchedule data"), but the trigger could be more specific about scheduling/booking scenarios rather than the generic "interact with DaySchedule data".	4 / 5
Trigger Term Quality	Includes the product name "DaySchedule" and natural entity terms (Users, Roles, Organizations, Projects, Activities, Notes) a user would mention, plus an explicit "Use when" phrase; a few natural synonyms (e.g. booking, scheduling, meetings) are missing, so it sits at good-but-not-comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	The named product "DaySchedule" establishes a clear niche with a distinct, product-specific trigger, yielding minimal conflict risk with other skills despite the otherwise generic entity list.	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/dayschedule/SKILL.md
Commit: f484c82

Reviewed: ~16 hours 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.