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

Blog Docs Log in Get started

ifood

iFood integration. Manage Recordses. Use when the user wants to interact with iFood 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/ifood/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 CLI commands and a solid connection-state workflow including retry loops, but it carries some padding and suffers from broken step numbering that hurts navigation. Splitting the lengthy state-handling reference into a separate file and tightening prose would improve conciseness and structure.

Suggestions

Fix the inconsistent step numbering: add a "1a"/Step 1 label and define an explicit "Step 2" so the "skip to Step 2" reference resolves.

Trim filler sentences (e.g. "so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection") to reduce token overhead.

Consider moving the detailed clientAction state table (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) into a references file, keeping only the happy path inline.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes several padded sentences such as "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection" that could be trimmed.	3 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands for every common case — install, login, connection ensure, polling, action list/run, and proxy requests — with a clear flags table covering the parameters.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with polling feedback loops (poll until READY, retry after CLIENT_ACTION_REQUIRED), but the step numbering is inconsistent — a "1b" with no "1a" and a dangling "skip to Step 2" with no Step 2 — leaving a minor navigation gap.	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers and no nested references, and no external bundle files are needed; however, at ~135 lines it exceeds the simple-skill threshold and the detailed clientAction state reference could arguably live in its own file.	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 cleanly answers both what and when and is highly distinct thanks to the named platform, but it is thin on concrete capability verbs and trigger synonyms, and "Manage Recordses" is awkwardly worded. Tightening the action list and adding natural synonyms would lift specificity and trigger quality.

Suggestions

Replace the generic "Manage Recordses" with concrete operations, e.g. "Create, read, update, delete, and list iFood Records."

Expand the trigger clause with natural user phrasings, e.g. "Use when the user wants to query iFood orders, restaurants, menus, or manage iFood data."

Fix the awkward plural "Recordses" to "Records" for a cleaner, more natural description.

Dimension	Reasoning	Score
Specificity	The description names the domain ("iFood integration") and one generic action ("Manage Recordses"), but offers no concrete operations like create/read/update/delete — matching the anchor that names the domain with minimal or generic actions.	2 / 5
Completeness	Both a "what" (iFood integration, manage Records) and an explicit "when" clause are present; the "when" is somewhat generic but clearly stated, fitting the anchor where both exist with room to be more specific.	4 / 5
Trigger Term Quality	It includes an explicit trigger ("Use when the user wants to interact with iFood data") with the brand keyword, but lacks common variations or synonyms such as orders, restaurants, menus, or food delivery.	3 / 5
Distinctiveness Conflict Risk	iFood is a uniquely named platform and the trigger ("iFood data") is brand-specific, giving it a clear niche with minimal overlap risk against 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/ifood/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.