「bot」の検索結果

Build cost-safe geospatial SQL for BigQuery, DuckDB, Snowflake, Wherobots, and Postgres and/or render results on an interactive Dekart map.

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

Review uncommitted code changes to find unreasonable design, unfinished requirements, potential bugs, missed reuse opportunities, and optimization opportunities. Use when the user asks for a review of pending, uncommitted, or unpublished code changes and expects both findings and concrete improvements.

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

Use Avibe's local Computer Use CLI for carefully bounded desktop observation and actions.

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

Use Avibe Vault for API keys, tokens, passwords, protected credentials, authenticated HTTP requests, or digest signing without exposing secret values to the agent.

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

Use `vibe watch` to run a managed Harness waiter that returns to the same conversation later. Best for reviews, CI, files, logs, and other wait-now-continue-later workflows.

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

Use Avibe Harness for durable Agent delegation, Sessions, scheduled Tasks, Watches, Runs, queues, and work that must continue beyond the current turn.

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

Audit and improve the prompt surface of Avibe Agents across backends (Claude, Codex/GPT, OpenCode) — global and project rules, Agent system prompts, Skills, delegation briefs, and Task and Watch messages — using real run evidence. Use when an Agent misbehaves (stalls, over-asks, over-reaches, ignores or over-applies a rule), after a model or backend change, or when the user asks to review, clean up, or tighten prompts.

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

Safely inspect and modify local Avibe configuration, routing, runtime settings, watches, scheduled tasks, Avibe Cloud remote access, and operational state. Also use it to report an Avibe bug, send product feedback, or file a feature request from the current conversation.

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

Build, inspect, update, restore, or share Avibe Show Pages for visual explanations, diagrams, reports, or interactive prototypes. Covers the page workspace and its Git history.

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

Deliver implementation PRs across Avibe, avibe-backend, avibe-docs, avault, and vault-sandbox. Required for branch and scope discipline, Codex review, CI, circuit breaking, and user-facing close-out, regardless of agent backend.

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

Use the official Sentry CLI to investigate issues, events, traces, and logs for Vibe Remote without committing Sentry credentials into the repository.

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

Use when starting any task, before invoking any other skill or GSD command, to route between Superpowers skills and GSD commands from project state and task scope. Fires first when both systems are installed.

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

Weekly. Scores the week from the ledgers with a source path beside every number and never writes a number it did not count in a file this run. It names exactly two things and files both as cards, the one fix worth doing next week and the one thing to stop, and it replays every learned browser flow once, read only, so a drifted selector is found on a Friday rather than on a Tuesday morning a routine needed it.

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

Weekly, on a Friday, read only everywhere. Scores the week from the ledgers with a source beside every number, replays the browser flows the other routines depend on, names one thing to kill and one thing to scale, and files both as cards. It sends only where you released the channel, spends only where you released it, never touches a credential, and never writes a number it did not measure.

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

Weekdays, heavy browser lane. Reads the member's own signal sources and saved searches, captures dated buying signals together with the contactable people attached to them, and appends both to the ledgers the outreach queue reads. Read only on every people surface, LinkedIn included. It holds every outbound action unless you released the channel, and it never touches a credential.

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

Weekly, file work only, no browser at all. Reads everything the week produced, picks exactly three moves, and argues both sides of each one before the member reads a word of it, with every clause carrying a number or an observation from a file it names. It argues against its own top recommendation last, records a predicted effect and the metric that would show it so the monthly review can score it, and files each move onto the register. It sends only where you released the channel, spends only where you released it, never deploys, and never touches a credential.

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

Weekly, on a Friday, read only everywhere. Scores the week from the ledgers with a source path beside every number, replays the browser flows the other routines depend on, names one thing to kill and one thing to scale, and files both as cards. It sends only where you released the channel, spends only where you released it, never touches a credential, and never writes a number it did not count out of a named file this run.

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

Monthly, on the last weekday, light browser lane. Re-tests every named qualification test and every buyer segment against a month of this kit's own ledger evidence, then rewrites both files itself where the evidence disagrees with the assumption they were written on. It records every change in strategy/CHANGELOG.md with the ledger path that justified it. It sends only where you released the channel, never re-queues anyone, never edits the contacted ledger, and never writes a number it did not count out of a named file.

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

Enhanced Mikado Method for complex architectural refactoring - systematic dependency discovery, tree-based planning, and bottom-up execution

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

Use when the next period ADS plan must be built from last period results — read the report and the audit, keep and scale winners, stop or fix losers, set new test hypotheses, split budget, plan three budget scenarios, and schedule the creative pipeline. Trigger on 'next month ads plan', 'plan ads from the report', 'what should we run next month', 'Q4 ads plan', 'next quarter media plan', 'the month ended, now what'. Also use when a report and an audit both exist and no decisions have been made. Not for — the first media plan before any data, see `54-media-plan-global`; scoring the account, see `21-ads-audit-global`; the next period CONTENT plan, see `40-next-content-plan-global`.

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

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.

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

Resolve an in-progress Git merge or rebase conflict while preserving the relevant intent of both sides. Use when conflict markers or an interrupted merge/rebase need investigation and resolution.

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

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

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

Optimize NestJS throughput with Fastify adapter, singleton scope enforcement, compression, and query projections. Use when switching to Fastify, diagnosing request-scoped bottlenecks, or profiling API overhead.

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