Name: infinity
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

infinity

Infinity integration. Manage Workspaces. Use when the user wants to interact with Infinity data.

Quality

61%

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

Quality

Content

65%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 executable CLI commands and a clear connection state machine, but it is slightly padded and monolithic. Adding validation guidance for destructive actions and splitting the bulk actions table into a reference file would raise the weaker dimensions.

Suggestions

Add a validation/verification checkpoint before running destructive actions (e.g., 'list-items' to confirm the target before 'update-item' or deletion).

Move the 20-row Popular actions table into a separate references file (e.g. actions.md) and keep only the few most-used actions inline.

Trim explanatory filler such as the Infinity product overview and 'Use action names and parameters as needed' to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes some unneeded explanation (the Infinity product intro, 'so you can focus on the integration logic rather than auth plumbing') and a filler line ('Use action names and parameters as needed').	3 / 5
Actionability	It provides copy-paste-ready, fully executable commands for the common cases (connection ensure, action list/run with --input JSON, proxy requests with a flags table), covering the typical workflow end to end.	5 / 5
Workflow Clarity	The connection workflow is well sequenced with a state machine and polling feedback loop, but the skill covers destructive operations (update-item, update-folder, update-attribute) with no validation/verification checkpoint, which caps this dimension at 3.	3 / 5
Progressive Disclosure	Sections are clearly headed and organized, but the entire skill is a single monolithic file with no bundle references; the large 20-row actions table and detailed connection state machine are inlined content that could live in separate reference files.	3 / 5
	Total	14 / 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 correctly includes an explicit 'Use when...' trigger and ties the skill to a distinct product (Infinity), but its capability list is thin and generic. Tightening the 'what' with concrete actions would lift specificity and completeness.

Suggestions

Replace the vague 'Manage Workspaces' with several concrete actions (e.g., 'List and create workspaces, boards, folders, and items; update attributes and comments').

Add natural trigger synonyms users might say, such as 'Infinity boards', 'Infinity tasks', or 'startinfinity.com'.

Expand the 'what' so it clearly enumerates the main capabilities rather than a single generic verb.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Infinity integration') but only offers one minimal, generic action ('Manage Workspaces'), lacking the several concrete actions the higher anchors require.	2 / 5
Completeness	It answers both what ('Infinity integration. Manage Workspaces.') and when via an explicit 'Use when the user wants to interact with Infinity data.' clause, though the 'what' is somewhat thin rather than fully concrete.	4 / 5
Trigger Term Quality	It includes relevant natural keywords ('Infinity', 'Workspaces', 'Infinity data') but misses common synonyms or variations users might say, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The 'Infinity' product name plus 'Infinity data' triggers give it a clear niche with minimal conflict risk, though the generic 'Workspaces' term has minor overlap with other workspace-oriented tools.	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/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.