Name: ayrshare
Rating: 56.8 (1 reviews)
Author: membranedev

ayrshare

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

Quality

65%

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/ayrshare/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 is a strong, command-heavy CLI guide with executable examples and a well-sequenced connection workflow including state-based checkpoints. Its main weaknesses are mild verbosity (marketing intro, vague overview, a redundant actions section) and placeholder-heavy examples that aren't fully filled in.

Suggestions

Trim the promotional intro paragraph and the abstract 'Ayrshare Overview' bullet list; assume Claude knows what a social media API is.

Remove the redundant 'Popular actions' section that re-states the `membrane action list` command already covered in 'Searching for actions'.

Show at least one fully-filled example, e.g. a real `--intent "post to social media"` with a concrete actionId and CONNECTION_ID, so the run/proxy flows are end-to-end copy-pasteable.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but includes a marketing-style intro paragraph ('It's used by businesses and individuals looking to streamline...'), a vague 'Ayrshare Overview' bullet list, and a redundant 'Popular actions' section that repeats the action-list command already shown.	3 / 5
Actionability	It provides copy-paste-ready commands for every stage (install, login, connection ensure/get, action list/run, request proxy) plus a flags table, but several examples leave placeholders unfilled ('QUERY', CONNECTION_ID, actionId, /path/to/endpoint) rather than showing concrete filled values.	4 / 5
Workflow Clarity	There is a clear install → authenticate → connect → poll → search → run sequence with a strong feedback loop on connection state (BUILDING/READY/CLIENT_ACTION_REQUIRED/ERROR), but 'skip to Step 2' references are dangling with no labeled Step 2, leaving minor sequencing gaps.	4 / 5
Progressive Disclosure	With no bundle files present, all content lives in a single SKILL.md organized into well-labeled sections that are easy to navigate; it earns good structure marks, though the detailed connection-state spec is inlined and could optionally be a one-level-deep reference.	4 / 5
	Total	15 / 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: it names a distinct product and provides an explicit 'Use when' trigger, satisfying both what and when. Its weaknesses are generic, buzzwordy action verbs and thin trigger-term coverage that omits the natural social-media phrasing users would actually say.

Suggestions

Replace generic verbs with concrete Ayrshare actions, e.g. 'Post to social networks, fetch analytics, and schedule content across platforms.'

Expand the trigger clause with natural user phrasing: 'Use when the user wants to post to or analyze social media via Ayrshare, or mentions social scheduling, cross-platform posting, or Ayrshare analytics.'

Drop the abstract 'Manage data, records' framing, which reads as fluff and dilutes the distinct product niche.

Dimension	Reasoning	Score
Specificity	Names the Ayrshare domain plus a few actions ('Manage data, records, and automate workflows'), but the actions are generic verbs over abstract nouns rather than concrete Ayrshare-specific operations like posting or fetching analytics.	3 / 5
Completeness	It has both a 'what' ('Ayrshare integration. Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Ayrshare data'), though the 'when' could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	The only natural keyword is the product name in 'interact with Ayrshare data'; it lacks the phrases users actually say ('post to social media', 'schedule a post', 'social analytics'), missing common variations.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product Ayrshare gives it a clear niche with low conflict risk, but the generic 'manage data, records, and automate workflows' wording creates minor overlap with other 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/ayrshare/SKILL.md
Commit: f484c82

Reviewed: less than a minute 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.