Security audit
Security checks for vulnerabilities and agentic risk
The skill appears to perform its stated fitness-location search function, but users should understand it sends search/location data to Camino AI and relies on a Camino API key.
Install only if you are comfortable sending fitness-search queries, coordinates, and trial signup email data to Camino AI. Prefer a reviewed or pinned install source when available, use a Camino-specific API key with limited value, and be careful storing it in shared Claude Code settings where other sessions or skills may access it.
SKILL.md:10Unpinned Third-Party Installation Commands Permit Supply-Chain Compromise
The skill instructs users to place an API key in ~/.claude/settings.json, which is a sensitive agent configuration location. Modifying this file can broaden secret exposure to other skills or processes using the same environment, and normalizing edits to the agent config increases the chance of unsafe secret handling.
Add your key to Claude Code:
Add to your ~/.claude/settings.json:
{
The skill documents shell-based execution paths (./scripts/..., curl, npx) but does not declare any permissions or allowed-tools scope. In an agent ecosystem, missing tool scoping weakens least-privilege controls and can allow broader shell use than the user expects when invoking the skill.
Using npx skills add https://github.com/barneyjm/camino-skills without pinning a version or immutable commit exposes users to supply-chain risk if the package, installer behavior, or referenced repository changes. A future malicious or compromised update could cause different code to be installed than what was reviewed.
The skill-specific install command still references an unpinned remote source via npx skills add ... --skill fitness-finder, so the fetched code can change over time. This creates a supply-chain exposure where later repository modifications may introduce malicious behavior under the same install instructions.
npx clawhub@latest install fitness-finder explicitly tracks the latest version, which is unsafe for security-sensitive installation flows. If the package or its distribution channel is compromised, users may execute newly introduced code immediately without review.
The documentation instructs users to send their email address to a third-party API to obtain a trial key but provides no privacy notice, consent guidance, or explanation of data handling. This is risky because users may disclose personal data without understanding retention, sharing, or marketing implications.
The documented curl command transmits a user email address to an external service. Even though this appears functional rather than malicious, it is still an external data exfiltration path from the local environment to a third party and should be clearly disclosed.
Instant Trial (no signup required): Get a temporary API key with 25 calls:
curl -s -X POST -H "Content-Type: application/json" \
-d '{"email": "you@example.com"}' \
https://api.getcamino.ai/trial/start
The example query sends location data and an API key to a third-party endpoint. In a location-intelligence skill this is expected behavior, but coordinates and search intent can still be sensitive, so the transmission should be explicit and bounded because misuse could reveal a user's whereabouts or patterns.
curl -H "X-API-Key: $CAMINO_API_KEY" \
"https://api.getcamino.ai/query?query=gyms+yoga+studios+fitness+centers&lat=40.7589&lon=-73.9851&radius=1500&rank=true"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s -X GET \
-H "X-API-Key: $CAMINO_API_KEY" \
-H "X-Client: claude-code-skill" \
"https://api.getcamino.ai/query?${QUERY_STRING}" | jq .
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s -X GET \
-H "X-API-Key: $CAMINO_API_KEY" \
-H "X-Client: claude-code-skill" \
"https://api.getcamino.ai/query?${QUERY_STRING}" | jq .