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

typesense

Typesense Search integration. Manage data, records, and automate workflows. Use when the user wants to interact with Typesense Search 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/typesense/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 content is highly actionable with concrete, executable commands and a strong connection workflow, but it loses conciseness to an unnecessary intro and duplicated examples, and its single-file structure inlines material that could be progressively disclosed.

Suggestions

Remove the 'Typesense is a fast, open source search engine...' intro paragraph and the 'Official docs' line, since Claude already knows what Typesense is; keep only the integration-relevant context.

Merge the 'Searching for actions' and 'Popular actions' sections to eliminate the duplicated 'membrane action list' invocation and tighten the flow.

Clearly label the action-running section as 'Step 2' (or rename the 'skip to Step 2' references) so the cross-references resolve to actual headings.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with code blocks and a flag table instead of prose, but it includes an unnecessary intro paragraph explaining what Typesense is and duplicates the 'action list' invocation across the 'Searching for actions' and 'Popular actions' sections.	3 / 5
Actionability	Fully executable, copy-paste-ready commands cover the common cases: install, login (including headless), connection ensure/wait, action list/run with JSON params, and proxy requests with a complete flag table.	5 / 5
Workflow Clarity	The connection sub-workflow is well sequenced with a validation checkpoint (poll --wait, branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after action), but the overall document references 'Step 2' without a clearly labeled Step 2 heading, leaving a minor sequencing gap.	4 / 5
Progressive Disclosure	The single-file skill is well organized with clear section headers and no broken or nested references, though substantial inlined bulk (the clientAction schema and proxy flag table) could be split into reference files; no bundle files exist to verify further.	4 / 5
	Total	16 / 20 Passed

Description

66%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 answers both what and when and names a distinct product niche, but its action verbs are generic and its trigger-term coverage is limited to the product name without common synonyms.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with Typesense-specific verbs such as indexing documents, searching collections, and managing aliases or API keys.

Broaden trigger terms to include natural variations users might say, such as 'search', 'indexing', 'collections', or 'Typesense API'.

Expand the 'Use when...' clause to enumerate concrete scenarios (e.g., searching records, managing collections, syncing data) rather than a single 'interact with Typesense Search data' phrase.

Dimension	Reasoning	Score
Specificity	Names the domain ('Typesense Search') and 1-2 actions ('Manage data, records, and automate workflows'), but the actions are generic rather than Typesense-specific verbs like index, search, or query collections, so coverage is not comprehensive.	3 / 5
Completeness	Both a clear 'what' (Typesense Search integration, manage data/records/workflows) and an explicit 'when' ('Use when the user wants to interact with Typesense Search data') are present, though the 'when' clause is narrow and could be more specific.	4 / 5
Trigger Term Quality	The natural product keyword 'Typesense Search' appears, but common variations and synonyms (e.g., 'search', 'indexing', 'collections') are missing, leaving only some relevant keywords.	3 / 5
Distinctiveness Conflict Risk	'Typesense Search' is a unique named product giving the skill a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	15 / 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/typesense/SKILL.md
Commit: f484c82

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