Name: infinity-1
Rating: 52 (1 reviews)
Author: membranedev

infinity-1

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

Quality

57%

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/infinity-1/SKILL.md

Quality

Content

57%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 solid, command-driven integration guide with executable examples and a clearly documented connection state machine, but it pads a generic product intro, omits validation for destructive/batch operations, and keeps all reference-style detail inline in one file.

Suggestions

Trim the opening paragraph that explains what Infinity is, and remove marketing-flavored phrases like 'so you can focus on the integration logic rather than auth plumbing'.

Add a validation/verification checkpoint before destructive or batch operations, e.g. confirm the target item and run a dry-run/GET before 'membrane request' with -X DELETE or -X PUT.

Move the proxy flag table and full connection state-machine reference into a separate REFERENCE.md, keeping SKILL.md a concise overview that links to it.

Dimension	Reasoning	Score
Conciseness	The guide is mostly command-driven and efficient, but the opening paragraph explaining what Infinity is and phrases like 'focus on the integration logic rather than auth plumbing' are unnecessary padding that could be trimmed.	3 / 5
Actionability	Concrete, copy-paste-ready CLI commands cover the main flows (install, auth, connect, search, run, proxy) with documented return shapes, but the mixed invocation style ('membrane' vs 'npx @membranehq/cli@latest') and unsubstituted placeholders are minor gaps.	4 / 5
Workflow Clarity	The connect-to-run sequence and state-machine handling are clearly sequenced with a poll feedback loop, but destructive/batch operations (proxy DELETE/PUT, action run on records) lack any validation or verification steps, capping this dimension at 3.	3 / 5
Progressive Disclosure	Sections are well-organized, but everything lives in a single ~140-line SKILL.md with no bundle files; reference-style detail (the flag table, full connection state machine) is inlined rather than split into a separate reference file.	3 / 5
	Total	13 / 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 establishes a clear product-specific niche and includes a 'Use when' trigger clause, but its stated capabilities are generic ('manage data, records, automate workflows') and the trigger terms lack the concrete synonyms (projects, boards, tasks) a user would naturally say.

Suggestions

Replace generic verbs with concrete Infinity-specific actions, e.g. 'Create and manage boards, columns, and items; automate workflows.'

Expand the 'Use when' clause to name natural triggers a user would say, e.g. 'Use when the user wants to manage Infinity projects, boards, tasks, or records.'

Dimension	Reasoning	Score
Specificity	Names the domain ('Infinity integration') but the actions ('Manage data, records, automate workflows') are generic rather than concrete, fitting the 'minimal or generic actions' anchor below the midpoint.	2 / 5
Completeness	Provides both a 'what' ('Manage data, records, and automate workflows') and a 'when' ('Use when the user wants to interact with Infinity data'), but the trigger clause is a single generic condition rather than enumerated concrete phrases.	4 / 5
Trigger Term Quality	Includes relevant keywords ('Infinity', 'data', 'records', 'workflows') but misses common variations and domain-specific terms users would say (projects, boards, tasks, items), so it lacks synonym coverage.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'Infinity' gives it a clear niche and distinct triggers, though the generic action verbs ('Manage data, records') create minor overlap risk with other data 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/infinity-1/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.