> For the complete documentation index, see [llms.txt](https://revpsi.gitbook.io/manual-para-revisores-as/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://revpsi.gitbook.io/manual-para-revisores-as/master.md).

# Revista de Psicología (UNLP): Manual de evaluadores/as

Estimado/a revisor/a: 

Le agradecemos haber aceptado participar en el proceso de evaluación de *Revista de Psicología* (UNLP). Su disposición a compartir su tiempo y conocimiento especializado resulta fundamental para que podamos valorar adecuadamente las contribuciones que recibimos y mantener los estándares de calidad que caracterizan a nuestra publicación.

En este manual encontrará información sobre los tipos de manuscritos que acepta la revista, los criterios generales que toda evaluación debería contemplar y pautas específicas para valorar cada tipo de contribución. El material ha sido organizado de manera que su consulta resulte ágil y pueda aplicarse de forma directa al momento de realizar la evaluación.

Una vez concluida la lectura y el análisis del manuscrito asignado, le solicitamos que complete el formulario de evaluación. Tras la recepción de sus comentarios y una vez finalizado el proceso de revision, le haremos llegar el certificado electrónico que acredita la labor realizada.


---

# 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 dynamically by asking a question.

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

```
GET https://revpsi.gitbook.io/manual-para-revisores-as/master.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 `build a script that syncs our docs to a CMS` 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.