「mail」の検索結果

Turns a list of merged changes, closed work items or commit messages the user provides into DRAFT release notes under the version heading and date the user supplies, grouped as features, fixes and other, in the organisation's tone from the style guide or prior notes given, with every entry traced to its source item, breaking changes and required actions flagged first, and internal-only items held back for the release owner to confirm. Use when the user asks to "write the release notes for this version", "turn these merged pull requests into a changelog", "summarise what shipped this sprint for customers", "draft the what's new for this release" or "group these closed tickets into release notes". Do not use for an announcement email or intranet post about a launch, use announcement-drafter instead; for a change ticket, use change-request-pack; for a how-to article about one fix, use knowledge-article-drafter. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Reviews one deal's notes and timeline (CRM opportunity record, activity log, emails, meeting notes, forecast entries) for risk signals such as a single contact thread, no identified budget owner, slipped or missing dates, silence after a proposal, an undefined decision process or a competitor named late, and returns a DRAFT risk register: each signal with the quoted evidence and its date, a severity on a stated scale, and one proposed next action with an owner role for the user to decide on. Use when the user asks to "review the risks on this deal", "why is this opportunity stalling", "is this deal single-threaded", "deal health check before the forecast call" or "what should we do next on <opportunity>". Do not use for a whole-account plan, use account-plan-builder instead; for scoring early leads against a rubric use lead-qualification-scorer. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Writes a DRAFT weekly KPI report from the figures the user pastes or attaches (this week, last week, optionally target and earlier weeks): a metrics table with change versus last week computed only from the stated figures, plain-language notes per metric, and numbered questions on every figure that moved more than the agreed threshold, crossed its target or broke its run. Use when the user asks to "write the weekly KPI report", "turn these numbers into this week's metrics report", "what changed versus last week", "draft the Monday numbers update" or "add commentary to this metrics table". Do not use for a recurring emailed report with a maintained trend sheet, use report-attachment-analyzer instead; for actuals versus budget, use budget-variance-explainer. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Maintains four living project files (overview and progress log, decision log, RAID log, links) from the mail, channel posts, documents and meeting notes the user attaches or the agent can reach, returns each touched file complete in the chat for the user to save, and builds a weekly DRAFT status report from those files. Use when the user asks to "set up tracking for project X", "catch the project files up", "log this decision against the project", "add this risk to the RAID log", "save this link to the project" or "write this week's status report". Do not use for reviewing an existing RAID log for stale or ownerless entries, use raid-log-review instead; for an HTML status page, use project-dashboard-builder; for minutes of one meeting, use meeting-minutes-writer. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Drafts one internal or external announcement (email, intranet post, town hall script, customer notice or press statement) in the organisation's voice from the facts, audience, sender and style guide the user provides, with a fact trace, reader-questions check, pre-send checks and an approvals checklist left blank for the named approvers. Use when the user asks to "announce this change to all staff", "draft the customer notice", "write the town hall script", "prepare a holding statement" or "rewrite this in our voice". Do not use for a digest of several items, use internal-newsletter-drafter instead; to pre-test a drafted message against personas, use communication-pretest-panel. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Builds a one-page meeting preparation brief from the calendar invite, recent mail threads with the attendees, chat messages and shared files: purpose, what each attendee likely wants, open threads, key files, talking points and risks. Returns it in the chat as a DRAFT Markdown document capped at 450 words. Use when the user asks to "prep me for my next meeting", "what do I need to know before the vendor call", "one-pager for tomorrow's steering meeting" or "brief me on my 2pm". Do not use for minutes or action items after a meeting, use meeting-minutes-writer or transcript-to-actions instead. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Drafts one anonymised DRAFT case study (situation, approach, outcome as evidenced, optional lessons) from engagement notes, status reports, closing reports, emails and metrics extracts the user supplies, with a fact trace to the notes, an evidence grade on every result, quotes only where the user supplied them with speaker role and permission, an anonymisation log and a confidentiality checklist that must be completed before publication. Use when the user asks to "write a case study from these notes", "turn this engagement into a customer story", "draft a success story for the website", "anonymise this project write-up" or "prepare a reference case for the proposal". Do not use for redacting identifiers from an existing document, use document-deidentification-pass instead; for checking whether a document's claims are substantiated, use claims-evidence-map. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Turns one meeting transcript, recording recap or set of raw notes into concise DRAFT minutes returned in the chat as a single Markdown document: header metadata, attendance and apologies, agenda items each with a short neutral summary and outcome, numbered decisions with an owner, numbered action items with owner and due date, open questions, carried-over actions and the next-meeting line, every entry backed by a short verbatim source fragment and every missing fact marked UNKNOWN. Use when the user asks to "write the minutes", "draft minutes from this transcript", "turn these notes into meeting minutes", "produce the minutes of meeting for today's call", "tidy my rough minutes into the standard format" or "prepare the minutes for circulation". Do not use for extracting action items, task lists or per-owner follow-up emails alone, use transcript-to-actions instead. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Pre-tests one message (email, announcement, intranet post, town hall script, customer notice or slide) against two to six role personas the user supplies and returns a DRAFT panel report: each persona's likely first reaction, objections, unanswered questions, misreadings and what they would do next, every point tied to the passage that triggers it, plus suggested edits that add no fact the message does not already hold. Use when the user asks to "pre-test this message", "how will the team read this", "run this past the personas", "what objections will this raise", "find the holes before I send" or "check this lands with managers and field staff". Do not use for an in-character review of a proposal or business case by one executive archetype, use the executive-review family (cfo-reviewer, frontline-skeptic-reviewer and siblings) instead; to write the message in the first place, use announcement-drafter. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Prepares a DRAFT leadership-meeting briefing pack from the reports, meeting notes, emails and dashboard exports the user provides: one headline, metrics exactly as stated with period and source, decisions the meeting must take, risks as reported, talking points with anticipated questions, a source reference on every line and UNKNOWN where the material is silent. Use when the user asks to "brief the leadership team", "prepare the exec pack", "pull together a briefing for the steering committee", "summarise these reports for the CEO", "what do I tell the board on Monday" or "build the pre-read for the management meeting". Do not use for a formal board or committee paper seeking a resolution, use board-paper-skeleton instead; for a personal one-page prep drawn from the user's own calendar and inbox, use meeting-prep-onepager. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Turns one decision discussion (meeting transcript, chat thread, email chain or notes) into a DRAFT one-page decision memo: the decision as stated, status, options considered, evidence cited, dissent recorded verbatim, owner, effective date and review date, with UNKNOWN for anything the discussion did not settle. Use when the user asks to "write up the decision", "record what we decided", "capture the decision from this thread", "draft the decision memo" or "add this to the decision log". Do not use for full minutes or action items, use transcript-to-actions instead; for a technical design decision, use architecture-decision-record; for a paper seeking a decision not yet taken, use board-paper-skeleton. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Reads one spreadsheet, CSV export or pasted table together with the user's question and drafts an insight pack: a data profile, observations cited to named columns and values and framed as leads, caveats, and suggested charts and follow-up analyses. Every figure carries the label "as read, verify in source"; correlation is never stated as causation. Use when the user asks to "profile this spreadsheet", "what does this data say", "find anomalies in this extract", "give me a first read on this CSV" or "summarise this table". Do not use for a purchase order log or spend extract, use purchase-order-anomaly-review instead; for actuals versus budget, use budget-variance-explainer instead; for a report that arrives by email on a schedule, use report-attachment-analyzer instead. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Builds a role-tuned morning brief as a dated Markdown document covering emails that need replies, today's calendar with conflicts flagged, chat mentions and upcoming deadlines, in the section order set by a preset (project manager, executive assistant, IT admin, sales or custom) read from an editable config. Use when the user asks to "run my brief", "give me my morning brief", "start-of-day summary", "switch my brief to the sales preset" or "change what my brief covers". Do not use for tracking promises made or owed across days, use commitment-catcher instead. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Turns one long support ticket thread (helpdesk history, email chain, chat transcript, call notes) into a one-page DRAFT escalation summary: the customer's ask in their own words, account context as stated, a dated history, what was tried and the stated result of each attempt, the current state, and what is needed from whom by when, every line referenced to a message and every missing fact marked UNKNOWN. Use when the user asks to "escalate this ticket", "summarise this thread for tier two", "write the hand-over for this case", "what has been tried so far", "brief engineering on this customer issue" or "prepare the escalation note". Do not use for a batch of tickets, use ticket-triage-pack instead; for the review after an outage, use incident-postmortem-drafter. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

