「guardian」の検索結果

Prospect discovery, enrichment, scoring, and reporting against an Ideal Customer Profile

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

Turn any external program into a Genesis module via structured discovery, connection mapping, config generation, and verification.

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

Evaluate technologies and competitive developments against Genesis architecture

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

Systematic debugging of issues — use when a test fails, runtime error occurs, unexpected behavior is reported, or an awareness tick produces anomalous results

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

Canonical guide to Genesis browser automation - layers (Camoufox, Chromium, the user's Chrome over CDP, TinyFish, desktop), per-tool timeouts, safety gates, verify-after-act, what a click checks (scroll, hit test, covered targets), overlays, iframes, tabs, and failure diagnosis

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

Forward Deployed Engineer delivery contract for AWS engagements, build-first artifacts, grounded cost estimates, Well-Architected review, evolution roadmap

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

Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?"

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

Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"

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

Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"

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

Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"

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

Fetches YouTube video metadata and transcripts (genesis web_fetch MCP tool first, yt-dlp via Bash as the fallback). Activate when the user shares a YouTube URL (youtube.com, youtu.be), asks to 'fetch this video', 'get the transcript', 'what does this video say', 'summarize this YouTube video', or references video content that needs to be retrieved. Also activate when processing multiple YouTube URLs in batch. Do NOT use for non-YouTube video platforms, local video files, or audio-only podcast URLs.

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

Anti-detection behaviour for Genesis browser automation - what the Camoufox tools already do, what the agent must still do, Cloudflare Turnstile handling, and per-site notes for bot-hostile sites

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

This skill should be used when the user asks to "optimize my LinkedIn profile", "update my LinkedIn headline", "rewrite my LinkedIn summary", "improve my LinkedIn about section", or when Genesis identifies that the user's profile doesn't align with their current goals or target audience.

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

This skill should be used when the user asks to "write a LinkedIn message", "draft a connection request", "help me reach out to someone on LinkedIn", "write an InMail", "message this person", or when the prospect-researcher skill identifies a high-value contact worth reaching out to. Also triggered by "how should I approach [person/company]" in a LinkedIn context.

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

This skill should be used when the user asks to "plan my LinkedIn content", "create a content calendar", "what should I post about this week", "plan my posting schedule", or when Genesis proactively suggests a weekly content plan during surplus compute. Also triggered by "I need post ideas" or "I don't know what to write about".

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

Superforecasting with calibrated reasoning, Brier score tracking, and prediction ledger management

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

Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"

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

Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"

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

Gatekeeping Git/PR by classifying change essence and recommending granularity, naming, and strategy. Use when PR preparation or commit strategy is needed.

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

Use at write time to vector/embedding memory — Grove content-addressed insertion, chroma/pgvector upserts, memory-consolidation promoting session traces to MEMORY.md, or embedding externally-ingested content. Scores each candidate record against a fixed panel of sentinel queries and quarantines any record that would become the nearest neighbor of too many unrelated queries — a hub — whether from adversarial poisoning or accidental over-generality. This is the memory-record-side sibling of skill-injection-guardian (file-side) and the write-side complement of memory-use-warrant (read-side). Quarantine, never silently drop; a human reviews. Backed by the admission-time hubness gate (arxiv 2606.19692v1). Triggers on inserting into vector memory, consolidating memory, and embedding stranger content.

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

VNX orchestration infrastructure guardian - maintains dispatcher, smart tap, receipt processor, intelligence systems, and documentation.

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

Use for Codex-app worktrees. Triggers: worktree, rename worktree, detached HEAD, ~/.codex/worktrees, 워크트리, 워크트리 이름, 새 워크트리, 브랜치랑 워크트리.

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

Implement layered collective defense using alarm signaling, role mobilization, and proportional response. Covers threat detection, alert propagation, immune response patterns, escalation tiers, and post-incident recovery for distributed systems and organizations. Use when designing defense-in-depth where no single guardian covers all threats, building incident response that scales with severity, or when current defense is over-reactive to every alert or under-reactive to genuine threats.

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

Assume the role of Galyarder CTO (Chief Technology Officer). Technical guardian. Enforce technical integrity, architectural determinism, self-healing formal verification, and planetary computational leverage.

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