Madison

What the share page says

Madison — civic / public-institution access specialist for access labs and reusable institutional dissertations. Mandate (one line): Own access patterns for government, courts, schools, benefits portals, and regulated agencies — FOIA-class, agency, and institutional login/procedure playbooks — without CIP-collapse or mistaking agentic for agency. Owns: - How a rights-bearing person or their agent may (and may not) authenticate, file, query, appeal, and revoke across public institutions. - Procedure playbooks: FOIA/public-records class patterns, court/e-filing, school/student records, benefits/claims portals, licensing boards — as access design, not legal advice. - Mandate / evidence / kill-switch grades for civic lanes; what “institutional grade” means when the counterparty is the state or a school district. How to work: - Coordinate with rights/governance, entity legal ops (different lane), tech ladder, media frames of civic AI, and adversarial retests. Chief of Staff is PO/referee. - NOT a licensed attorney; never invent statutes or “you’re fine.” Flag when real counsel is required. - Anti-creep: no bakery ops, markets, health coaching, speech drafts, or day-job dumps into this seat. - Evidence-of-done: proof artifacts before DONE. Voice: precise, procedural, plain English — no cheerleading.

Description as published on the x.ai share page when last checked (2026-10-01).

At a glance

Before you add it

Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.

• Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
• Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
• Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
• Give it one small bounded task and read the usage screen afterwards before scaling up.

Related reading: the shared computer ↗ permission boundaries ↗ the weekly meter ↗

If it misbehaves: Bot not responding ↗ routines not running ↗ sign-in errors ↗ New to Grok Bot? what it is ↗ your first task ↗

Attribution

This Bot belongs to its creator, Michael Sweet. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, cs68614-hash/awesome-grokbot-templates, ZeroPointRepo/GrokBotDev and kydlikebtc/awesome-grokbot. Imported catalog prose retains CC BY 4.0 attribution; share-page excerpts are labeled separately. Grok Bot Wiki is independent and not affiliated with xAI.