Security audit
Security checks for vulnerabilities and agentic risk
This skill is a clearly scoped PoYo API helper that only submits user-prepared persona data when the user asks it to.
Install only if you intend to use PoYo's Generate Persona API. Keep POYO_API_KEY in a server-side environment, review the JSON payload before submission, and avoid sending private task IDs, audio IDs, callback URLs, or confidential style descriptions unless you trust PoYo and the callback receiver.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Content-Type: application/json
Get API keys from <https://poyo.ai/dashboard/api-key>.
Recommended skill env var:
The skill declares shell-capable behavior via its metadata (curl requirement and a referenced submission script) but does not declare any explicit tool scope such as permissions or allowed-tools. This creates an authorization ambiguity where an agent platform may permit broader shell access than intended, increasing the risk of unintended command execution or unsafe use of environment secrets like POYO_API_KEY.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer YOUR_API_KEY" \
--header "Content-Type: application/json" \
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
: "${POYO_API_KEY:?POYO_API_KEY is required}"
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer ${POYO_API_KEY}" \
--header "Content-Type: application/json" \
This shell script performs an HTTP POST to a remote service and transmits the full contents of the user-supplied JSON payload, but the script provides no confirmation prompt, logging, or explanatory comment/docstring about that data transfer. Because network transmission of user or system data is safety-relevant for code files, the lack of any disclosure is a missing warning under the rule.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
: "${POYO_API_KEY:?POYO_API_KEY is required}"
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer ${POYO_API_KEY}" \
--header "Content-Type: application/json" \
--data @"$1"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
: "${POYO_API_KEY:?POYO_API_KEY is required}"
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer ${POYO_API_KEY}" \
--header "Content-Type: application/json" \
--data @"$1"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
: "${POYO_API_KEY:?POYO_API_KEY is required}"
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer ${POYO_API_KEY}" \
--header "Content-Type: application/json" \
--data @"$1"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
: "${POYO_API_KEY:?POYO_API_KEY is required}"
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer ${POYO_API_KEY}" \
--header "Content-Type: application/json" \
--data @"$1"
The script requires and uses the POYO_API_KEY environment variable, which is a sensitive credential, but there is no accompanying comment, user-facing disclosure, or warning about this credential usage. For code files, access to sensitive environment variables should have some visible disclosure unless already clearly documented elsewhere.