「triage」の検索結果

Triage the LinkedIn inbox - sort connection requests and DMs into leads, recruiters, peers and spam, and draft the replies worth sending. Use when the user says "my inbox is a mess", "triage my DMs", "should I reply to this", pastes a batch of LinkedIn messages, or is drowning in connection requests.

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

Triage inbound journalist source queries and draft a response only when the user's expertise is a real fit. Runs each query through proven source-request lenses (4-gate fit triage, credential-standing test, deadline read, BLUF/inverted-pyramid drafting), kills weak fits, asks for missing proof, and never auto-sends.

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

Audit a content library, docs site, or blog for AI-generated filler that's eroding trust and search performance — and triage what to fix, rewrite, or delete. Use when asked to find slop in a content library, audit AI-written content quality, explain why content engagement or rankings dropped after scaling with AI, or set a quality bar for AI-assisted publishing. Produces an audited inventory with per-piece verdicts, the detection signals used, a triage plan, and a publishing quality gate that prevents recurrence. For a single article's AI-citability use aeo-optimizer; for the strategy itself use content-calendar or seo-content-brief.

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

Triages all inbound leads from a given period — demo requests, free trial signups, content downloads, webinar registrations, chatbot conversations. Classifies by urgency, qualifies against ICP, enriches with context, and produces a prioritized action queue with recommended response for each lead. Tool-agnostic — works with any CRM, form tool, or lead source.

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

Use when the user wants to triage a CORPUS of production crashes/hangs from an aggregator (Sentry, App Store Connect) — grouped, counted issues — rather than a single crash file.

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

Triage TestFlight crashes, beta feedback, and performance diagnostics using asc. Use when the user asks about TF crashes, TestFlight crash reports, beta tester feedback, app hangs, disk writes, launch diagnostics, or wants a crash summary for a build or app.

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

End-to-end GitHub repository maintenance for open-source projects. Use when asked to triage issues, review PRs, analyze contributor activity, generate maintenance reports, or maintain a repository. Triggers include "triage", "maintain", "review PRs", "analyze issues", "repo maintenance", "what needs attention", "open source maintenance", or any request to understand and act on GitHub issues/PRs. Supports human-in-the-loop workflows with persistent memory across sessions.

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

Triage technical SEO findings from Ahrefs Site Audit (and similar crawlers) by SEO impact, not just severity. Use this skill when reviewing crawl results, prioritizing technical fixes, scoping a technical SEO sprint, or after running any site-wide crawl. Triggers on site audit results, technical fix list, crawl errors, technical SEO triage, prioritize technical issues, what should we fix first, broken links, redirect chains. Also triggers when a long list of crawler issues is creating decision paralysis.

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

Triage and categorize new GitHub issues on watched repos

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

Linear expert for workspace/team admin, Cycles, Projects, Initiatives, Roadmaps, GraphQL API queries, triage workflows, GitHub integration, bulk operations, and Jira-to-Linear migration.

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

Build a trusted capture-and-triage front door so no commitment lives in your head. Use when open loops keep slipping, an inbox has become a backlog, or vague notes never turn into action.

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

Rapid NDA screening with GREEN/YELLOW/RED classification. 10-point checklist for incoming NDAs. Use when triaging NDAs, screening non-disclosure agreements, or routing NDAs for approval.

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

Swiss legal source and authority triage. Use when a user asks a Swiss legal, regulatory, compliance, contract, employment, corporate, litigation, IP, tax, privacy, public-law, fintech, register, or cantonal-law question; when Swiss law may apply; or when an AI legal answer needs source routing across federal, cantonal, communal, regulator, register, contractual, professional, soft-law, multilingual, or open-data layers.

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

First-touch triage for external pull requests - verdict, label, and a welcoming comment within minutes of open

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

Daily GitHub notification inbox triage - surfaces aging vuln PR replies, security advisories, review requests, and mentions that need action

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

Classify and advance issues or external pull requests through the configured triage workflow. Use explicitly to inspect queues, evaluate an item, recommend a state, or apply an authorized transition.

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

NIST SP 800-61r3-aligned incident triage that preserves evidence, separates analysis from authorization, and records status. Use for incident intake, severity assessment, containment readiness, or evidence preservation; not generic debugging or unscoped response.

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

Triage review findings interactively — approve, skip, or prioritize each issue. Use after /phx-review to filter findings before fixing.

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

Triage review findings interactively — approve, skip, or prioritize each issue. Use after phx-review to filter findings before fixing.

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

Triage review findings interactively — approve, skip, or prioritize; Use after $elixir-phoenix:phx-review to filter…

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

Triage review findings interactively — approve, skip, or prioritize each issue. Use after /phx:review to filter findings before fixing.

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

Environment Triage

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

Interpret medical lab/test reports (blood panels, urine, liver/kidney function, thyroid, tumor markers, coagulation, cardiac enzymes, hormones, etc.) uploaded as images, PDFs, or text. Trigger whenever the user uploads a lab report, medical test result, or clinical diagnostic sheet — or says things like "help me read this report", "what do these results mean", "化验单", "检验报告", "帮我看看这个报告", "blood test results", "lab results", "体检报告", "检查报告单", "血常规", "尿常规", "肝功能", "肾功能", "甲功", "凝血", "interpret my labs", "are these results normal", "这些指标正常吗". Also trigger when the user uploads ANY medical-looking document with tables of values, reference ranges, or clinical test names — even if they don't explicitly ask for interpretation. Do NOT trigger for symptom triage (use emergency-triage instead), drug interaction queries, or general medical Q&A without an actual report to interpret.

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

SOC alert triage, incident playbook automation, escalation workflows, shift reporting, and SOC KPI tracking

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