Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md - [ ] No API keys or secrets are embedded in `SKILL.md` or `package.json`
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a documentation-only connector for a third-party document extraction API, and its sensitive data transmission is disclosed and aligned with its stated purpose.
Install only if you are comfortable sending selected documents to SkillBoss API Hub. Use environment variables or a secret store for the API key, avoid uploading highly sensitive regulated data until you have reviewed the provider's privacy and retention terms, and test with non-sensitive samples first.
Referenced artifact was not completely inspected
- [ ] No API keys or secrets are embedded in `SKILL.md` or `package.json`
The referenced endpoint is a third-party API, and the skill's primary function depends on sending user-supplied documents there. Even though HTTPS is used and the documentation includes some privacy warnings, this still represents external transmission of potentially sensitive data and credentials.
curl -X POST "https://api.heybossai.com/v1/run" \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "reducto/parse", "inputs": {"document_url": "https://example.com/document.pdf"}}'
The referenced endpoint is a third-party API, and the skill's primary function depends on sending user-supplied documents there. Even though HTTPS is used and the documentation includes some privacy warnings, this still represents external transmission of potentially sensitive data and credentials.
curl -X POST "https://api.heybossai.com/v1/run" \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "reducto/parse", "inputs": {"document_url": "https://example.com/document.pdf"}}'
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
**Security Note:** If storing API keys in `~/.openclaw/openclaw.json`:
- Set file permissions: `chmod 600 ~/.openclaw/openclaw.json`
- Never commit this file to version control
- Prefer environment variables or your agent's secret store when possible
- Rotate keys regularly and limit API key permissions if supported
This example again sends documents to an external service for processing. Because the skill is specifically meant to extract document contents, the risk is not hypothetical: sensitive document text may be disclosed to the provider and retained or further processed outside the user's environment.
curl -X POST "https://api.heybossai.com/v1/run" \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "reducto/parse", "inputs": {"document_url": "https://example.com/document.pdf"}}'
This example uploads base64-encoded file contents directly to the external API, which increases the likelihood that full raw document contents, including PII or financial data, are transmitted. The added JSON extraction use case can encourage users to process especially sensitive structured records such as invoice numbers, dates, totals, and vendor information.
Simple field list:
curl -X POST "https://api.heybossai.com/v1/run" \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
Schema-based extraction still requires uploading the underlying document to a third-party API, so the security concern remains the external disclosure of the full source material. The structured nature of the extraction may also make downstream misuse easier if sensitive financial values are automatically normalized and exposed.
With JSON schema:
curl -X POST "https://api.heybossai.com/v1/run" \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
Table extraction to CSV entails sending document data to an outside endpoint, with the same confidentiality concerns as other examples. Tabular documents often contain financial, operational, or personally identifiable information that becomes easier to export and redistribute once converted to CSV.
curl -X POST "https://api.heybossai.com/v1/run" \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "reducto/parse", "inputs": {"document_url": "https://example.com/table.pdf"}}'
The async example uploads full file contents to the provider and stores processing state remotely via a record ID, extending the time window during which sensitive documents may reside with the third party. This increases exposure relative to transient local-only processing because both content and metadata may persist beyond the immediate request.
Queue the document:
curl -X POST "https://api.heybossai.com/v1/run" \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "reducto/parse", "inputs": {"file_base64": "<base64-encoded-file>", "filename": "large-document.pdf", "output_format": "markdown", "async": true}}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Poll for results:
curl -X POST "https://api.heybossai.com/v1/run" \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "reducto/parse", "inputs": {"document_url": "https://example.com/document.pdf"}}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Poll for results:
curl -X POST "https://api.heybossai.com/v1/run" \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "reducto/parse", "inputs": {"document_url": "https://example.com/document.pdf"}}'
No suspicious patterns detected.