> For the complete documentation index, see [llms.txt](https://developers.oxylabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.oxylabs.io/products/es/web-scraper-api/features/custom-parser/writing-instructions-manually.md).

# Escritura manual de instrucciones

Mira cómo escribir instrucciones de análisis manualmente para manejar casos extremos o personalizar la lógica de análisis.

Si bien Custom Parser te ayuda a automatizar el análisis de datos con funciones impulsadas por IA, también puedes escribir instrucciones de análisis manualmente usando expresiones CSS y XPath. Esto te da la opción de **gestionar casos límite** o **personalizar la lógica de análisis** para escenarios específicos.

Custom Parser requiere estos parámetros obligatorios al crear un trabajo:

* `parse` establecer en `verdadero`
* `parsing_instructions` que contiene un objeto JSON con tus reglas de extracción

Una vez que estés satisfecho con tu lógica de análisis personalizada, puedes guardar las instrucciones como un [preajuste del analizador](/products/es/web-scraper-api/features/custom-parser/parser-presets.md).

Consulta nuestras guías completas a continuación, donde puedes encontrar ejemplos prácticos, buenas prácticas para expresiones XPath y una referencia completa de todas las funciones de análisis disponibles.

{% content-ref url="/pages/6fd3569c2400a7c36b3fda738cd4df91a4fa24ac" %}
[Ejemplos de instrucciones de análisis](/products/es/web-scraper-api/features/custom-parser/writing-instructions-manually/parsing-instruction-examples.md)
{% endcontent-ref %}

{% content-ref url="/pages/3a03dac151c6640f8e582e5735cba3337282067c" %}
[Consejos para escribir expresiones XPath](/products/es/web-scraper-api/features/custom-parser/writing-instructions-manually/tips-for-writing-xpath-expressions.md)
{% endcontent-ref %}

{% content-ref url="/pages/d79a67118b9a83d04625db94c5a04803156f17bd" %}
[Lista de funciones de análisis](/products/es/web-scraper-api/features/custom-parser/writing-instructions-manually/list-of-functions.md)
{% endcontent-ref %}

{% content-ref url="/pages/eb1e80d0a1c7f2ff775e97e19e98b9af8eae4599" %}
[Ejemplos de funciones de análisis](/products/es/web-scraper-api/features/custom-parser/writing-instructions-manually/list-of-functions/function-examples.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.oxylabs.io/products/es/web-scraper-api/features/custom-parser/writing-instructions-manually.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
