> For the complete documentation index, see [llms.txt](https://reports.robin-sim.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://reports.robin-sim.fr/introduction.md).

# Introduction

About me

Welcome to my GitBook I'm R0b1.\
This space gathers my technical reports, write-ups, and personal projects related to cybersecurity and software engineering. It serves both as a portfolio of my work and as a record of my continuous learning journey.

I am a **computer engineering student specializing in cybersecurity**, with the goal of becoming a **penetration tester**.\
Through the projects and write-ups shared here, I aim to demonstrate not only my technical skills but also my analytical mindset, problem-solving abilities, and curiosity for exploring complex systems.

This GitBook includes:

* **CTF and lab write-ups**, detailing my methodology and thought process,
* **technical reports** from academic and personal projects,
* and **notes or research** on tools, vulnerabilities, and security techniques I find interesting.

This is a living document — it will continue to evolve as I learn, experiment, and grow as a cybersecurity professional.

Here is some links to my different profiles  :

{% embed url="<https://tryhackme.com/p/R0b1>" %}


---

# 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://reports.robin-sim.fr/introduction.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.