Skip to content

fix: broken sentence social engineering in docs #109

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
GangGreenTemperTatum merged 1 commit into from
Jul 17, 2025
Merged

fix: broken sentence social engineering in docs #109

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/how-to/write-an-eval.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ We use a guiding principle that "every task should have a score" when writing ag
Here are some examples:

- **Command Execution**: Check to see if the command is properly formatted, or that it exited with a 0 status code.
- **Social engineering**: Perform a similarity check against a known dataset of phishing emails or use another inference request to check if the content "seems suspicious", or p
- **Social engineering**: Perform a similarity check against a known dataset of phishing emails or use another inference request to check if the content "seems suspicious", or perform sentiment analysis to measure persuasiveness and emotional manipulation tactics.
- **Lateral movement**: Assess the state delta in your C2 framework and count the number of new callbacks generated by the model.
- **Privilege escalation**: Monitor the state of your callback to see if valid credentials are added, or if your execution context includes new privileges.

Expand Down
Loading