Security audit
Security checks for vulnerabilities and agentic risk
This skill is coherent for comparing job postings, with disclosed Crawlora API use and no persistence, but users should know their job queries, public URLs, and Crawlora key are sent to Crawlora.
Install this only if you are comfortable using Crawlora for job-posting research. Treat job searches, employer slugs, public posting URLs, and your Crawlora API key as data shared with Crawlora; keep web_scrape use limited to public job-related pages and avoid sending private profile, resume, or account information unless you intentionally choose to do so.
The skill invokes a shell script but does not declare any explicit tool scope or allowed-tools boundary. That creates an avoidable capability gap where an agent may execute shell commands more broadly than intended, increasing the risk of unintended command execution or access beyond the skill's stated purpose.
The skill directs the agent to send an API key in requests to an external service and to transmit query data to a third-party endpoint. External transmission is expected for this skill's function, but it still creates a real data-exposure boundary: user-provided search terms, employer targets, and credentials could be sent off-platform if not tightly controlled.
Set `CRAWLORA_API_KEY` to your Crawlora key. Prefer the listed Crawlora MCP tools
when connected; otherwise use the bundled `scripts/crawlora.sh`, which sends
`x-api-key` to `https://api.crawlora.net/api/v1`. Read
[reference/endpoints.md](reference/endpoints.md) for exact methods and parameters.
Check application `code` as well as HTTP status; payloads are inside `data`.
Stop on authentication errors, back off on `429`, and retry a transient upstream
The skill is for comparing job postings, but the endpoint list includes a general-purpose web_scrape capability that can fetch arbitrary public URLs. That materially expands the skill's reachable surface beyond the stated purpose, enabling misuse for unrelated scraping, policy bypass attempts, or exfiltration of user-supplied targets through an external service. In this context, the mismatch between purpose and capability makes the finding more dangerous, not less.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
#!/usr/bin/env bash
# Crawlora REST helper — minimal, dependency-free (curl only).
# Calls https://api.crawlora.net/api/v1 with your Crawlora API key.
# Get a free key (2,000 credits/mo, no card) at https://crawlora.net?utm_source=github&utm_medium=referral&utm_campaign=crawlora-skills.
#
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
#!/usr/bin/env bash
# Crawlora REST helper — minimal, dependency-free (curl only).
# Calls https://api.crawlora.net/api/v1 with your Crawlora API key.
# Get a free key (2,000 credits/mo, no card) at https://crawlora.net?utm_source=github&utm_medium=referral&utm_campaign=crawlora-skills.
#
# Usage:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
#!/usr/bin/env bash
# Crawlora REST helper — minimal, dependency-free (curl only).
# Calls https://api.crawlora.net/api/v1 with your Crawlora API key.
# Get a free key (2,000 credits/mo, no card) at https://crawlora.net?utm_source=github&utm_medium=referral&utm_campaign=crawlora-skills.
#
# Usage:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
#!/usr/bin/env bash
# Crawlora REST helper — minimal, dependency-free (curl only).
# Calls https://api.crawlora.net/api/v1 with your Crawlora API key.
# Get a free key (2,000 credits/mo, no card) at https://crawlora.net?utm_source=github&utm_medium=referral&utm_campaign=crawlora-skills.
#
# Usage:
The comment says the helper is limited to documented Crawlora job routes, but the implementation also allows /web/scrape. This documentation/code mismatch can mislead reviewers and downstream users about the true authority of the skill, making risky behavior easier to overlook in security-sensitive agent environments.
The helper explicitly permits POST access to /web/scrape, which is a generic web-scraping endpoint outside the narrowly described job-posting comparison routes. In an agent-skill context, this expands capability from fixed job-data retrieval to arbitrary remote fetching, increasing the risk of misuse for unscoped collection, policy bypass, or unintended data exfiltration via a third-party API.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
# config supplies the header and is removed automatically on exit.
umask 077
curl_config="$(mktemp "${TMPDIR:-/tmp}/crawlora-curl.XXXXXX")"
chmod 600 "$curl_config"
trap 'rm -f "$curl_config"' EXIT
printf 'header = "x-api-key: %s"\n' "$CRAWLORA_API_KEY" >"$curl_config"
auth=(--config "$curl_config")
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
[ -n "$body" ] || body='{}'
# Stream the body on stdin so curl never interprets a user value as its
# @file shorthand (and cannot read local files supplied in a request body).
printf '%s' "$body" | curl -q -fsS -X "$method" "${auth[@]}" \
-H "Content-Type: application/json" --data-binary @- "${base}${path}"
fi
This markdown file describes the skill's purpose in broad terms but does not define specific trigger phrases, activation conditions, or exclusions. Without clear trigger boundaries or negative examples, the skill could be invoked for generic job-search or career-comparison requests beyond its intended scope.
No suspicious patterns detected.