Target Intelligence
AdvisoryAudited by Static analysis on May 13, 2026.
Overview
No suspicious patterns detected.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Queries may consume or access PatSnap resources using the user's API key, and the key could be exposed if the setup command or MCP config is shared.
The skill requires a PatSnap API key and places it in the MCP server URL, giving the agent delegated access to PatSnap services under the user's account.
Log in to https://open.patsnap.com, go to **API Keys**, and create a new key... "https://connect.patsnap.com/096456/logic-mcp?apiKey=sk-xxxxxxxxxxxx"
Use a dedicated, revocable PatSnap API key, avoid sharing terminal history or MCP configuration containing the key, and rotate the key if it is exposed.
Information entered into target-intelligence requests may be sent to PatSnap MCP services for processing and retrieval.
The skill depends on remote MCP services, so target queries and tool interactions flow between the user's agent and PatSnap-operated services.
**PatSnap LifeScience MCP Services** give Claude Code direct access to 200M+ patents, drug R&D records, and biological data.
Use this skill only for queries you are comfortable sending to PatSnap, and verify that the MCP servers are configured from the official PatSnap pages.
A small automatic API call may occur before the user's actual analysis request is processed.
The skill directs the agent to make a preliminary MCP tool call before answering; the probe is limited and related to verifying the configured service.
**Before processing any user query after this skill loads, the following connectivity check MUST be performed.** ... Use `ls_target_fetch` to look up EGFR by name
Be aware of the initial connectivity check and disconnect the MCP service if you do not want automatic PatSnap API calls.