「are」の検索結果

Run Telegram as a scoped auto-reply assistant grounded in the owner's vault and written in their voice: whitelisted low-stakes chats are answered autonomously, while anything financial, committing, sensitive or from an unknown contact becomes a draft for the owner. Triggers: "handle my telegram", "reply for me in <chat>", or a new message in a whitelisted chat.

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

Health-check, audit and, on approval, fix a self-hosted n8n automation stack. Health is read-only; any workflow edit goes preview, approval, apply. Triggers: "/n8n", "/n8n health", "/n8n fix <id>", "which workflows are failing".

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

Send one research question to as many independent LLMs as possible at once, each in its strongest reasoning mode with proof of that mode, then synthesize. Floor of 3 models, quorum of 4; late answers are collected later. Use for high-stakes questions where one model's view is not enough. Triggers: /hyper, hyper research, ask every LLM, max fan-out research.

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

Protocol for two LLM agents (Claude, Codex or any other) to agree and work from one shared folder: message format, channels, roles, evidence rules, wake-up alarm and anti-patterns. Triggers: /llm-pact, agree with codex, connect a second agent, pair rules, agent consensus, two-agent protocol.

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

Package a contribution (gist, script, fix or skill) as a product instead of a bare snippet: README with problem and result, install steps, a test, license, honest limits and a clear entry point. Use before publishing a gist, sharing a fix or releasing a slice of internal tooling. Triggers: /pack, package this properly, make it a product, ship it with quality.

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

Health-check the connected MCP servers and scout new ones: the safe pre-flight before integration work, plus a connector finder. Read-only by default. Triggers: "/mcp", "/mcp health", "/mcp discover <need>", "which MCP servers are alive", "find an MCP for <X>".

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

Move or sync the hub role of an agent-plus-vault setup between computers, where an always-on desktop is the hub and laptops are satellites. Checklist with counters verified before and after, and it never migrates silently. Triggers: "/migrate", "/migrate check", "/migrate pack", "/migrate bootstrap".

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

List incoming deliverables held in quarantine: fixes, scripts and tasks that arrived over file sync from an unverified source or without a signature and are not applied until the owner decides. Fail-closed by design. Triggers: "/quarantine", "what is quarantined", or a deploy check reporting held items.

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

Keep serialized build-in-public content continuous: read one canon file of season, arcs, beats and loops and say which narrative beat to advance next, so episodes chain into a series. Pairs with the episode adapter, which does the writing. Triggers: "/reality-show", "season state", "what arcs are open".

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

Measure a target repository's queue and find a live open issue the contribution would close, before opening a pull request there. Reports how many PRs are open, how many of the last N closed ones were actually merged, and which issue to attach to, because a cold PR into a dead queue is a wasted artifact. Triggers: "/issue-match", "is this repo worth a PR", "measure the queue".

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

Onboard a new machine as a receive-only follower on a multi-machine agent network: it reads the shared vault, canon, skills and memory, runs nothing heavy locally (no RAG, reindex or GPU), and never receives executable hooks from the hub. Checklist-driven, with a verify step at each stage. Triggers: "/follower-onboard <machine>".

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

Write a self-contained handoff document so another session, person or machine continues the work without this session's context: decisions and why, what is done and tested, exact paths and values, open blockers, boundaries, and an explicit continue-from-here step. Lands in a synced folder with a short seed prompt. Triggers: "/handoff", "prepare a handoff", "hand this off".

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

Use Gemini as a third external reviewer alongside two other vendors: diff review with an APPROVE or REQUEST_CHANGES verdict, and QA-breaker duty in the post-build test ritual. Headless over REST with a CLI fallback, and verdicts go to a shared usage journal. Triggers: "/gemini review", "gemini opinion on this diff".

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

- Enumerate an organisation's subdomains and sibling domains from Certificate Transparency logs and passive DNS, without sending traffic to the target. Use when looking for staging, dev, admin or VPN hosts, mapping the full hostname footprint of a domain, or spotting infrastructure a company forgot it had

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

- Build an entity-relationship link-analysis graph of an investigation — nodes, typed edges carrying source and confidence, aliases, and temporal validity — to expose shared infrastructure, bridging nodes and the real principal behind a [человек]. Use when an investigation has outgrown a list and needs a graph, or when asked how a set of people, companies and domains connect

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

Health-check the second brain so failures are not silent: is the local search server alive, is the RAG index fresh, is the session-memory ledger filling, did the nightly distillation run. Read-only, with a green/red verdict per component. Triggers: "/brain", "/memory", "is the reindex alive".

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

Find a Telegram chat, group or channel by name and return its numeric id and t.me link from a local index, with no live crawl. Also answers which groups you share with a person or company. This is the chat lane, not people search. Triggers: "/chat <query>", "find the <X> chat", "chat id for <X>".

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

Read the system-architect map: a deterministic catalog of everything the setup is made of (vault, import scripts, scheduled tasks, MCP servers, SQLite databases, hooks, skills, dashboards), what is healthy and what fell off. Consult it before changing shared infrastructure and re-scan after. Triggers: "/arch", "/arch broken", "/arch scan", "what broke in the system".

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

Cross-vendor code review: this agent reviews the other agent's diff and the other agent reviews this one's, so the final check always comes from a different model. Verdicts are APPROVE or REQUEST_CHANGES with file:line references. Triggers: "/codex-review", "cross-review this diff", "have the other vendor check this".

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

Send and read messages between machines in a fleet over a shared Telegram group, so cross-machine coordination survives a file-sync outage and humans can watch the machines talk. A synced folder stays as the fallback for oversized payloads. Triggers: "/bus", "post to the bus", "check the bus", "tell the other machines".

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

Pull new and changed claude.ai web conversations into an Obsidian vault, extract artifacts as first-class notes, concept-link them, and refresh the RAG index and dashboard. Idempotent: curated notes are never overwritten. Triggers: "/claudeai-sync", "pull claude.ai", "grab new claude.ai chats".

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

Build a dashboard from idea to live link in one pass: create the visualization, file it in one shared catalog, cross-link it with the others, publish to GitHub Pages and return the working URL right away. Use when results carry more than one fact to decide on. Triggers: /dash, build a dashboard, show it visually, publish the dashboard, give me the dashboard link.

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

Work the comments under published posts in one pass: list unanswered ones, reply only where a reply is genuinely expected (at most three per pass), name top commenters as warm-DM candidates, and prepare reply drafts on approval. Triggers: "/comments", "unanswered comments", "who is commenting".

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

Write a bold, value-adding follow-up when your own outbound message got silence: check the thread, pick a second channel, add new value instead of a bare bump. Use when an email, DM or PR comment went unanswered. Triggers: /bold-followup, /bump, follow up on silence, second channel.

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