Name: occasion
Rating: 58.4 (1 reviews)
Author: membranedev

occasion

Occasion integration. Manage Events, Venues, Users, Orders, Reports. Use when the user wants to interact with Occasion data.

Quality

68%

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/occasion/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 body is highly actionable with concrete CLI commands and a well-structured connection workflow, but it lacks validation checkpoints for destructive proxy/action operations and carries some trimmable prose. Organization is good for a single-file skill with no external references.

Suggestions

Add a validation/verification step after destructive proxy requests (e.g., re-fetch the resource or confirm the response status) to satisfy the workflow_clarity feedback-loop requirement.

Tighten prose by removing filler such as "so you can focus on the integration logic rather than auth plumbing", "This will burn less tokens", and the non-instructive "When to use which actions" line.

Resolve the dangling "skip to Step 2" reference (no Step 2 is labeled) and make the "Popular actions" section list concrete example actions instead of repeating the search command.

Dimension	Reasoning	Score
Conciseness	Mostly command-driven and efficient, but trimmable prose remains ("so you can focus on the integration logic rather than auth plumbing", "This will burn less tokens") plus the filler line "When to use which actions: Use action names and parameters as needed."	3 / 5
Actionability	Copy-paste commands cover install, auth, connection, action list/run, and a proxy flags table, but the "Popular actions" section only repeats the search command without listing actual actions, leaving a minor gap.	4 / 5
Workflow Clarity	The connection flow is sequenced with a poll/state feedback loop, but proxy requests and action runs can be destructive or batch (POST/PUT/DELETE) with no validation/verification steps, which caps this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist; the single file is well-sectioned with clear headers and no nested references, with only minor redundancy between "Popular actions" and "Searching for actions".	4 / 5
	Total	14 / 20 Passed

Description

75%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 concise and answers both what and when for a named platform, with good trigger keywords and minimal conflict risk. It stops short of comprehensive, granular action verbs and concrete trigger phrases that would warrant top marks.

Dimension	Reasoning	Score
Specificity	"Manage Events, Venues, Users, Orders, Reports" lists several concrete domain objects, though the single generic verb "Manage" is less action-specific than the anchor examples.	4 / 5
Completeness	It states a clear "what" (manage Events, Venues, Users, Orders, Reports) and an explicit "when" clause, but the trigger is generic rather than elaborated with concrete user phrases, fitting the 4-anchor.	4 / 5
Trigger Term Quality	"Occasion" plus entity names and the explicit "Use when the user wants to interact with Occasion data" give good keyword coverage; synonyms are limited because the tool targets a single named platform.	4 / 5
Distinctiveness Conflict Risk	"Occasion" is a named platform giving a clear niche, yet generic entity terms (Events, Orders) carry minor overlap risk with general event or calendar skills.	4 / 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/occasion/SKILL.md
Commit: f484c82

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