- Check and interpret data-breach exposure for an email, username, phone or name using Have I Been Pwned, the Pwned Passwords k-anonymity range API, DeHashed, IntelX and Snusbase. Use when checking breach or leak exposure, finding which services an account was registered with, interpreting a combolist or credential dump, assessing credential compromise, or auditing your own leaked personal data

日本語の概要は準備中です。原文の説明を表示しています。

- Entry point for open-source intelligence, investigation and verification work. Use when asked to investigate, research, verify, vet, check out, look up, background-check, trace, attribute or find someone or something; when a request involves due diligence, KYC or KYB, counterparty or vendor risk, sanctions and PEP screening, AML, fraud, business email compromise

日本語の概要は準備中です。原文の説明を表示しています。

- Mine GitHub, GitLab and git history for identities, infrastructure and leaked credentials using commit author emails, GitHub code search, the commit… Use when investigating a developer or organisation on GitHub, finding leaked API keys, AWS keys or tokens in code, enumerating org members and their personal repos, or recovering secrets deleted from HEAD but still present in history or forks

日本語の概要は準備中です。原文の説明を表示しています。

Stop a Google Takeout export from expiring undownloaded: detect the ready-to-download mails with a deterministic zero-token scan, report the live links with days remaining, then drive the download and vault import. Triggers: "/takeout-pull", "is my takeout ready", "pull my takeout".

