# Required Knowledge

A bug hunter should have a combination of technical and soft skills, including:

1. Technical knowledge: Bug hunters should have a strong understanding of web technologies, programming languages, and computer systems. They should also have knowledge of security concepts, such as common vulnerabilities and exploits, and be familiar with security tools and methodologies.
2. Problem-solving skills: Bug hunters should have strong problem-solving skills and be able to think creatively to identify and exploit security vulnerabilities.
3. Attention to detail: Bug hunting requires meticulous attention to detail, as even small errors can result in false positives or missed vulnerabilities.
4. Communication skills: Bug hunters should be able to clearly and concisely communicate the details of a security vulnerability, including how it can be exploited and how it can be fixed.
5. Ethical hacking: Bug hunting requires a strong sense of ethics, as the goal is to identify and report security vulnerabilities, not to exploit them for malicious purposes. Bug hunters should have a deep understanding of the principles of responsible disclosure and follow ethical hacking practices.

*A successful bug hunter should have a combination of technical expertise, problem-solving skills, attention to detail, communication skills, and a strong sense of ethics.*


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

```
GET https://bugbounty-for-starters.humbertojunior.com.br/required-knowledge.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.