TracecatHQ

Prose rules for case comments, incident summaries, Slack briefs and any analyst facing text, built on ASD-STE100 Simplified Technical English. Covers sentence construction, word choice, and the evidential qualifiers a security case must keep. Attach to any…

Load when the prompt's first line is `OAuth app lifecycle <primary_user>|<client_id>`, followed by one app's grant data as JSON. Takes one Google Workspace OAuth app from the audit log to a triaged Tracecat case and a published Slack card. You read the saved…

Load when the prompt's first line is `OAuth grant review <grant_key>`, and whenever a lifecycle skill or a request asks you to judge one Google Workspace OAuth app grant. Assess how much access that grant gives one person, and produce the severity, the…

The reporting structure of your organisation. Use it to find the manager who must approve a person's access before you write an access-review message.

Load before researching the company behind a third-party application, whether it reached you as an OAuth grant, a SaaS onboarding request, an alert about third-party app access, or a question in chat. Answers six fixed questions a reviewer needs in order to…

Provides verified corrections for IAM behaviors that AI agents frequently get wrong — policy evaluation edge cases, trust policy gotchas, STS session limits, Organizations quirks, and SAML/MFA specifics. Also provides structured workflows for IAM role…

Investigate AWS credential compromise, STS session abuse, and API breaches; produce an evidence-backed timeline, containment plan, and incident handoff.

Turns a threat report, a malware analysis, vendor tool documentation, or a raw log sample into draft Sigma detection rules, validated against sigma-cli where a shell exists and labelled "not machine-validated" where not, each paired with a validation note…

Use after exploitability is demonstrated to prepare and persist a narrow supplier intake ingress policy, its compatibility analysis, rollback conditions, and the human decision required to apply it.

Use when a vulnerability finding needs fresh evidence of impact at the exposed supplier intake ingress, or when a completed control needs an attack and benign-traffic retest.

Use when a case involves API Gateway abuse, API key exposure, API authentication or authorizer weakness, WAF/API alerts, abnormal API invocation volume, scraping, injection through API endpoints, BOLA/IDOR, or API-layer data exfiltration.

Use when a case involves compromised AWS credentials, leaked or exposed IAM access keys, suspicious STS use, unauthorized IAM activity, GuardDuty IAM findings, unusual AWS API calls, or attacker persistence through IAM users, roles, policies, or access keys.

Use when a case involves unintended S3 access, public bucket or object exposure, permissive bucket policy or ACL changes, S3 GuardDuty/Macie findings, bulk object access, or data exposure through compromised credentials.

Use when the task is to create a new incident-response skill or playbook from scratch rather than triage a BOTSv3 case — no existing source playbook, and the user wants a structured interview or quick-mode draft for a new incident type.

Use when converting an existing human-readable incident-response playbook into an AI-usable skill — playbook authoring and transformation work, not direct BOTSv3 case closure.

Use when a case involves ransomware indicators, ransom notes, encrypted files or objects, volume or object lockout, destructive encryption behavior, mass deletion, extortion, or compromise paths that could lead to ransomware impact.

Use when building, editing, validating, or debugging generic Tracecat automations through Tracecat MCP, including workflow DSL/YAML authoring, table design, unique indexes, run-python Tracecat imports, agent presets, ai.agent or ai.preset_agent workflows,…

Use when an external agent needs to connect to or operate Tracecat through MCP, including workspace discovery, workflows, actions, cases, tables, integrations, agent presets, skills, executions, or safe platform navigation.

Use when creating, uploading, updating, publishing, or re-binding a local Agent Skill directory through Tracecat MCP, including pushing a fix to a skill an agent preset already uses.

Use when building, editing, validating, or debugging Tracecat Slack bots and Slack-facing automations through Tracecat MCP, including Slack app mentions, interactive messages, event subscriptions, webhooks, thread replies, Slack tools, ai.agent or…

Use whenever Tracecat Workspace Chat answers platform questions or operates workflows, cases, tables, agent presets, integrations, secrets, variables, or other workspace features. Adapts generic Tracecat MCP guidance to the tools actually exposed in Workspace…