Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent patent-litigation research workflow with optional local reporting helpers and no evidence of hidden execution, persistence, or exfiltration.
Install only if you intend to let the agent use PatSnap connectors and public sources for litigation research. Keep API keys out of prompts and reports, approve only the needed connectors, and direct generated JSON/HTML/CSV files to a chosen output folder because reports may contain sensitive legal or business analysis.
There is a clear description-behavior mismatch. The description promises a substantial analytical workflow for patent-litigation exposure monitoring and report generation, but the provided code does not implement any of those capabilities. Its only observable behavior is printing an informational message. This is a materially different and far narrower primary purpose than declared.
The description presents an end-user skill that monitors litigation exposure and produces substantive evidence-backed analysis and reports. The supplied code does not perform that monitoring or analysis. Instead, it initializes an empty target-centric record for up to five parties, validates that a populated record conforms to expected schema rules, and writes the empty JSON structure to disk. While the schema contains fields related to cases, patents, inventors, geography, conclusions, and timelines, the code does not populate them from any connectors or primary sources, nor does it generate HTML or CSV outputs. This is a material difference in primary purpose and implemented capability, not merely an internal supporting detail.
The skill explicitly instructs use of networked patent and public-record sources, local script execution, and report artifact creation, but it does not declare any tool scope or allowed-tools boundaries. That creates an over-privileged/under-specified execution surface where a host agent may grant broader file, write, or network access than intended, increasing the chance of data exfiltration, unintended file modification, or use of unapproved external endpoints.
The instruction 'Use one portable, static, English HTML file' imposes a specific language on outputs. Under the policy criteria, forcing a locale/language without user opt-in is a natural-language policy violation unless the constraint is explicitly justified as region-specific or optional.
The configuration sets DEFAULT_REPORT_LANG = "en", which imposes a specific language by default. Under the policy, language constraints should offer user choice or be clearly justified as region-specific; this file does not show such an opt-in or justification.
The file’s rendering contract states that the report language defaults to English. This is a natural-language locale policy constraint, and the file does not indicate user choice or a documented justification for enforcing English as the default language.
No suspicious patterns detected.
