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

Blog Docs Log in Get started

respondio

Respond.io integration. Manage Organizations. Use when the user wants to interact with Respond.io 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/respondio/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 delivers strong, executable CLI guidance with a solid connection-readiness state machine and clear sectioning. Its main weaknesses are a marketing-flavored intro, a stub 'Popular actions' section, and inconsistent step labeling that slightly muddies the workflow.

Suggestions

Trim the opening paragraph to only what execution requires; remove the marketing framing about which teams use Respond.io.

Either populate 'Popular actions' with concrete example actions (e.g., list contacts, send broadcast, create template) or remove the stub heading so it does not promise content it does not deliver.

Replace the dangling 'Step 2' / '1b' references with a consistent numbered workflow (1. Install, 2. Authenticate, 3. Connect, 4. Discover actions, 5. Run) so the sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-focused and efficient, but the opening marketing paragraph ("used by sales, marketing, and support teams to centralize conversations, automate workflows...") and lines like "so you can focus on the integration logic rather than auth plumbing" are unnecessary explanation that could be trimmed, fitting the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	Provides concrete, executable commands throughout (install, login, connection ensure, action list/run, request with a full flag table) that are largely copy-paste ready; not a 5 because the 'Popular actions' section is a stub that redirects to discovery rather than listing concrete actions, and JSON input examples use only placeholder values.	4 / 5
Workflow Clarity	There is a clear install → auth → connect → search → run sequence with a state-machine feedback loop for connection readiness (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and re-polling after user action; not a 5 because step labels are inconsistent (dangling 'Step 2' and '1b' references with no labeled 1a or Step 2) and the 'Popular actions' section breaks the flow.	4 / 5
Progressive Disclosure	The single file is well-organized into clearly headed sections with no external bundle files and nothing that clearly demands splitting out; not a 5 because the 'Popular actions' stub and inconsistent step numbering are minor organization gaps, and the file exceeds the simple-skill size where structure alone earns a 5.	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 correctly includes an explicit 'Use when...' trigger and names a concrete domain, but it lists only a single action and offers limited trigger-term variations. It is distinct thanks to the Respond.io brand yet remains thin on capability coverage.

Suggestions

Expand the 'what' with several concrete actions drawn from the body (e.g., 'manage contacts, conversations, WhatsApp Business accounts, broadcasts, templates, and reports') to raise specificity.

Add natural trigger synonyms users might say (e.g., 'Respond.io contacts, WhatsApp messages, broadcasts, or templates') so the description triggers on more phrasings than just the brand name.

Dimension	Reasoning	Score
Specificity	Names the domain ("Respond.io integration") and one concrete action ("Manage Organizations"), matching the anchor for domain + 1-2 actions without comprehensive coverage; not a 4 since only one action is listed rather than several.	3 / 5
Completeness	Provides both a 'what' ("Respond.io integration. Manage Organizations.") and an explicit 'when' ("Use when the user wants to interact with Respond.io data."), placing it at the both-present anchor; not a 5 because the 'what' is thin and only one trigger phrase is given.	4 / 5
Trigger Term Quality	Includes the brand "Respond.io" and the phrase "interact with Respond.io data", but lacks synonyms or variations (e.g., contacts, WhatsApp messages, broadcasts) users might naturally say, fitting the 'some relevant keywords' anchor.	3 / 5
Distinctiveness Conflict Risk	The specific brand "Respond.io" gives a clear niche with low conflict risk, but the generic "interact with Respond.io data" phrasing leaves minor overlap risk with other messaging integrations, fitting the 'mostly distinct' anchor rather than the fully-distinct anchor 5.	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/respondio/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.