Name: supersaas
Rating: 60 (1 reviews)
Author: membranedev

supersaas

SuperSaaS integration. Manage Schedules, Resources, Services, Promotions, Dashboards, Reports. Use when the user wants to interact with SuperSaaS data.

Quality

70%

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/supersaas/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 content is highly actionable with executable commands throughout and a well-structured connection workflow with state-based feedback loops. Its weaknesses are some padded introductory prose, missing validation guidance for destructive data operations, and a large inline action table that could be externalized.

Suggestions

Add an explicit validation/verification step before destructive actions (e.g. confirm the target ID with get-appointment before running delete-appointment), which would lift workflow_clarity above the destructive-operations cap.

Trim the introductory paragraph to one factual line about SuperSaaS rather than three sentences of analogy and explanation.

Move the popular-actions table to a references/ACTIONS.md file and link to it from the body to deepen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-and-table driven, but the intro ("SuperSaaS is an online appointment scheduling software... Think of it as a customizable calendar and booking system that can be embedded on a website.") and asides like "so you can focus on the integration logic rather than auth plumbing" add unnecessary explanation, matching the anchor for mostly efficient with some unnecessary explanation.	3 / 5
Actionability	It provides copy-paste-ready, executable commands for every stage (install, login, connection ensure/get, action list, action run with JSON input, request proxy) plus a full popular-actions table and options table, matching the anchor for fully executable guidance covering common cases.	5 / 5
Workflow Clarity	The connection flow has state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with feedback loops, but destructive operations (delete-user, delete-appointment, update-*) lack validation/verification steps, and "skip to Step 2" references a step that is never labeled, so the destructive-operations cap holds it at 3.	3 / 5
Progressive Disclosure	The skill has well-organized sections with clear headers and easy navigation, and no bundle files exist to split further; it stays at 4 rather than 5 because the large inline popular-actions table is content that could live in a separate reference file, a minor organization gap.	4 / 5
	Total	15 / 20 Passed

Description

71%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 clearly names a distinct niche and lists concrete capability domains with an explicit "Use when" clause. Its main weakness is the generic trigger phrasing, which lacks the natural synonyms (appointments, bookings, scheduling) users would actually say.

Suggestions

Add concrete trigger synonyms to the "Use when" clause, e.g. "Use when the user wants to manage SuperSaaS appointments, bookings, schedules, or resources."

Replace the single generic verb "Manage" with a few distinct actions (e.g. "List, create, update, and delete appointments, users, and schedules") to raise specificity.

Dimension	Reasoning	Score
Specificity	The phrase "Manage Schedules, Resources, Services, Promotions, Dashboards, Reports" lists six concrete domains, matching the anchor for several specific actions; it stays at 4 rather than 5 because a single generic verb ("Manage") is applied to all of them rather than distinct concrete actions.	4 / 5
Completeness	Both "what" ("SuperSaaS integration. Manage Schedules, Resources, Services, Promotions, Dashboards, Reports.") and "when" ("Use when the user wants to interact with SuperSaaS data.") are explicitly present, but the trigger clause is generic rather than listing concrete trigger phrases, so it fits the anchor where "when" could be more specific.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with SuperSaaS data" surfaces the key brand term but omits natural synonyms users would say (appointments, bookings, scheduling), matching the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	"SuperSaaS integration" carves out a clear niche tied to a named product with distinct triggers and minimal overlap risk, matching the anchor for a clear niche with minimal conflict.	5 / 5
	Total	16 / 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/supersaas/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.