Name: swiftype
Rating: 59.2 (1 reviews)
Author: membranedev

swiftype

Swiftype integration. Manage data, records, and automate workflows. Use when the user wants to interact with Swiftype 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/swiftype/SKILL.md

Quality

Content

75%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 a highly actionable CLI integration guide with executable commands, a clear connection workflow, and explicit state-based feedback loops. It loses points for conceptual/marketing padding and minor structural redundancy rather than any lack of utility.

Suggestions

Trim concept explanations Claude already knows — drop 'Swiftype is a search solution... provide a better search experience' and 'so you can focus on the integration logic rather than auth plumbing' to improve token efficiency.

Fix the dangling 'Step 2' reference and reconcile the '1b' subsection numbering so the connection workflow has a coherent, labeled step sequence.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes unnecessary conceptual padding such as 'Swiftype is a search solution for websites and apps. It allows businesses to provide a better search experience' and 'so you can focus on the integration logic rather than auth plumbing'; not a 2 because the bulk is action-oriented, not a 4 because the product/marketing-style explanations are the kind of concept-padding the rubric penalizes.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (npm install, membrane login, connection ensure, action list/run, request) plus a flag table for proxy options, covering the common cases; placeholders like CONNECTION_ID are inherent to CLI integration and do not reduce executability.	5 / 5
Workflow Clarity	Clear sequenced workflow (install, authenticate, connect, poll for state, search actions, run/proxy) with explicit feedback loops (poll until READY, re-poll after user action, branch on CLIENT_ACTION_REQUIRED and error states); not a 5 because of a dangling 'Step 2' reference and inconsistent numbering ('1b' with no '1a'), not a 3 because checkpoints and error-recovery loops are genuinely present.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Overview, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no deeply nested or buried references; not a 5 because it is a single ~145-line file with no reference split and minor redundancy between 'Searching for actions' and 'Popular actions', not a 3 because structure is clean and nothing is monolithic or poorly navigable.	4 / 5
	Total	16 / 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 successfully pairs a 'what' with an explicit 'Use when...' trigger and leverages a distinct product name for low conflict risk. Its main weakness is generic action language ('manage data, records, automate workflows') that lacks concrete, specific capabilities.

Suggestions

Replace generic verbs with concrete Swiftype capabilities, e.g. 'Search documents, manage engines, and query the Swiftype API' instead of 'Manage data, records, and automate workflows'.

Expand the trigger clause with natural variations users might say, e.g. 'Use when the user wants to search Swiftype engines, manage documents, or query Swiftype data.'

Dimension	Reasoning	Score
Specificity	Names the domain (Swiftype) and lists several action areas ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, fitting 'names domain and 1-2 concrete actions, not comprehensive'; not a 2 because multiple distinct action categories are named, not a 4 because no specific concrete operations are enumerated.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Swiftype data') are present; not a 5 because the 'what' is generic and the trigger phrases lack concrete richness, clearly above a 3 which requires the 'when' to be missing or only weakly implied.	4 / 5
Trigger Term Quality	The natural trigger keyword 'Swiftype' appears ('Use when the user wants to interact with Swiftype data'), giving some relevant keywords, but it offers no synonyms or variations; not a 2 because the product name is a genuine natural-language trigger, not a 4 because coverage is thin with no variations.	3 / 5
Distinctiveness Conflict Risk	The unique proper-noun product name 'Swiftype' provides a clear niche with minimal conflict risk, but the generic action language ('manage data, automate workflows') creates minor overlap risk with other data-integration skills; not a 5 due to that generic overlap, not a 3 because the Swiftype anchor makes it mostly distinct.	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/swiftype/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.