Results for “abuse-reporting”

Use when reporting progress, status updates, or completion of work to managers, stakeholders, or dependent agents. This skill defines a standard format for clear, consistent, and actionable status updates.

Use to review how call recordings are notified, stored, accessed, redacted and deleted, including the parts that differ from text conversations. Trigger for "review our call recording practices", "do we need to tell customers we're recording", "who can listen to our calls", recording retention, card details spoken on a call, or a request for a customer's own recording.

Detect abuse of service accounts through anomalous interactive logons, privilege escalation, lateral movement, and unauthorized access patterns.

Write donor appeal letters with stories and impact. TRIGGERS - Use when user needs help with donor-appeal related tasks.

Write donor appeal letters with stories and impact. TRIGGERS - Use when user needs help with donor-appeal related tasks.

Write cease and desist letters with legal basis. TRIGGERS - Use when user needs help with cease-desist related tasks.

Reporting Templates

Applies the same change across multiple repositories in parallel using git worktrees, tests, and pull requests.

Use to clean up sprawling helpdesk tags, categories and custom fields so reporting built on them means something. Trigger for "our tags are a mess", "consolidate our ticket categories", "why don't our tag reports add up", duplicate or near-duplicate tags, tags nobody uses, agents tagging inconsistently, or before building reporting on top of tags.

Use when adapting academic findings for a public audience (op-ed, social post, podcast) and the simplification must stay evidence-faithful, avoid overclaiming, respect embargoes, and disclose AI assistance.