Name: google-dialogflow
Rating: 59.2 (1 reviews)
Author: membranedev

google-dialogflow

Google Dialogflow integration. Manage data, records, and automate workflows. Use when the user wants to interact with Google Dialogflow 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/google-dialogflow/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 content is highly actionable, with concrete executable commands and a clear connection-state feedback loop. Its main gaps are a removable concept-explaining intro paragraph and slightly inconsistent step numbering.

Suggestions

Delete the opening paragraph that defines what Dialogflow is and who uses it; Claude already knows this and it costs context tokens.

Fix the step numbering so the referenced 'Step 2' has a matching header and the '1b' subsection has a corresponding '1a', making the connection workflow sequence unambiguous.

De-duplicate the action-discovery command between 'Searching for actions' and 'Popular actions', and add an explicit 'verify the output field' checkpoint after running an action.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explaining what Dialogflow is and who uses it is unnecessary background Claude already knows, and a few phrases pad the auth explanation, though the bulk of CLI commands and the flag table are efficiently presented.	3 / 5
Actionability	The body provides fully executable, copy-paste-ready commands across the whole lifecycle (install, login, connection ensure, polling, action list/run, proxy) plus a concrete flag table, covering the common cases.	5 / 5
Workflow Clarity	The connection-readiness flow is a clear sequence with a real validate-act-retry feedback loop over explicit states (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but step numbering is inconsistent ('Step 2' referenced with no matching header, '1b' with no '1a') and post-run result verification is only implicit.	4 / 5
Progressive Disclosure	The body is well-organized into clearly labeled sections and is appropriately self-contained with no bundle files, but it carries some density and redundancy (the search command reappears under 'Popular actions') that keep it short of a lean overview pointing to one-level references.	4 / 5
	Total	16 / 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 is competent: it names the integration, lists a few high-level actions, and includes an explicit 'Use when' clause. Its weakness is generality — the actions and triggers lack Dialogflow-specific concreteness and natural synonyms.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with Dialogflow-specific actions such as managing agents, intents, entity types, sessions, and webhooks.

Expand the 'Use when' trigger with natural user phrasing and synonyms, e.g. 'Use when the user wants to build or manage Dialogflow chatbots, conversational agents, intents, or voice assistants.'

Reference the file extensions or platform terms users actually mention (e.g. Dialogflow ES/CX, intents, entities) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	It names the Dialogflow domain plus a couple of actions ('Manage data, records, and automate workflows'), but those actions are generic abstractions rather than concrete Dialogflow-specific operations like intents, entities, or agents, so it is not comprehensive.	3 / 5
Completeness	It states a 'what' (manage data, records, automate workflows) and an explicit 'Use when the user wants to interact with Google Dialogflow data' clause, but the 'when' is somewhat generic and lacks concrete trigger phrases.	4 / 5
Trigger Term Quality	The trigger repeats the product name 'Google Dialogflow' but offers no natural synonyms or variations users would say (e.g. chatbot, conversational AI, intents, voice assistant), so coverage is relevant but incomplete.	3 / 5
Distinctiveness Conflict Risk	The named product 'Google Dialogflow' makes it largely distinct, though the generic surrounding language ('manage data, records') leaves minor overlap risk with broad data-management skills.	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/google-dialogflow/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.