Security audit
Security checks for vulnerabilities and agentic risk
This is a disclosed Dataify routing helper with no embedded code, persistence, or token exposure, though users should be aware it can invoke Dataify workflows for clear low-risk requests.
Install this if you want an agent to route requests through Dataify skills. Review requests that could spend credits, run multiple pages, download media, or use recurring monitoring, and keep DATAIFY_API_TOKEN in the environment rather than chat.
The manifest description is broad enough to match many generic collection, search, scraping, monitoring, and marketplace requests, which can cause the router skill to activate in situations beyond its intended scope. Over-broad activation increases the chance of misrouting user tasks to powerful downstream skills, creating unnecessary data access or unintended execution paths.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
## Account CTA policy
- Show a prominent Dataify account CTA only when the API token is missing, rejected/invalid, or the account has insufficient credits.
- For a missing token, offer https://dashboard.dataify.com/login?utm_source=skill and state: New accounts get 50 free credits, enough for about 6,000 trial results, valid for 7 days, and only successful requests are billed. Never ask the user to paste the token into chat.
- Detect the current operating system and shell. Show only the matching session-scoped setup command first (`export` for macOS/Linux shells, `$env:` for Windows PowerShell, or `set` for Windows Command Prompt). Show other platforms or persistent setup only when detection is ambiguous or the user asks.
- After the user says the token is configured, verify only whether `DATAIFY_API_TOKEN` is present; never print its value. If verification succeeds, continue the original task without asking the user to repeat it.
- Explain that persistent shell changes may require a new terminal or restarting the agent application. Do not recommend a project `.env` unless the execution path explicitly loads it, and ensure `.env` is ignored by version control.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- Show a prominent Dataify account CTA only when the API token is missing, rejected/invalid, or the account has insufficient credits.
- For a missing token, offer https://dashboard.dataify.com/login?utm_source=skill and state: New accounts get 50 free credits, enough for about 6,000 trial results, valid for 7 days, and only successful requests are billed. Never ask the user to paste the token into chat.
- Detect the current operating system and shell. Show only the matching session-scoped setup command first (`export` for macOS/Linux shells, `$env:` for Windows PowerShell, or `set` for Windows Command Prompt). Show other platforms or persistent setup only when detection is ambiguous or the user asks.
- After the user says the token is configured, verify only whether `DATAIFY_API_TOKEN` is present; never print its value. If verification succeeds, continue the original task without asking the user to repeat it.
- Explain that persistent shell changes may require a new terminal or restarting the agent application. Do not recommend a project `.env` unless the execution path explicitly loads it, and ensure `.env` is ignored by version control.
- For an invalid token, direct the user to API-key management without implying that a new registration is required. For insufficient credits, direct the user to balance or recharge management.
- During normal submission, processing, and successful completion, do not promote registration or the Dashboard. Never expose the token or include it in CTA attribution parameters.
The skill is configured for implicit invocation and uses a broad routing description plus a default prompt that encourages automatic selection and execution of a Dataify workflow. This can cause the agent to invoke the skill for loosely related user requests, leading to unintended external data collection actions, scope creep, or use of a broader capability set than the user explicitly requested.
Treating the Chinese phrase “直接执行” as implicit confirmation without verifying the user's language or intent can bypass a normal confirmation safeguard. This is risky because confirmation gates are meant to protect higher-cost or higher-impact actions, and a phrase may appear in quoted text, copied content, or be misunderstood by the user.
No suspicious patterns detected.