Results for “triage mode”

AI-assisted label triage for NVIDIA/NemoClaw issues and PRs. Reads triage-instructions.md at runtime for consistent label guidance. Supports single-item mode (give it a number) and batch mode (fetches up to 50 unlabeled open items). On approval, applies labels and an optional triage comment via gh CLI, then logs the session to the daily-rhythm activity folder. Trigger keywords - triage, label issues, suggest labels, batch triage, triage issue, triage PR, label this, what labels.

The English summary is being prepared. Showing the original description.

Review source code without running it to identify potential security vulnerabilities. Findings include severity, confidence, attack scenarios, and suggested fixes, delivered as JSON for further triage and Markdown for human review.

• Review source code for potential vulnerabilities
• Focus a scan using a threat model
• Prepare findings for further triage

Triage mode operational spec for the team lead. Returns lead identity, facilitator identity, mode-specific rules, suggest-members guidance, and phase arc for triage teams that diagnose an issue without changing it.

The English summary is being prepared. Showing the original description.

Process large email, document, and transcript archives by routing items to AI models according to their importance. Rule-based privacy checks run before model calls, while extracted information becomes linked knowledge pages with progress checkpoints.

• Extract useful information from large email archives
• Organize decisions and advice from meeting transcripts
• Route reports to suitable models by importance

Use when the user asks to "triage our comments, DMs, and mentions", "draft replies to this thread", "can we repost this fan post", or "set up inbox SLAs and an escalation path"; produces a ranked triage queue with register detection (sincere / ironic / performative / parasocial, sentiment-inversion table included — "this is so bad" under a comedy register is praise), a commenter taxonomy (troll monitor-only / rager / misguided / unhappy-customer / advocate) with a response-tier ladder and per-channel SLAs, an escalation matrix ending at the crisis path, a moderation ladder plus house rules for owned spaces, and a UGC curation-and-rights mode whose dated permission entries route to the channel registry — every reply is a ranked DRAFT a human posts; nothing is ever auto-sent. Not for launch-window feedback triage — use launch-feedback-synthesizer. 评论私信提及分诊/语域识别/回复草稿/UGC授权

The English summary is being prepared. Showing the original description.

Find the decisions in a pipeline that do not need the expensive model and propose the gate for each: a rule, a classic classifier, or a small model, with fail-closed routing. Use when the user asks to cut model costs or latency, says the big model handles everything, or wants a triage / routing / filter layer in front of an agent. Analysis plus an optional baseline scaffold. Do NOT use for auditing context layout (context-audit) or for building eval suites (evals-bootstrap).

The English summary is being prepared. Showing the original description.

When you want to manage projects across your businesses using a kanban + Eisenhower methodology. One kanban per business (whatever portfolio of businesses, projects, or initiatives you run). Tool-agnostic — connects via API/MCP to whatever PM tool each business uses (Notion, GitHub Projects, Plane, Linear, Obsidian file-based, or manual mode). Async-first output. Six modes — setup (scaffold a new board for a business), triage (Eisenhower-sort the backlog), next (pick the next thing to work on, single board or across all), status (paste-ready async snapshot), unblock (diagnose Review/Blocked column), weekly (Friday pulse + week planning). Triggers on "/pm," "/pm setup," "/pm triage," "/pm next," "/pm status," "/pm unblock," "/pm weekly," "what should I work on next," "kanban status," "Eisenhower this," "triage my backlog," "what's blocked."

The English summary is being prepared. Showing the original description.

OCRs scanned or image-only corpora with vision-language models in four phases. Triage inventories the scans, identifies script and language, and shortlists models by script, hardware, and data constraints. Evaluate selects a system by measured CER or WER against ground truth, using born-digital twins, a second reader, and decision rules set in advance. Run builds the production pipeline. Clean removes model artifacts, audits what every cleaning rule deletes, corrects with rule-based and LLM passes, and records provenance. Use when choosing an OCR model for a corpus, measuring OCR accuracy, transcribing scans at scale, or correcting raw OCR. Born-digital documents with text layers go to doc-to-markdown; runs on Leiden's ALICE cluster add vlm-ocr-alice.

The English summary is being prepared. Showing the original description.

Use when the user asks to "triage our comments, DMs, and mentions", "draft replies to this thread", "can we repost this fan post", or "set up inbox SLAs and an escalation path"; produces a ranked triage queue with register detection (sincere / ironic / performative / parasocial, sentiment-inversion table included — "this is so bad" under a comedy register is praise), a commenter taxonomy (troll monitor-only / rager / misguided / unhappy-customer / advocate) with a response-tier ladder and per-channel SLAs, an escalation matrix ending at the crisis path, a moderation ladder plus house rules for owned spaces, and a UGC curation-and-rights mode whose dated permission entries route to the channel registry — every reply is a ranked DRAFT a human posts; nothing is ever auto-sent. Not for launch-window feedback triage — use launch-feedback-synthesizer. 评论私信提及分诊/语域识别/回复草稿/UGC授权

The English summary is being prepared. Showing the original description.

Work through GitHub pull request feedback by classifying findings, fixing code, running repository checks, and posting replies. With suitable permissions, the skill repeats Copilot reviews until the latest code is reviewed and every thread has an agent response.

• Address outstanding Copilot review comments
• Run repeated reviews on a completed pull request
• Explain declined suggestions and hand off design decisions

Coordinates specialist agents in Claude Code to work from product requirements through design, implementation, testing, deployment, and operations. Includes task queues, saved progress, parallel reviews, and recovery workflows for managing extended development work.