日本語の概要は準備中です。原文の説明を表示しています。

Gate for any outbound message before it leaves: pull request or issue comment, DM, invite, post, email. Use before sending to check facts, tone, platform rules, registry status and AI-slop, and to block text that fails.

日本語の概要は準備中です。原文の説明を表示しています。

- Investigator OPSEC — threat-model who might notice you, control your attribution surface across IP, ASN, browser and TLS fingerprint, timing and logged-in accounts, separate research identity from… Use when setting up a research account, avoiding tipping off a subject, worrying about LinkedIn profile-view leakage, needing a burner phone or email, or hardening a research VM or browser profile

日本語の概要は準備中です。原文の説明を表示しています。

- Craft advanced search-engine queries and Google dorks to surface hidden files, documents and mentions. Use when building a Google dork, hunting a leaked document, or searching paste sites and document repositories for a name, email or selector

日本語の概要は準備中です。原文の説明を表示しています。

- Find leaked or mentioned selectors circulating in pastes, leak forums, Telegram channels and dump markets, and judge whether a claimed leak is genuine or a recycled combolist. Use when checking whether a name, email, domain or credential is circulating, verifying a breach claim made against your organisation, or setting up ongoing leak monitoring

日本語の概要は準備中です。原文の説明を表示しています。

Write a bold, value-adding follow-up when your own outbound message got silence: check the thread, pick a second channel, add new value instead of a bare bump. Use when an email, DM or PR comment went unanswered. Triggers: /bold-followup, /bump, follow up on silence, second channel.

日本語の概要は準備中です。原文の説明を表示しています。

Rewrite machine-written text so it reads like a busy human wrote it: cut 50-70%, break the even rhythm, drop AI-tell words and filler, keep facts and protected terms. Use before publishing any post, reply or email drafted by a model. Triggers: /ai-slop, /slop, humanize, anti-slop, make it shorter and alive.

日本語の概要は準備中です。原文の説明を表示しています。