Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md 2. `references/templates/patents_template.html` → `patents.html`
Security audit
Security checks for vulnerabilities and agentic risk
This skill appears to be a legitimate patent-research report generator with disclosed PatSnap connector use and local report outputs.
Install this if you want an English patent-opportunity report workflow and are comfortable using PatSnap MCP connectors. Run it in a dedicated output folder, review the generated provenance files for query details and assumptions, and treat the report as decision support rather than legal, investment, valuation, or freedom-to-operate advice.
Referenced artifact was not completely inspected
2. `references/templates/patents_template.html` → `patents.html`
This instruction forces a specific language/locale choice regardless of user preference. The file does not offer the user a language choice or explain a region-specific compliance reason for restricting output to English.
The instruction says to require sufficient English narrative and sets an English-word-count quality gate. This is a natural-language locale constraint in a markdown prompt, and the file does not provide user opt-in or explain a region-specific/business justification for forcing English.
The instruction explicitly requires using English as the report and connector language. This is a natural-language locale policy constraint that does not offer the user a language choice or opt-in, which matches the policy-violation category.
The skill explicitly instructs the agent to create and verify ten output files, but it does not prominently warn the user up front that workspace writes will occur. In an agent environment, implicit file creation can surprise users, overwrite existing artifacts, or leak derived content into shared workspaces even when the task itself is legitimate.
This markdown file applies to SQP-2, and line L135 explicitly directs persistence of data to a local file. The surrounding instructions do not disclose this storage behavior or warn that user/request data and search metadata will be written to disk.
The instruction requires a 'concise English name' for each subfield, which imposes a specific language choice in natural-language guidance. The file does not indicate that English is optional, user-selected, or justified as a documented locale constraint.
The HTML root sets lang="en", which expresses a fixed English-language locale in the template. Under the policy rule, forcing a specific language without user opt-in or documented justification is a natural-language locale policy issue.
No suspicious patterns detected.