7,562 件 ・ 人気順
概要と使いどころ
Run evaluations for Hugging Face Hub models using inspect-ai and lighteval on local hardware. Use for backend selection, local GPU evals, and choosing between vLLM / Transformers / accelerate. Not for HF Jobs orchestration, model-card PRs, .eval_results publication, or community-evals automation.
日本語の概要は準備中です。原文の説明を表示しています。
Set up a Slack notification channel (Sentinel) for a colony by driving the browser — reuse or create the "Hive Sentinel" Slack app from a JSON manifest, install it, capture the bot + app tokens, create/select the channel via the Slack API, and turn Sentinel on so the colony can ping the user on Slack and accept replies. Use when the user asks to "set up Slack notifications", "get pinged on Slack", "connect Slack for alerts", "set up Sentinel on Slack", or clicks the in-app "Set this up with the agent" button on the Slack channel step. Requires hive.browser-automation.
日本語の概要は準備中です。原文の説明を表示しています。
Read before automating X / Twitter with browser_* tools. Verified flows for post, reply, delete, search-and-engage, plus the Draft.js compose quirks that silently disable the send button. Includes the daily-reply and job-market-reply playbooks. Requires hive.browser-automation for the underlying screenshot + coordinate workflow. Verified 2026-04-11.
日本語の概要は準備中です。原文の説明を表示しています。
Claim tasks, record step progress, and verify SOP gates in the colony SQLite queue. Applies when your spawn message includes a db_path field.
日本語の概要は準備中です。原文の説明を表示しています。
Set up a Telegram notification channel (Sentinel) for a colony by driving the browser — create a bot via @BotFather in Telegram Web, store its token, detect the chat to notify, and turn Sentinel on so the colony can ping the user on Telegram and accept replies. Use when the user asks to "set up Telegram notifications", "get pinged on Telegram", "connect Telegram for alerts", "set up Sentinel on Telegram", or clicks the in-app "Set this up with the agent" button on the Telegram step. Requires hive.browser-automation.
日本語の概要は準備中です。原文の説明を表示しています。
Required before any hive-browser CLI command. The browser is driven from the terminal by running `hive-browser <command> ... --json` via terminal_exec — not via MCP tools. Teaches the browser lifecycle rules (the bridge attaches to the USER'S running Chrome — never kill or launch browser processes; timeouts are transport issues, not crashes), the screenshot + coordinate workflow (hive-browser interact with a fractional coordinate) that reaches shadow-DOM inputs selectors can't see, the viewport-fraction coordinate rule (not pixels), rich-text editor quirks ("send button stays disabled" failures), and CSP gotchas. Covers Chrome via CDP through the GCU Beeline extension.
日本語の概要は準備中です。原文の説明を表示しています。
Read before automating LinkedIn with browser_* tools. LinkedIn combines shadow DOM (#interop-outlet), strict Trusted Types CSP that silently drops innerHTML, Lexical composer, native beforeunload dialogs that hang the bridge, and aggressive spam filters — each has bitten us at least once. Verified flows for profile messaging, connection-request acceptance, feed composition, and search. Requires hive.browser-automation. Verified against logged-in production 2026-04-11.
日本語の概要は準備中です。原文の説明を表示しています。
Run independent subtasks in parallel — one git worktree and one implementation sub-agent per task, each opening its own PR — then cross-review every PR. polly never merges; the human does.
日本語の概要は準備中です。原文の説明を表示しています。
Commit the validated fix and follow local-only, workflow-owned, or direct PR publication.
日本語の概要は準備中です。原文の説明を表示しています。
Route gh-aw workflow design/create/debug/upgrade requests to the right prompts.
日本語の概要は準備中です。原文の説明を表示しています。
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents
日本語の概要は準備中です。原文の説明を表示しています。
Configure GSD workflow toggles and model profile
日本語の概要は準備中です。原文の説明を表示しています。
workflow | discuss plan execute verify phase progress
日本語の概要は準備中です。原文の説明を表示しています。
Check progress, advance workflow, or dispatch freeform intent — the unified GSD situational command
日本語の概要は準備中です。原文の説明を表示しています。
Configure GSD settings — workflow toggles, advanced knobs, integrations, and model profile
日本語の概要は準備中です。原文の説明を表示しています。
Batch several `/gsd-quick`-shaped tasks together — planned, dispatched, and merged as one run
日本語の概要は準備中です。原文の説明を表示しています。
Capture ideas, tasks, notes, and seeds to their destination
日本語の概要は準備中です。原文の説明を表示しています。
Execute a trivial task inline — no subagents, no planning overhead
日本語の概要は準備中です。原文の説明を表示しています。
Post-mortem investigation for failed GSD workflows — diagnoses what went wrong.
日本語の概要は準備中です。原文の説明を表示しています。
This repo is indexed by graft/. For ANY task here, whether understanding how something works, finding where code lives, tracing what calls a symbol or what a change breaks, or scoping an edit, get your context from graft before grepping or reading source files.
日本語の概要は準備中です。原文の説明を表示しています。
This repo is indexed by graft/. For ANY task here, whether understanding how something works, finding where code lives, tracing what calls a symbol or what a change breaks, or scoping an edit, get your context from graft before grepping or reading source files.
日本語の概要は準備中です。原文の説明を表示しています。
Generate weekly status-request email drafts to outside counsel across the active portfolio — markdown per matter, plus Gmail drafts when the MCP is available. Use when the user asks for OC status requests, weekly outside counsel check-ins, or wants per-matter status emails drafted from the portfolio log.
日本語の概要は準備中です。原文の説明を表示しています。
Triage a subpoena served on the company — classify it, analyze scope/burden/privilege, cross-check the portfolio, and produce an objections framework, compliance plan, and deadline calendar. Use when the user says "we got a subpoena", "served with a subpoena", or shares a subpoena, CID, or third-party document request to evaluate.
日本語の概要は準備中です。原文の説明を表示しています。
Log a client communication — call, email, text, letter, in-person, voicemail. Append-only per-case record with dated entries, direction, medium, summary, action items. Works alongside /client-letter and /status client. Use when logging a call or client email, reviewing a communication log, or asking "what did we tell [client] last time".
日本語の概要は準備中です。原文の説明を表示しています。