• Turning product requirements into development tasks
• Coordinating implementation, testing, and reviews
• Resuming extended work from saved progress

Prepare a draft letter demanding an end to trademark or copyright infringement, or assess a letter you received. It organizes rights, demands, counterparty risks, and response options for attorney review, following your team's enforcement policy.

• Drafting an infringement warning letter for attorney review
• Assessing a received cease-and-desist letter
• Reviewing counterparty risks before asserting rights

Support ClawHub staff moderation through its local admin tool, including skill reports, removals and restores, user restrictions, publisher and package management, and staff email, with approval checks and verification after changes.

• Triage skill reports and restore hidden listings
• Ban users or lift account restrictions
• Manage organization publishers and package ownership

Sets up AFL++ to test C/C++ programs with varied generated inputs, a technique called fuzzing. Covers running tests across CPU cores, monitoring progress, reducing input collections, and reproducing crashes for investigation.

• Running C/C++ fuzzing across multiple CPU cores
• Exploring further after libFuzzer progress stalls
• Monitoring fuzzing progress and stability

Add fast, local, typed decisions to any project with Laya, an open-source non-generative decision model (pip install laya). It classifies, routes, scores and answers yes/no questions about a piece of text, returning calibrated probabilities in roughly 20-35 ms on a laptop GPU, with no LLM call and no data leaving the machine. Use this skill whenever the user wants to classify or route text, triage tickets or emails, detect spam, phishing, toxicity or intent, put a guardrail in front of an agent or LLM, score something against a rubric, or replace an LLM-based classifier to cut latency or cost. Also use it when they mention Laya, Jev, a "System 1 model", "typed decisions" or a "decision model", even if they never name Laya.

The English summary is being prepared. Showing the original description.

Expert in integrating Claude Code with CI/CD pipelines. Covers headless mode for non-interactive execution, GitHub Actions and GitLab CI/CD integration, automated code review, issue triage, and PR workflows. Essential for teams wanting AI-powered automation in their development pipelines. Use when "claude code CI/CD, headless mode, GitHub Actions claude, GitLab CI claude, automated code review, PR automation, issue triage, claude-code, cicd, automation, github-actions, gitlab, headless, pipeline, devops" mentioned.

The English summary is being prepared. Showing the original description.

Runs security audits on codebases — full scans, diff reviews, threat models, vulnerability triage, remediation guidance, and finding tracking. Activate when the user says "security scan", "audit this repo", "review this PR for security", "threat model", "triage vulnerabilities", "fix this vuln", or "track findings".

The English summary is being prepared. Showing the original description.

OCR scanned or image-only corpora with vision-language models in four phases: `triage` inventories the scans, identifies script and language, and shortlists models by script, hardware, and data constraints; `evaluate` picks a system by measured CER/WER against ground truth, using born-digital twins, a second reader, and decision rules set in advance; `run` builds the production pipeline; and `clean` removes model artifacts, audits what every cleaning rule deletes, corrects with rule-based and LLM passes, and records provenance. Born-digital documents with a text layer go to $doc-to-markdown; runs on Leiden's ALICE cluster add $vlm-ocr-alice.

The English summary is being prepared. Showing the original description.

Google Workspace CLI (gws) リファレンス。Rust 製。 `gws <service> <resource> <method>` 形式で Gmail / Drive / Calendar / Sheets / Docs / Chat 等 19 サービスを統一操作。Google Discovery Service 経由の動的コマンド生成。 `+` プレフィックスのヘルパーコマンド（+send, +agenda, +upload, +triage 等）、 ワークフロー合成（+standup-report, +meeting-prep, +weekly-digest）、 OAuth / サービスアカウント / CI ヘッドレス認証、env vars / .env / keyring 設定、 グローバルフラグ（--dry-run, --page-all, --sanitize）、exit codes、Model Armor 統合。

The English summary is being prepared. Showing the original description.

Assess OpenClaw security reports against released versions and documented trust boundaries, which define trusted users and components. Gather evidence to recommend closing, keeping open, or narrowing a report, and draft a maintainer response.

• Assessing an OpenClaw security report
• Checking whether released versions contain a reported bug
• Comparing a report with existing advisories

Sort issues and external pull requests, which are proposed code changes, by category and readiness. Verify reports, identify missing information, and record clear briefs so an agent or a person can take the next step.

• Finding issues that need a maintainer's attention
• Checking a bug report or an external pull request
• Preparing a clear brief for an agent to work from

Get started with vulnerability review through a guided practice target, from threat modeling to scanning and triage. Ask questions about the pipeline and receive answers grounded in its documentation and source, with references and a next command.

• Learn the vulnerability review workflow
• Try a first scan on the bundled practice target
• Find commands with supporting documentation

Review issues and external pull requests, classify them, verify their claims, and assign a handling state. The skill checks existing implementations and past rejections, requests missing details, and prepares briefs that agents or human maintainers can act on.

• Find issues and external PRs needing attention
• Reproduce reported bugs and verify PR changes
• Prepare work briefs for agents

Run an external frontier-model referee (Claude Code -> a different vendor's frontier model via the Oracle CLI) on a paper, proof, estimator, or replication package -- and adjudicate what comes back. Use when the user says "send this to oracle", "get an external review", "run a referee round", "deep-check this proof", or before a submission when an independent second opinion is worth more than another in-house pass. Never launches bare: brief first, evidence-forcing prompt, coverage manifest, then CONFIRMED/REFUTED/DOWNGRADED triage.

The English summary is being prepared. Showing the original description.