Dialogflow Cx Conversations
Analysis
The skill appears to do what it claims for Dialogflow CX, but it needs Google Cloud access and sends conversation text to Dialogflow.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
"https://dialogflow.googleapis.com/v3beta1/projects/${PROJECT_ID}/locations/${LOCATION}/agents/${AGENT_ID}/testCases"The documentation includes authenticated POST operations that can create Dialogflow test-case resources; this matches the testing purpose but is still a cloud-side mutation.
Install:
pip install google-cloud-dialogflow-cx google-authThe helper script instructs users to install external Python packages without pinned versions; this is a normal setup step for the Google SDK but still relies on package-source trust.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
- Service account or OAuth credentials with Dialogflow API access - `gcloud` CLI authenticated OR bearer token
The skill needs Google Cloud credentials to call Dialogflow; this is purpose-aligned, but the effective permissions depend on the credential the user provides.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
| **Sessions** | Conversation instances with state | | **Detect Intent** | Process user input and get responses |
The skill sends user text into Dialogflow sessions that maintain conversation state; this is expected for the product but means prompts may become part of provider-side session context.
