Administers the email, chat, meeting and file-sharing platform the organization runs on — tenant and domain configuration, mail authentication and routing, phishing and spam controls, shared mailboxes and distribution groups, external sharing and guest access, permission sprawl in file storage, and retention and legal hold. Use this to configure a tenant, tighten sharing, investigate a mail delivery or phishing problem, or work out who can see a file and why.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
This platform holds most of the organization's unstructured information and nearly all of its external communication. It is usually configured once during migration, by whoever ran the migration, and then never revisited.
SPF, DKIM and DMARC together determine whether your mail is delivered and whether someone else can send as you. All three need to exist and agree.
Every new tool that sends mail on your behalf is a change to this configuration. Route that through the same process as any other change, or the first sign will be a customer saying your invoices go to spam.
External sender warnings, impersonation and lookalike-domain protection, attachment and link inspection, and blocking auto-forwarding to external addresses are settings. Auto-forward rules in particular are the classic account-compromise persistence mechanism, and the account owner will not notice.
Alert on inbox rule creation that forwards or deletes. It is one of the highest-signal detections available and it comes free with the platform.
Shared mailboxes, distribution lists and team channels accumulate faster than anything else in the tenant and are never cleaned up. Each needs a named owner and a review date, because a distribution list nobody owns eventually mails the whole company by accident, and a shared mailbox with stale access is a standing data exposure.
Never leave a shared mailbox with a sign-in-capable account. It is an unmonitored identity with a password.
The defaults are usually more permissive than the organization would choose, and the settings sit at several levels — tenant, site, folder, individual link — with the most permissive winning.
Run a sharing report on a schedule. Nobody discovers over-sharing by browsing.
Retention policies decide what survives deletion and for how long, and they have to be set before the data you will need is deleted. Legal hold suspends deletion for named custodians and must be capable of being applied quickly.
The platform's own recycle bins are not a retention policy and not a backup — the retention windows are short and administrator deletion can bypass them.
references/sources.md in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.