T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:87- Finding
Mutable Remote Documentation Is Used to Generate and Run Invocation Code
- Content
View full analysis
`PBCNet 2.0_api_doc.md` - `Gnina` -> `Gnina_api_doc.md` The agent MUST: 1. Resolve the selected SciMiner tool's Markdown file and read it before every invocation. 2. Never invent `provider_name`, `tool_name`, parameter names, enum values, upload-field names, content type, or submission flow from memory. 3. Extract and follow the selected SciMiner doc section's exact: - Base URL - API endpoint - Content-Type - Authentication header - Tool Name - Method - Parameter table, including required fields and enum values - File-upload instructions and example code ``` ```markdown 13. Write or run invocation code directly from the selected Markdown docs' base-information block, parameter table, file-upload instructions, and example code. Do not apply a shared invocation template or local registry abstraction in this skill. ``` ```markdown - Use the selected SciMiner Markdown docs under `https://sciminer.tech/tool_api_files/` as the authoritative source for payload construction and invoke-method details. - Read the SciMiner API key from `~/.config/sciminer/credentials.json` and send it as the `X-Auth-Token` header. ``` ### Technical Analysis The Skill makes mutable Markdown hosted on an external server the authoritative source for request endpoints, authentication behavior, upload procedures, and example code. It then explicitly instructs the Agent to ...[truncated 2458 chars]- Remediation
View remediation
