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

Blog Docs Log in Get started

ygy

Y.gy integration. Manage data, records, and automate workflows. Use when the user wants to interact with Y.gy 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ygy/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 content is a strong, actionable CLI integration guide with executable commands and a clear connection-state workflow including feedback loops. Its weaknesses are conciseness artifacts (a leftover placeholder sentence and a duplicated "Popular actions" section) and a slightly incoherent step numbering in the connection flow.

Suggestions

Remove the placeholder line "I don't have enough information about that app to provide a description." and fold the duplicate "## Popular actions" section into "### Searching for actions" to eliminate redundancy.

Label the connection flow consistently (Step 1: ensure / 1b: wait for ready → Step 2: search and run actions) so the "skip to Step 2" reference resolves cleanly.

Replace the generic `--input '{"key": "value"}'` example with a real Y.gy action payload (e.g. creating a shortened URL) to lift actionability toward 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and a flag table, but it carries unnecessary waste: the stray placeholder line "I don't have enough information about that app to provide a description." and the "## Popular actions" section, which repeats the `action list --intent=QUERY` command already shown under "Searching for actions". It is above 2 because the bulk is tight executable guidance, but below 4 due to those redundant/artifact tokens.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands across the common cases (install, login, headless login completion, connection ensure, poll-wait, action list/run, proxy requests) plus a flag table. It is not 5 because some examples use generic placeholders (`{"key": "value"}` input, `CONNECTION_ID`, `<agentType>`) that leave minor gaps for the reader to fill.	4 / 5
Workflow Clarity	There is a clear install → authenticate → connect → search → run → proxy sequence with an explicit state-checkpoint feedback loop (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR, plus "poll again" after the user acts). It is below 5 because the flow references "Step 2" and "1b" without a cleanly labeled Step 1, leaving the numbering slightly incoherent; it is above 3 because validation checkpoints are clearly present.	4 / 5
Progressive Disclosure	No bundle files exist in references/scripts/assets, so the single SKILL.md carries everything, organized into clearly headed sections (Overview, Working with Y.gy, Connecting, Searching, Popular actions, Proxy, Best practices). Structure is good and navigation is easy; it is below 5 due to the redundant "Popular actions" section and minor organization noise, and above 3 because content is well-sectioned rather than monolithic.	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 provides both a 'what' and an explicit 'when' trigger tied to the Y.gy app name, giving it reasonable completeness and distinctiveness. Its main weakness is specificity: the listed actions (manage data, records, automate workflows) are generic and omit the concrete Y.gy capabilities (URL shortening, bundles, analytics) that would also serve as natural trigger terms.

Suggestions

Replace generic verbs with concrete Y.gy capabilities, e.g. "Shorten URLs, group links into bundles, and view link analytics."

Add natural trigger terms and synonyms users would say, such as "URL shortener", "shorten a link", or "Y.gy analytics", alongside the existing "Use when…" clause.

Keep the explicit "Use when the user wants to interact with Y.gy data" trigger but tie it to specific tasks (shortening links, managing bundles, checking analytics) to lift completeness toward 5.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Y.gy integration") but its actions — "Manage data, records, and automate workflows" — are minimal and generic rather than concrete Y.gy operations, matching the anchor for naming a domain with generic actions. It does not list specific concrete actions, so it stays below 3.	2 / 5
Completeness	Both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Y.gy data") are present. It is not 5 because the 'what' is generic rather than concrete trigger phrases; it is above 3 because the 'when' clause is explicit.	4 / 5
Trigger Term Quality	It includes relevant keywords ("Y.gy", "data", "records", "workflows") and a natural trigger phrase ("Use when the user wants to interact with Y.gy data"), but it omits the common natural terms users would actually say for this app (URL shortening, links, analytics) and their synonyms. It is above 2 because a natural trigger phrase is present, but below 4 due to the missing variations.	3 / 5
Distinctiveness Conflict Risk	The "Y.gy" app name and "interact with Y.gy data" trigger carve out a mostly distinct niche with minimal conflict risk, though the generic verbs (manage data, records, workflows) create minor overlap with general data-management skills. It is below 5 due to that residual overlap and above 3 because the app-named trigger is specific.	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/ygy/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.