Dialogflow Cx Advanced
Analysis
This skill is coherent for Dialogflow CX administration, but it gives an agent high-impact Google Cloud deployment and webhook authority that should be reviewed carefully before use.
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.
### Deploy Flow to Environment
POST /v3beta1/{environment}:deployFlowThis documents an authenticated operation that changes which flow version is deployed to a Dialogflow environment, with no explicit approval, environment scoping, or rollback guidance.
Install:
pip install google-cloud-dialogflow-cx google-authThe script documents installing unpinned Python packages, while the registry has no install spec; this is user-directed and relevant to the skill, but users should still verify package provenance.
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 requires Google Cloud credentials capable of Dialogflow API access, while the registry metadata declares no primary credential and the artifacts do not specify least-privilege roles or token-use limits.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
"sessionInfo": {
"session": "projects/.../sessions/...",
"parameters": { ... }
},
"text": "user input"The webhook reference shows that external fulfillment endpoints may receive end-user text and session parameters; this is expected for Dialogflow webhooks but privacy-sensitive.
