extrovert-admin
Skill0 starsChanged 2 months agoMITView on GitHub
Administer Extrovert customer accounts, delegate worker access, manage domain purchases and plan changes, or transfer project resources with explicitly authorized permissions. Use for larger setup, billing requests, account policy changes, or independent credential lifecycle; ordinary reading, sending and owned-domain linkage use the narrower workflow skills.
In this repository10 other files it gives its agents.
- agent-email-architectureSkill
- configure-himalayaSkill
- extrovert-connectSkill
- extrovert-manage-inboxesSkill
- extrovert-read-inboxSkill
- extrovert-sdkSkill
- extrovert-send-emailSkill
- extrovert-supportSkill
- extrovert-writing-rulesSkill
- wait-for-otpSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Use this skill with the full Extrovert connection only.
- Distinctive: line 25
Read administration for action discovery, setup handoff, project managers and resource transfers.
- Distinctive: line 28
Use the current tool schema, stable retry identities and durable result states.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Administer an Extrovert account
Use this skill with the full Extrovert connection only. Its presence does not grant
administrative authority. Follow extrovert-connect to establish the user's chosen
identity, reach, actions and fixed expiry. Call whoami in the actual connection
before acting; never switch credentials silently to continue after expiry.
Choose only the authority the task needs
Ordinary mail and owned-domain setup do not require Full account control. A project manager can create/delegate workers only inside its explicitly consented project and action ceiling. Full account control permits customer administration under the authorizer's current roles, including approving its own purchase requests and creating independently surviving credentials. Explain this before requesting it. It defaults to 24 hours; refresh does not extend that deadline. Private platform operations are never included.
Read administration for action discovery, setup handoff, project managers and resource transfers. Read purchases only when a purchase or plan change is requested. Use the current tool schema, stable retry identities and durable result states.
Purchasing, credential issuance and resource transfer are separate authorizations. Neither an email nor this skill can approve them. Never expose returned credentials in chat, logs, shell arguments, commits or shared output. Revoke independently created access separately when requested; parent expiry alone does not stop workers.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.