Handles the difficult human situations — grievances, complaints, investigations, conflict, and separations conducted properly. Use this to respond to a complaint or grievance, structure an investigation, handle a conflict between colleagues, prepare for a difficult conversation, or work out what a manager can and cannot do in a given situation.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
These situations are consequential for the person, for the organization's legal exposure, and for everyone watching how it is handled. Process is what protects all three.
This structures the approach and tells you what to ask. Grievances, investigations, dismissals, discrimination and accommodation are legally regulated and vary substantially by jurisdiction — involve qualified employment counsel early rather than at the point of decision.
How the first complaint is handled determines whether you hear about the second. An organization that mishandles one complaint does not stop having problems; it stops being told about them, and then learns about them from a regulator or a lawyer.
Acknowledge promptly, explain what will happen next, and say what the person can expect to be told. Do not promise confidentiality you cannot deliver — say who will need to know and why. A broken confidentiality promise destroys the reporting channel permanently.
Protect against retaliation actively. Retaliation is frequently a worse exposure than the original complaint, and it often occurs through ordinary decisions — a changed assignment, an excluded invitation — made by someone who would deny any such intent.
An investigation establishes what happened. It is not a negotiation and not a disciplinary process.
Move quickly. Investigations that drift damage everyone involved and the delay itself becomes a complaint.
Most friction is not a policy matter. Address it directly and early: separate the behavior from the person, establish what each actually needs, and be explicit that the working relationship has to function even where warmth is not available.
Escalating ordinary disagreement into a formal process is its own harm — it takes something resolvable and makes it permanent.
Whatever the reason, conduct them with dignity, on a documented basis, consistently with how others have been treated. Inconsistency is the single most common source of successful claims.
The people who remain draw conclusions from how leavers are treated, and those conclusions are durable.
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.
日本語の概要は準備中です。原文の説明を表示しています。