977 件 ・ 関連度順
概要と使いどころ
Analyze inbox emails to identify action-required items, prioritize by urgency/importance, classify by topic, and draft contextual replies. Use when triaging unread emails, prioritizing inbox, generating response drafts, or tracking email response status.
日本語の概要は準備中です。原文の説明を表示しています。
Show what this repository has already decided about its vulnerabilities, read from the durable record rather than by scanning again — open versus resolved, the decision taken on each, and what is still waiting. Use when picking up triage after a break, auditing past decisions, onboarding to a repository with security history, or checking nothing high-severity is open before a release.
日本語の概要は準備中です。原文の説明を表示しています。
Concrete remediation proposal with Safe Harbour confidence — version bump, inline as first-party code, patch, workaround, or advisory. Use when applying a fix for a triaged CVE, evaluating fix-type trade-offs across registry / source / distro patches, producing rollback-safe manifest edits with dry-run verification, or generating a CycloneDX SBOM after the fix lands.
日本語の概要は準備中です。原文の説明を表示しています。
Audit a dataset or access rule before it joins an identity-graph build (access rules behave like datasets in NQL here). Enumerates failure modes (hub identifiers, high-degree nodes, suspicious values, over-connected identifiers), tests hypotheses in parallel, quantifies damage by rows / edges / entities, and proposes minimal filters ranked by severity. When issues are found, returns a validated `CREATE MATERIALIZED VIEW` NQL the caller can run to produce a graph-ready clean source; if the data passes, says so and recommends it unchanged. Plans and authors the clean-view NQL; does not execute it. Use when: "audit this dataset before the graph build", "find bad edges in <source>", "check identity data quality", "recommend filters for the graph build", "quantify damage from <identifier_type>", "pre-graph DQ". (narrative-identity)
日本語の概要は準備中です。原文の説明を表示しています。
Lightweight triage for the ln-* skill set. Use when unsure which ln skill to use next, starting work on something new, or when the user asks for guidance on their development process.
日本語の概要は準備中です。原文の説明を表示しています。
Compares one clause (liability, termination, confidentiality or any other) across several contracts, templates or successive versions and returns a DRAFT comparison table: verbatim clause text per document, the clause split into elements with every difference from the baseline highlighted and categorised, and neutral questions for counsel. Never says which wording is better or enforceable. Use when the user asks to "compare the liability caps across these five supplier contracts", "line up the termination clause in these three drafts", "show how the confidentiality clause changed between versions", "contrast this clause with our template" or "benchmark the indemnity wording across our customer agreements". Do not use for a whole-contract review, use contract-review-pack instead; for screening one NDA against standard positions, use nda-triage. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews one employee software request (tool, purpose, users, data handled, cost, urgency) against the approved-tools list and the policies the user provides and returns a draft review for the reviewer: match state on the list with the row quoted, approved tools the list itself describes as covering the same need, policy clauses that bear on the request with quoted text, questions for the requester and the reviewer, and one suggested decision with its basis. Never approves, procures, installs or adds a tool to the list. Use when the user asks to "review this software request", "is this tool on the approved list", "check this request against our software policy", "do we already have something approved that does this" or "prepare the decision note for this tool request". Do not use for a full vendor security assessment, use vendor-risk-screening-brief instead; for sorting mixed requests, use request-intake-triage. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Abstracts one contract into a key-terms table with clause references, compares each term against the user's playbook of standard positions, and returns a DRAFT contract review pack: deviations and issues, open questions and a reviewer checklist. Flags governing law and never gives legal advice or enforceability or acceptability calls. Use when the user asks to "review this contract", "abstract the key terms", "summarise this MSA", "pressure-test this SOW against our playbook" or to compare an agreement with their standard positions. Do not use for a first pass on a stand-alone NDA, use nda-triage instead, or for one clause lined up across several documents, use clause-comparison-table 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.
日本語の概要は準備中です。原文の説明を表示しています。
Synthesises a batch of customer feedback (survey answers, reviews, ticket and chat comments) into a DRAFT themed report: coded themes with record counts and shares, anonymised verbatim quotes cited to record codes, contradictions and unverified claims, and the follow-up questions to answer next. Produces no sentiment score or percentage positive as fact; ratings appear only as distributions with n. Use when the user asks to "theme this feedback", "what are customers saying", "summarise these survey answers", "analyse these reviews", "find the top complaints in these comments" or "code this voice of the customer data". Do not use for exit interviews, use exit-interview-synthesis instead; for sorting a live queue and drafting replies, use ticket-triage-pack; for project retrospectives, use lessons-learned-synthesis. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Operate Jira Cloud via its REST v3 API — issues, projects, sprints, boards, comments, transitions, JQL search. Use when the user wants to triage, bulk-update, report on, or otherwise interact with Jira programmatically without the MCP server installed.
日本語の概要は準備中です。原文の説明を表示しています。
Work leads in Telegram: find prospects by topic, keep only those who self-mentioned it, resolve their handle including through shared groups, pitch personalized and grounded in real templates, run a two-step scheduling close, triage follow-ups, and capture everyone in the CRM. Triggers: "find leads for <topic>", "pitch this prospect", "run outreach".
日本語の概要は準備中です。原文の説明を表示しています。
Triage a lead pipeline and say who needs action today: replied means send the scheduling link, link sent 24h ago without a booking means nudge, awaiting reply means check inbound, going cold means follow up, booked means close out. Ranked and draft-first, so the owner edits before anything goes out. Triggers: "/pipeline", "work my leads", "who is stuck in the funnel".
日本語の概要は準備中です。原文の説明を表示しています。
Найти человека и его каналы связи по нашим ЖЕ данным: архив ТГ 16.7 млн сообщений, CRM, книга чатов, почта, досье. Триггеры: /find-person, найди хэндл, как с ним связаться, найди контакт, где он есть, кто это, найди телеграм <имя>, найди человека. НЕ путать: /find = поиск по волту; /triage = кого касаться; этот = где у человека дверь и что мы о нём уже знаем.
日本語の概要は準備中です。原文の説明を表示しています。
Watch incoming feedback from outside engineers on your open-source repos: comments, reviews, issues, mentions. Use when you need to find who replied to your pull requests or issues, triage human versus bot responses, and answer within a day with evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Operational guide for WordPress.org submission readiness of NV oOS standalone plugins (nvoos-docs-hub live at 0.5.3; nvoos-content-graph live at 1.0.10 in the re-submission loop; nvoos-design-system next in the pipeline — issue #6811). Covers the 18 wp.org guidelines, the Plugin Check (PCP) gate in CI and Docker, PCP finding triage, the reviewer-reply loop (findings taxonomy from the real 0.4.3 review, related-issue sweep checklist, reply-email template), packaging exclusion tri-sync, readme.txt standards, .wordpress-org listing assets, and the NV oOS Complete checkout-flow disclosure discipline (docs-hub 0.5.3, content-graph). Use when preparing a wp.org submission, responding to a reviewer email, fixing the plugin-check CI job, triaging PCP findings, or capturing listing screenshots.
日本語の概要は準備中です。原文の説明を表示しています。
Operational guide for the NV oOS Dependabot alert triage-and-remediation loop: querying open alerts via gh api, separating stale from genuinely vulnerable lockfile entries (default-branch forensics), deciding between safe in-major override bumps, scoped overrides, or deferred major migrations (npm pack signature diffing), regenerating the 13-lockfile tree, dismissing alerts with the right reason, GitHub issue housekeeping, and triaging the known CI failure modes. Use when asked to fix dependabot alerts, close out dependabot issues, bump vulnerable npm packages, or resume a dependabot session.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "monitor brand mentions", "set up social listening", "did anything spike about us this week", or "watch these accounts for buying triggers"; runs always-on keyless listening — a versioned listening-query architecture (brand variants incl. misspellings and 中文 names, exclusion terms, per-source syntax for HN Algolia / Bluesky / GDELT / Tavily), a mention sweep with six-class triage (crisis / bug / lead / praise / question / spam) each routed with an SLA, a 7-day rolling baseline with spike flags (the crisis trigger input), a B2B trigger watchlist (funding / hiring / launch signals), and an explicit coverage disclosure where X/IG/TikTok/LinkedIn/小红书 numbers are proxy-labeled, never Measured. Not for launch-window telemetry (T-0→T+30 rank and review polling) — use launch-monitor. 舆情监听/品牌提及监测/基线突刺/触发信号
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "optimize my Shopping feed", "fix product disapprovals", "improve product titles/attributes", or "build feed-driven PMax asset groups"; audits and rewrites the Shopping/Performance Max product feed — title/description patterns, required and recommended attributes, GTIN/availability/price hygiene, disapproval triage, and feed-driven asset-group / listing-group structure — informing the ROAS O (Offer) dimension. Not for text ad copy — use ad-creative-builder; not for scoring the account or the RQS — use ad-account-auditor. 商品Feed优化/购物广告Feed/商品标题优化/商品禁投修复
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "triage launch feedback", "cluster reviews, comments, and board posts into themes", or "set up a you asked, we shipped loop"; produces a feedback theme digest (frequency, severity, representative quotes per theme), an open→planned→started→completed/declined status loop with duplicate-merge and notification rules, shipped-change announcement material, and a compliant social-proof harvest protocol (never incentivized store reviews). Not for repurposing or amplifying the harvested proof — use content-amplifier; not for executing testimonial outreach threads — use outreach-manager. 反馈分诊/状态环/社证收割/评测合规
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "find influencers", "build an influencer list", or "discover creators in [niche]"; produces a multi-platform candidate pool, per-influencer profiles, authenticity red-flag screening, and a tiered shortlist with preliminary triage signals. Not for STAR scoring or ranking a known shortlist — use fit-scorer. 达人挖掘/找达人/创作者名单
日本語の概要は準備中です。原文の説明を表示しています。
Triage acc's open promises and close them with honest real-world verdicts via acc_act(runtime="outcome").
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Codeball — codeBall AI-powered pull request risk assessment including automatic PR quality scoring, risk classification, and auto-approval for low-risk changes. Use when configuring CodeBall for automated PR triage, risk-based review routing, and review workload optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Semgrep — semgrep static application security testing (SAST). Covers code scanning, custom rule creation, CI integration, autofix capabilities, multi-language support, and vulnerability triage. Use when scanning source code for security vulnerabilities, creating custom detection rules, or integrating SAST into CI pipelines.
日本語の概要は準備中です。原文の説明を表示しています。