Name: ifttt
Rating: 64.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

ifttt

IFTTT integration. Manage Applets, Services, Users. Use when the user wants to interact with IFTTT data.

Quality

77%

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

Quality

Content

76%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 copy-paste CLI commands and good organization, but lacks validation/verification steps for mutating operations, which caps workflow clarity. Minor verbosity and a duplicated discovery command keep conciseness and progressive disclosure just below the top tier.

Suggestions

Add validation checkpoints for destructive operations: after `action run` or proxy POST/PUT/DELETE calls, verify the result (e.g., re-list or check response status) before declaring success, to lift workflow clarity above 3.

Remove the redundant discovery command in "Popular actions" (it duplicates the "Searching for actions" section) and cut the IFTTT-concept intro paragraph to improve conciseness.

Consider moving the full proxy flag table or extended action examples into a reference file to better split content and reach progressive disclosure 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven, but the intro paragraph explains what IFTTT is (a concept Claude already knows) and the "Popular actions" section repeats the discovery command already shown, leaving minor over-explanation to trim short of a 5.	4 / 5
Actionability	Copy-paste-ready `npx @membranehq/cli@latest` commands cover login, connect, list, run, and proxy flows, with clear placeholders (CONNECTION_ID, ACTION_ID) and a flag table, matching the 5 anchor for fully executable guidance across common cases.	5 / 5
Workflow Clarity	There is a rough sequence (login → connect → list → run → proxy), but no validation checkpoints for destructive/batch-capable operations such as action runs and proxy POST/PUT/DELETE requests, which caps workflow clarity at 3 per the destructive-operation rule.	3 / 5
Progressive Disclosure	Clean section headers organize a single-purpose skill with no external bundle needed, but at ~118 lines with a duplicated "Popular actions" discovery block it sits at the 4 anchor rather than the well-split 5.	4 / 5
	Total	16 / 20 Passed

Description

78%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.

A solid description that states both capability and an explicit trigger clause with distinct IFTTT-specific vocabulary. It is held back from the top tier by generic action verbs and a trigger clause that lacks concrete natural variations.

Suggestions

Replace the single generic verb "Manage" with distinct concrete actions (e.g., "Create, list, and update Applets and Services") to reach specificity 5.

Expand the trigger clause with concrete natural phrases (e.g., "Use when the user wants to create or manage IFTTT applets, connect triggers and actions, or query IFTTT data") to lift completeness and trigger_term_quality.

Add the related domain nouns ("Triggers", "Actions") that users naturally mention so trigger keyword coverage is comprehensive.

Dimension	Reasoning	Score
Specificity	Names three concrete managed entities ("Manage Applets, Services, Users") but relies on a single generic verb applied to a list rather than multiple distinct actions, so it sits above the 3 anchor but short of comprehensive coverage at 5.	4 / 5
Completeness	Explicitly answers both what ("Manage Applets, Services, Users") and when ("Use when the user wants to interact with IFTTT data"), but the trigger clause is generic rather than listing concrete trigger phrases, matching the 4 anchor rather than 5.	4 / 5
Trigger Term Quality	Includes natural domain terms ("IFTTT", "Applets", "Services", "IFTTT data") with an explicit "Use when the user wants to interact with IFTTT data" trigger, but misses common variations and synonyms like "triggers", "actions", or "connect IFTTT".	4 / 5
Distinctiveness Conflict Risk	The IFTTT-specific vocabulary (Applets, Services) carves a clear niche with minimal overlap risk against other skills, matching the 5 anchor for distinct triggers.	5 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: membranedev/application-skills
Path: skills/ifttt/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.