T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:32- Finding
Unpinned Remote Documentation Can Supply Executable Invocation Code
- Content
View full analysis
`Chai-1_api_doc.md` - `Boltz-2` -> `Boltz-2_api_doc.md` - `AlphaFold3` -> `AlphaFold3_api_doc.md` - If the user explicitly requests a covalent-ligand workflow, use the corresponding `Chai-1-Covalent_api_doc.md`, `Boltz-2-Covalent_api_doc.md`, or `AlphaFold3-Covalent_api_doc.md`. The agent MUST: 1. Resolve the selected 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 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 4. Choose the correct section if the selected doc contains multiple tool variants, such as standard vs covalent workflows or inline inputs vs file uploads. 5. Cite the selected Markdown doc as the payload source in summaries. [...] 2. Read the corresponding Markdown file from `https://sciminer.tech/tool_api_files/`. 3. If the request includes covalent chemistry, switch to the corresponding covalent Markdown doc. 4. Choose the doc section that matches the user's input shape. 5. Collect any missing required parameters from the user. 6. Upload required file inputs exactly as described by the selected Markdown do ...[truncated 3424 chars]- Remediation
View remediation
