Name: seam
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

seam

Seam integration. Manage data, records, and automate workflows. Use when the user wants to interact with Seam data.

Quality

62%

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/seam/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 body provides concrete, executable CLI guidance with a well-sequenced connection workflow and explicit state checkpoints. Its main weaknesses are padded prose that could be trimmed and a few minor workflow/organization gaps.

Suggestions

Trim non-essential commentary such as the Seam business-context intro, the 'auth plumbing' aside, and 'This is the fastest way to get a connection' to tighten token efficiency.

Label the workflow steps explicitly (e.g. 'Step 1', 'Step 2') so the 'skip to Step 2' references resolve, and add a verification note after running an action (e.g. check the `output` field for errors before proceeding).

Consider moving the detailed connection-state handling (CLIENT_ACTION_REQUIRED sub-fields, BUILDING polling) into a referenced file to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is largely command-driven, but several padded passages add little ('Seam is a platform that provides an API...', 'so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection', and the ungrammatical 'Those will be used to adjust tooling...'). It is mostly efficient with unnecessary commentary that could be trimmed, matching anchor 3 rather than 4.	3 / 5
Actionability	Concrete, copy-paste CLI commands cover install, login, connection, action search/run, and proxy, plus a full proxy-options table. It does not reach 5 because key identifiers are placeholders (CONNECTION_ID, <actionId>, <agentType>) and the Seam Overview lists entity names abstractly without concrete action examples.	4 / 5
Workflow Clarity	There is a clear install->login->connect->search->run->proxy sequence with state-checking checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll->handle-client-action->re-poll feedback loop. It stops at 4 because the text references an unlabeled 'Step 2' and provides no verification step after running an action.	4 / 5
Progressive Disclosure	The skill is self-contained with no external bundle files and is organized into clearly headed sections (Overview, Working with Seam, Popular actions, Best practices). It is not 5 because at ~150 lines and multi-step it could split the verbose connection-state handling into a referenced file, leaving minor organization gaps per anchor 4.	4 / 5
	Total	15 / 20 Passed

Description

57%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 states both what the skill does and when to use it, anchored by the distinct 'Seam' brand name. Its main weakness is generic, non-concrete action language and missing device-specific trigger terms.

Suggestions

Replace generic verbs with concrete Seam capabilities, e.g. 'Control smart locks and thermostats, manage access codes, and subscribe to device events'.

Add natural trigger terms users would actually say, such as 'smart locks', 'access codes', 'thermostats', or 'Seam devices', to the Use-when clause.

Make the 'when' clause more specific, e.g. 'Use when the user wants to manage Seam-connected devices, locks, or access codes'.

Dimension	Reasoning	Score
Specificity	The description names the Seam domain but the actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete. It does not reach 3 because no specific operations (e.g. control locks, manage access codes) are listed, and is above 1 because the domain is named with a few action verbs.	2 / 5
Completeness	Both the 'what' ('Manage data, records, and automate workflows') and the 'when' ('Use when the user wants to interact with Seam data') are present, and the explicit Use-when clause avoids the cap at 3. It does not reach 5 because the 'when' clause is generic and lacks concrete trigger phrases naming Seam's use cases.	4 / 5
Trigger Term Quality	'Seam' is a genuine natural brand keyword a user would say, but 'data', 'records', and 'workflows' are generic and the device-specific terms users actually use (smart locks, thermostats, access codes, webhooks) are missing. It sits at 3 rather than 4 because common synonyms and variations are absent.	3 / 5
Distinctiveness Conflict Risk	The 'Seam' brand name anchors a clear niche and the trigger ('interact with Seam data') is brand-specific, keeping conflict risk low. It is not 5 because the generic action verbs ('manage data, records, automate workflows') could overlap with other integration skills.	4 / 5
	Total	13 / 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/seam/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.