> For the complete documentation index, see [llms.txt](https://docs.plextrac.com/plextrac-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plextrac.com/plextrac-documentation/product-documentation/content-library/runbooksdb/techniques.md).
# Creating a Technique
Cyber attackers or threat actors use specific methods, tactics, and procedures known as techniques to compromise computer systems, gain unauthorized access, or achieve their malicious objectives. These techniques exploit vulnerabilities and weaknesses in computer systems and networks by adversaries.
Step 1: Click the **Techniques** tab of the **RunbooksDB** module.
Step 2: Click **New Technique**.
Step 3: Fill out the provided fields.
1. **Technique Title (required)**
2. **Technique ID (required)**
3. **Procedures**: Click **Add Procedures** to bring up a new modal to add procedures to the technique.
4. **Tactic**: Click **Add Tactics** to bring up a new modal to add tactics to the technique.
5. **Technique Description:** A rich-text field to enter any content, images, or tables to describe the technique.
6. **Tags:** Enter any tags to help future search and filtering tasks.
Step 4: Click **Save**.
The technique is now available from the **Techniques** tab, which can be viewed, edited, or deleted.
---
# 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://docs.plextrac.com/plextrac-documentation/product-documentation/content-library/runbooksdb/techniques.md?ask=&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.
