|
              /idasql skills (LLM translates intent to SQL)
                    |
                 IDASQL  -->  IDA database(s)
                    |
                 Results  -->  LLM summarizes & reasons

" with nothing in between. Could be a whitespace? The original prompt shows:

Maybe the input chunk is an empty string? Or there is a blank line before " response". Looking at the prompt: The last line "INPUT:" and then the next line is " response". Actually the user wrote "INPUT:" then a newline, then " response". That might mean the chunk content is simply nothing, i.e., a blank line. However, typical chunking of a Markdown document might include a single newline as a separator. The instructions say: "If the chunk starts mid-paragraph, continue translating from that point. Do not add a leading newline or indent unless it exists in the source." So if the input is empty, we output nothing? But I need to see if there's any actual content. The user's final line: " response" might be part of the assistant's response template? No, that's likely a placeholder. The actual chunk content appears to be nothing. The instruction: "Return ONLY the translated text." So if the chunk is blank, I should return blank. However, the prompt might be truncated. Let's examine the original user message: 

So after "INPUT:" there is a blank line, then the word " response". I suspect that " response" was accidentally typed by the user, maybe as a placeholder or a glitch. The actual chunk might be the blank line before " response". The user might have intended to provide the chunk content, but mistakenly left the word " response" there. However, as an AI, I must follow the instruction: "Translate the following Kitploit tool content." The input is given after "INPUT:". So the input is the blank line? The blank line may be the chunk. In Markdown, an empty line might be needed to preserve structure. Since there's nothing to translate, I'll output nothing. But then there's " response" next to it. That could be the AI's cue, but the instruction says "Return ONLY the translated text. No preamble, no commentary." So I'll output an empty string. However, I need to be careful: The user said "This is chunk 3 of 53" and "Content type: README chunk 3/53." So it's plausible that chunk 3 is an empty line. If the document had a blank line between sections, that would be a chunk. So I'll treat the input as empty. So response should be empty. But the instruction "DO NOT add introductory headings like '## Chunk N' ... DO NOT add 'End of chunk N' ... DO NOT add '...' ellipsis markers." So if I output nothing, that's fine. However, I should ensure I'm not missing any hidden characters. The prompt ends with "INPUT:\n\n response" - there's a newline after INPUT:, then another newline, then " response". So the "INPUT:" line is followed by two newlines, then the word " response" on its own line. That's ambiguous. Probably the chunk content is the blank line before " response"? Or the " response" is part of the chunk? If " response" is part of the chunk, it would be a word to translate. But translating "response" to Spanish would be "respuesta", but that might not be appropriate for a README. Given the context, "response" likely is not part of the README content, but an accidental prefix. I'll interpret that the actual input chunk is empty (just a newline), and the " response" is a stray. Therefore, I'll output nothing. The safest: treat the input as blank, output blank. If that's wrong, the next chunk might clarify. Since we need to follow rules: "Translate ONLY the exact text provided". The exact text provided is "" (an empty string) because the word " response" might be appended by mistake. To be precise, the string after "INPUT:" and before the end of the message is "\n\n response". But the " response" is on a new line and could be part of the chunk. Could be the user typed "INPUT:" and then next line " response" meaning "Here is the response" but that's meta. The instructions forbid meta-text. I'll consider the content to be only the first line after "INPUT:" which is blank. So translated: nothing. I'll return an empty string.```
$ idasql -s WerFaultTool.exe.i64 -q "SELECT * FROM funcs LIMIT 5"
Opening: WerFaultTool.exe.i64...
Database opened successfully.

+------+-------------------------------------------------+------+----------+-------+
| addr | name                                            | size | end_addr | flags |
+------+-------------------------------------------------+------+----------+-------+
| 16   | WerFaultTool.AboutForm::.ctor                   | 13   | 29       | 4096  |
| 32   | WerFaultTool.AboutForm::Dispose                 | 30   | 62       | 4096  |
| 64   | WerFaultTool.AboutForm::InitializeComponent     | 295  | 359      | 4096  |
| 400  | WerFaultTool.WerFaultGUI::.ctor                 | 936  | 1336     | 4096  |
| 1344 | WerFaultTool.WerFaultGUI::CreateDynamicControls | 231  | 1575     | 4096  |
+------+-------------------------------------------------+------+----------+-------+
5 row(s)

El agente inicia IDASQL sin interfaz gráfica en segundo plano. A partir de este punto, chatea de forma natural con la base de datos. Por ejemplo:```
/idasql:annotations Fully annotate the function I'm looking at, also use the decompiler skill.

### Trabajando con Múltiples Bases de Datos

Puedes trabajar con dos o más bases de datos simultáneamente. Indica a tu agente:```
/idasql:connect In this folder, there are many *.exe files. Please use parallel agents to open IDASQL in the background and report how many functions each has.

El agente trabaja con todas las bases de datos al mismo tiempo. Puedes hacer referencias cruzadas, comparar y transferir anotaciones entre ellas.

### Trabajar con la interfaz de IDA

Todo lo anterior funciona igualmente desde la GUI de IDA. Para conectar tu agente con una sesión de IDA abierta:

1. En el prompt `idasql>` de IDA, escribe:   ```
   .http start

luego instala el plugin `idasql` desde ese marketplace. Consulta el [README de idasql-skills](https://github.com/allthingsida/idasql-skills#installation) para Codex y otras rutas de instalación.

#### Skills

| Skill | Description |
|-------|-------------|
| `connect` | Conéctate a bases de datos de IDA: CLI, servidor HTTP, arranque de sesión, enrutamiento de skills, contratos globales. |
| `disassembly` | Consulta el desensamblado de IDA: funciones, segmentos, instrucciones, bloques, operandos, gráficos. |
| `data` | Consulta cadenas, bytes y datos binarios de IDA: búsqueda, reconstrucción, patrones de bytes. |
| `xrefs` | Analiza referencias cruzadas de IDA: llamadores, llamados, importaciones, referencias de datos, búsqueda grep. |
| `decompiler` | Descompila funciones de IDA: pseudocódigo, árbol AST ctree, variables locales, etiquetas. |
| `annotations` | Edita bases de datos de IDA: comentarios, renombrados, tipos, marcadores, renderizado de enum/struct. |
| `types` | Sistema de tipos de IDA: crear/modificar/aplicar structs, uniones, enums, typedefs, parse_decls. |
| `debugger` | Depurador de IDA: puntos de interrupción, parcheo de bytes, condiciones, inventario de parches. |
| `storage` | Almacenamiento clave-valor persistente en bases de datos de IDA mediante netnode_kv. |
| `idapython` | Ejecuta IDAPython vía idasql: fragmentos, sandbox, captura de salida. |
| `functions` | Catálogo completo de referencia de funciones SQL de idasql. |
| `analysis` | Analiza binarios de IDA: triaje, auditoría de seguridad, detección de crypto/red, consultas multi-tabla. |
| `resource` | Recupera binarios de IDA: anotación recursiva, recuperación de estructuras, reconstrucción de tipos. |
| `ui-context` | Captura el contexto de la interfaz de usuario de IDA en vivo: pantalla, selección, foco de widget, anclas de dirección. |

#### Ejemplos de Prompts```
/idasql:analysis analyze this binary; tell me the most called functions.
/idasql:data find functions that reference "password" strings and rank by xrefs.
/idasql:xrefs show callers of CreateFileW and summarize error handling.
/idasql:data identify suspicious hardcoded URLs and the functions that reference them.