Name: fomo
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

fomo

Fomo integration. Manage Organizations. Use when the user wants to interact with Fomo data.

Quality

68%

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

Quality

Content

75%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 clear connection workflow, supported by good section structure. Its main weaknesses are minor verbosity in the intro and best-practices prose and the absence of validation guidance around destructive event operations.

Suggestions

Trim the opening "Fomo is a marketing tool..." paragraph to one line or remove it; Claude can infer the product context from the docs link.

Add a brief validation/retry note for destructive actions (e.g. verify an event exists with get-event before update-event, and confirm before delete-event) to lift workflow_clarity past the destructive-ops cap.

Resolve the dangling "Step 2" reference by labeling the connection steps consistently or removing the cross-reference.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient commands and tables, but the opening paragraph explains what Fomo is and the best-practices section editorializes ("burn less tokens", "This is the fastest way"), adding tokens Claude doesn't need.	3 / 5
Actionability	Commands are copy-paste ready throughout (install, login, connection ensure/get, action list/run, request) with a popular-actions table and proxy flag reference covering the common cases.	5 / 5
Workflow Clarity	The connection workflow is well-sequenced with state checks and a poll-after-user-action feedback loop, but the "Step 2" reference is dangling and destructive event ops (delete-event, update-event) lack explicit validation guidance.	4 / 5
Progressive Disclosure	No bundle files exist; the single ~150-line SKILL.md is organized into clear sections with content appropriately inline for a CLI integration skill, though some reference material (full action catalog, proxy options) could optionally be split out.	4 / 5
	Total	16 / 20 Passed

Description

61%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 identifies the Fomo niche and includes an explicit "Use when" trigger, but its capability statement is thin and slightly off-target relative to the skill's real entities. Expanding the action list and trigger synonyms would raise it from solid to strong.

Suggestions

Replace or augment "Manage Organizations" with the skill's actual core actions, e.g. "Create, update, search, and list social-proof events, manage templates, and retrieve statistics."

Broaden the trigger clause with natural synonyms: "Use when the user wants to manage Fomo events, templates, notifications, or social-proof data."

Keep the third-person voice but make the "what" enumerate 3-4 concrete actions to lift specificity from 2 toward 4.

Dimension	Reasoning	Score
Specificity	"Manage Organizations" names only one action and is arguably misaligned with the body's actual entities (Event, Account, Project), so actions are minimal and slightly inaccurate rather than comprehensive.	2 / 5
Completeness	It states both what ("Manage Organizations") and when ("Use when the user wants to interact with Fomo data"), but the when clause is generic rather than listing concrete trigger phrases, so it falls short of a 5.	4 / 5
Trigger Term Quality	"Fomo" and "Fomo data" are natural terms a user would say, but common variations like social proof, events, notifications, or templates are missing.	3 / 5
Distinctiveness Conflict Risk	Fomo is a specific named third-party app, giving the skill a clear niche with a distinct trigger ("interact with Fomo data") and minimal conflict risk with other skills.	5 / 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/fomo/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.