Name: svix
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

svix

Svix integration. Manage Organizations. Use when the user wants to interact with Svix 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/svix/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 content is a well-structured, actionable integration guide with concrete commands and a clear connection-state workflow including feedback loops. Its main weakness is conciseness, with marketing-style prose and a filler opener that could be trimmed.

Suggestions

Cut the filler opener ("Svix is a data management platform…") and the auth-plumbing marketing clause to tighten conciseness.

Label the workflow steps explicitly (Step 1, Step 2) so the "skip to Step 2" reference resolves, improving workflow clarity.

Move the verbose clientAction type breakdown and proxy flags table into a separate reference file and link to it from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary prose such as "so you can focus on the integration logic rather than auth plumbing" and the filler opener "Svix is a data management platform. Use the available actions to discover its full capabilities.", matching the mostly-efficient-but-could-be-tightened anchor; it is not lean enough for score 4.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands (install, login, connection ensure, action list/run, request) plus a flags table, matching the mostly-executable anchor with minor gaps like the CONNECTION_ID placeholder; it stops short of score 5 because common-case examples are not fully fleshed out.	4 / 5
Workflow Clarity	The install→authenticate→connect→poll→search→run sequence is clear with explicit state checkpoints (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a re-poll feedback loop, matching the clear-sequence-with-most-checkpoints anchor; the unlabeled "Step 2" reference and loose step numbering keep it from score 5.	4 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is well-organized into clearly signaled sections (Overview, Working with Svix, Connecting, Searching, Proxy, Best practices), matching the good-structure anchor; the inline clientAction detail and proxy flag table could arguably live in separate references, a minor gap that prevents score 5.	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 correctly pairs a concrete capability with an explicit "Use when" trigger and leverages a distinctive named product, but its capability list and trigger-term variety are thin. Expanding both would lift the weaker specificity and trigger-term dimensions.

Suggestions

Add 2-3 more concrete Svix capabilities (e.g., create endpoints, send messages, manage event types) to raise specificity beyond a single action.

Broaden trigger terms with natural synonyms users might say (e.g., webhooks, event delivery, Svix API) instead of the generic "interact with Svix data".

Tighten the "what" to lead with the concrete actions rather than the abstract "Svix integration." opener.

Dimension	Reasoning	Score
Specificity	"Manage Organizations" names the Svix domain plus one concrete action, matching the anchor that lists a domain with 1-2 concrete actions but is not comprehensive; it is more concrete than the score-2 "names domain only" anchor yet far short of the multi-action score-5 anchor.	3 / 5
Completeness	It states a clear "what" ("Svix integration. Manage Organizations.") and an explicit "Use when the user wants to interact with Svix data" clause, matching the anchor with both what and when where the when could be more specific; it does not reach the score-5 anchor's concrete multi-trigger phrasing.	4 / 5
Trigger Term Quality	The phrase "interact with Svix data" supplies the core natural keyword ("Svix") but offers few synonyms or variations, fitting the anchor for some relevant keywords missing common variations; it lacks the broader term coverage of the score-4 anchor.	3 / 5
Distinctiveness Conflict Risk	Svix is a named product giving a clear niche with low conflict risk, but the generic trigger "interact with Svix data" leaves minor overlap potential, placing it at the mostly-distinct score-4 anchor rather than the minimal-conflict score-5 anchor.	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/svix/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.