Name: savvycal
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

savvycal

SavvyCal integration. Manage Users. Use when the user wants to interact with SavvyCal data.

Quality

61%

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

Quality

Content

61%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 a well-structured, largely executable guide to driving SavvyCal through the Membrane CLI, with a notably clear connection-state machine. Its main weaknesses are mild prose padding, a broken 'Step 2' cross-reference, and the absence of validation checkpoints before running potentially mutating actions.

Suggestions

Add a validation/verification step before running mutating actions (e.g., dry-run, confirm the action's inputSchema, or check the result's output for expected fields) to lift workflow clarity.

Fix or remove the dangling 'skip to Step 2' references by adding a '## Step 2: Run actions' heading or rewording the pointers.

Trim non-essential prose like the auth-plumbing aside and the marketing-style intro paragraph to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and brief explanations, but contains unnecessary prose such as 'so you can focus on the integration logic rather than auth plumbing' and an introductory paragraph on what SavvyCal is.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands (npm install, membrane login, connection ensure, action run) and a flag table, with only minor gaps from placeholder IDs that are inherent to the workflow.	4 / 5
Workflow Clarity	The install→login→connect→search→run sequence is clear and the connection-state feedback loop is well handled, but running SavvyCal actions (which can modify user/calendar data) lacks any validation or verification checkpoint, capping this dimension at 3.	3 / 5
Progressive Disclosure	The single file is well sectioned with clear headers and no nested references, but the dangling 'skip to Step 2' references have no matching 'Step 2' heading, a minor organization gap.	4 / 5
	Total	14 / 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 is structurally sound — it states what the skill does and when to use it and names a distinct product — but it is thin on specific capabilities and lacks the natural scheduling vocabulary users would actually say. It sits comfortably above the vague baseline without reaching the comprehensive, trigger-rich examples.

Suggestions

List more concrete SavvyCal actions beyond 'Manage Users' (e.g., manage scheduling links, availability, organizations) to raise specificity.

Add natural user trigger terms like 'scheduling', 'calendar', 'appointments', or 'availability' to the 'Use when' clause.

Make the 'when' clause more specific, e.g. 'Use when the user wants to manage SavvyCal users, scheduling links, or availability.'

Dimension	Reasoning	Score
Specificity	It names the domain ('SavvyCal integration') and one concrete action ('Manage Users'), matching the anchor for naming a domain plus a minimal concrete action, but coverage is not comprehensive.	3 / 5
Completeness	Both 'what' ('SavvyCal integration. Manage Users.') and 'when' ('Use when the user wants to interact with SavvyCal data.') are present, but the trigger phrase is generic rather than concrete, so it does not reach a 5.	4 / 5
Trigger Term Quality	'SavvyCal', 'Users', and 'interact with SavvyCal data' are relevant keywords, but natural scheduling synonyms a user would say (scheduling, calendar, appointments, availability) are missing.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product SavvyCal gives it a clear niche with low conflict risk, though the generic 'Manage Users' trigger could overlap slightly with other user-management skills.	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/savvycal/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.