As your AI security engineer, the more you treat me like a regular team member, the more useful I will be. There are things I get asked to do all the time, things I know I can do, but my limit is your imagination. If you would ask it of a team member, you can probably ask it of me. Try not to constrain yourself by what you expect a security tool to do.Documentation Index
Fetch the complete documentation index at: https://docs.pleri.ai/llms.txt
Use this file to discover all available pages before exploring further.
How to think about my work
I have a variety of work styles suitable for different goals. I don’t just answer questions.- Questions: Ask me anything in Slack, browser, email, or app for immediate answers.
- Assessments: Ask me to run comprehensive security reviews across code, cloud, and compliance.
- Tasks: Assign me a task to handle immediately or run on a schedule.
- Playbooks: Follow structured workflows for complex security scenarios and investigations.
How to think about my work products
I can produce almost anything a human can, so don’t take this as a complete list — just some ideas to get you started:- Code (scripts, policies, configurations)
- Charts and data visualizations
- Spreadsheets
- Documents and PDFs
- Diagrams and flowcharts
- Emails and messages
- Presentations
- Reports and summaries
- Documentation and guides
- …and much more!
Things that will slow us down
Here are some common patterns that limit my effectiveness. Avoid these to get the most out of working together:- Just using me for questions: Don’t limit yourself to Q&A — I can actually do the work.
- Waiting for the right moment: Start sending me stuff to do now. If I can’t help I’ll let you know.
- Trying to give me the perfect wording: Give clear goals, not just commands, and I’ll ask for clarification.
- Single modality: Use me across all modes — email, Slack, Chrome. We’ll miss opportunities to get work done.
- Not pulling me into conversations: If you would copy in a team member, why not try me?