T09 · Insecure Skill Coding Practices
- Location
SKILL.md:140- Finding
Mandatory Verbatim Rendering of Untrusted Search-Gateway Content
- Content
View full analysis
**CRITICAL:** Never skip the list and jump to a summary. Titles are already Markdown links; users must be able to click through. #### Part B — Analysis [OPTIONAL, after Part A] **Language for your added commentary:** align with the **user’s conversation language** and the **query language** when helpful: - English query → English analysis (typical for EN users). - Non-English query → match the user’s language for the follow-up. - The `message` block is always copied **verbatim**, regardless of language. #### Good pattern ``` API returns a long `message` string with numbered results and snippets. Assistant output: --- Brief synthesis: … (optional, grounded in what appeared above) ``` #### Forbidden - Skipping the result list and answering from memory. - Rebuilding the list from `data.docs` instead of using `message`. - Editing URLs or titles inside `message`. - Claiming sources that are not in `message`. - Stripping Markdown links from titles. ``` ### Technical Analysis The Skill treats the gateway's pre-rendered `message` field as trusted presentation content and explicitly requires the assistant to reproduce it without alteration. Search results originate from public web content and therefore cross an external trust boundary, even though the immediate HTTP endpoint is on localhost. A compromised gateway, poisoned search result, or maliciously constructed indexed page could cause attacke ...[truncated 2119 chars]- Remediation
View remediation
