T09 · Insecure Skill Coding Practices
- Location
SKILL.md:103- Finding
Apify API Token Transmitted in URL Query String
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly purpose-aligned for Twitter/X trend research, but its REST fallback documents an unsafe way to pass an Apify API token in a URL.
Review before installing or using. The core behavior matches the advertised Twitter/X trend-research purpose, but do not use the REST fallback as written with a real token in the URL; prefer an authorization header or managed Apify tooling, protect any .env file, and avoid sending confidential campaign, customer, or strategy terms as search queries.
SKILL.md:103Apify API Token Transmitted in URL Query String
The manifest description lists many natural-language trigger phrasings such as finding what a target audience is talking about or identifying conversations to join, but it does not define exclusion conditions or negative examples. This can cause overlap with general research or social-media analysis requests and may lead to unintended invocation.
The skill explicitly sends user-supplied search terms to a third-party service (Apify), which is an external data transmission boundary. While this is expected for the skill's purpose, it becomes a real security/privacy concern if users are not clearly informed that their prompts, search queries, or derived sensitive terms may be transmitted off-platform to an external provider.
REST API fallback:
curl -X POST "https://api.apify.com/v2/acts/apidojo~tweet-scraper/runs?token=$APIFY_TOKEN" -H "Content-Type: application/json" -d '{
"searchTerms": ["B2B SaaS", "#saas", "B2B SaaS 2026"],
"maxItems": 500,
"tweetLanguage": "en"
The skill explicitly sends user-supplied search terms to a third-party service (Apify), which is an external data transmission boundary. While this is expected for the skill's purpose, it becomes a real security/privacy concern if users are not clearly informed that their prompts, search queries, or derived sensitive terms may be transmitted off-platform to an external provider.
REST API fallback:
curl -X POST "https://api.apify.com/v2/acts/apidojo~tweet-scraper/runs?token=$APIFY_TOKEN" -H "Content-Type: application/json" -d '{
"searchTerms": ["B2B SaaS", "#saas", "B2B SaaS 2026"],
"maxItems": 500,
"tweetLanguage": "en"
The markdown includes commands that write CSV and JSON output files automatically, but the skill description does not clearly warn users that running these examples will create files on disk. For markdown files, behaviors that affect user data or system state should be disclosed so the user understands the side effect before use.