Name: amity
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

amity

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

Quality

72%

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

Quality

Content

82%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 highly actionable with executable commands and a well-sequenced connection workflow including a polling feedback loop. Main weaknesses are the undefined 'Step 2' reference that breaks navigation and minor verbosity in the intro and redundant discovery example.

Suggestions

Define or remove the undefined 'Step 2' reference ("skip to Step 2") so the connection workflow navigation is consistent.

Add an explicit validation/verification checkpoint after running actions or proxy requests (e.g. inspect the `output` field and check for error states) to close the workflow feedback loop.

Trim the introductory Amity marketing paragraph and the duplicate discovery command in 'Popular actions' to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable CLI commands and brief explanations, but includes light padding (the introductory Amity marketing paragraph and the redundant 'Popular actions' discovery example) that could be trimmed, matching the efficient-with-minor-over-explanation anchor.	4 / 5
Actionability	It provides copy-paste ready commands for install, login, connection ensure, polling, action list/run, and proxy requests, plus a complete flag table covering the common cases, matching the fully-executable anchor.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with state-based branching and a poll-again feedback loop, but the referenced 'Step 2' is never defined and the action-running section lacks an explicit validation checkpoint, so it sits at clear-sequence-with-most-checkpoints but minor gaps.	4 / 5
Progressive Disclosure	With no bundle files present, content is organized into well-signaled single-file sections (Overview, Working with Amity, Best practices) that are easy to navigate; it is good structure rather than the maximally-split one-level-deep-references level 5, since some detail (e.g. full clientAction handling, proxy options) could live in separate reference files.	4 / 5
	Total	17 / 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 is functional with an explicit Use-when clause and a clear platform niche, but the capability verbs are generic and the trigger coverage lacks synonyms and file/extension-style natural terms. Tightening the action list and broadening trigger phrasing would lift specificity and trigger quality.

Suggestions

Replace generic verbs ("Manage data, records") with concrete Amity actions such as "create and moderate communities, manage channels and posts, send messages" to raise specificity.

Broaden trigger terms with natural synonyms users actually say, e.g. "Use when the user wants to work with Amity communities, channels, posts, or messaging APIs."

Keep the explicit 'Use when' clause but pair it with the concrete action list so both what and when are maximally specific.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Amity domain plus 1-2 actions, but the verbs (manage, automate) are generic and the coverage is not comprehensive, matching the anchor for naming domain with 1-2 concrete actions.	3 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Amity data"), but the when clause is somewhat generic, so it lands at has-both-but-when-could-be-more-explicit rather than the fully concrete level 5.	4 / 5
Trigger Term Quality	Terms like "Amity", "data", "records", "workflows" and the phrase "interact with Amity data" are relevant, but common synonyms and natural variations users might say are missing, placing it at some-relevant-keywords-with-gaps rather than good coverage.	3 / 5
Distinctiveness Conflict Risk	"Amity integration" scopes it to a specific platform with a distinct trigger ("interact with Amity data"), giving mostly distinct identity with only minor overlap risk against generic data-management skills.	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/amity/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.