Use first, before context/search fan out, when a task needs repo-local Odylith startup grounding.
日本語の概要は準備中です。原文の説明を表示しています。
102 件 ・ 関連度順
概要と使いどころ
Use first, before context/search fan out, when a task needs repo-local Odylith startup grounding.
日本語の概要は準備中です。原文の説明を表示しています。
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building self-correcting retrieval systems for AI agents. Keywords: RAG, retrieval, Corrective RAG, Self-RAG, query decomposition, reranking, hallucination, grounding.
日本語の概要は準備中です。原文の説明を表示しています。
Perform triangulated cognitive research combining SQLite memory, GitHub 10k+ stars patterns, and ToT DAG benchmarking before critical architectural decisions. Automatically triggers subagent research escalation when confidence is low (<0.70). Keywords: research, benchmark, github, memory, triangulation, grounding, best-practices, escalation
日本語の概要は準備中です。原文の説明を表示しています。
Use before loading, placing, scaling, or animating GLB models in PlayCanvas to measure bounds, grounding, clips, joints, and hierarchy with the bundled offline inspector.
日本語の概要は準備中です。原文の説明を表示しています。
Use before repeatedly placing GLB models in PlayCanvas to record each asset's uniform scale, grounding offset, pivot compensation, and yaw once.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate and review GO-CAM (Gene Ontology Causal Activity Model) activities / annotons — molecular-function typing, has-input, causal relations, complexes, evidence — and check their consistency with gene annotation reviews. Use when reviewing cached GO-CAMs under gocams/, filling a GoCamReview YAML (gocams/<id>/<id>-review.yaml), or grounding a module in GO-CAM models.
日本語の概要は準備中です。原文の説明を表示しています。
Curate, review, or repair ai-gene-review ModuleReview YAML documents under modules/, including pathway/module boundary setting, parts and variant modeling, annoton-level molecular functions, representative UniProt/PTN grounding, module deep-research provenance, validation, rendering, and project batch updates.
日本語の概要は準備中です。原文の説明を表示しています。
Frames a structured, testable threat-hunting hypothesis: grounding it in adversary behavior and available telemetry, defining the data sources and detection logic, and setting success criteria and outcomes. Activates for requests to start a threat hunt, write a hunt hypothesis, or plan a hypothesis-driven hunt.
日本語の概要は準備中です。原文の説明を表示しています。
Discovers requirements and designs an end-to-end governed agentic analytics solution using Knowledge Catalog and Managed Service for Apache Spark (Lightning Engine). Use when designing data science and analytics workflows across structured and unstructured distributed data (including in S3, Azure Blob, AlloyDB, and Iceberg), establishing metadata governance with Knowledge Catalog aspect types, or grounding agentic IDEs (VS Code, Antigravity) by using the Google Cloud Data Agent Kit. Don't use for provisioning borderless data lakehouse infrastructure (use google-cloud-solution-agentic-ai-borderless-data-lakehouse instead).
日本語の概要は準備中です。原文の説明を表示しています。
Pre-production security checklist for Agentforce deployments: agent run-as permission scope, grounding-source data classification, action write-scope, audit trail. NOT for the full go-live readiness gate covering cost telemetry, rate limits, rollout and rollback — use agentforce/agentforce-production-readiness-checklist. NOT for a general org security review — use security/security-health-check.
日本語の概要は準備中です。原文の説明を表示しています。
Build AI chatbots end to end — conversation design, persona, retrieval grounding, escalation, and deployment. Use when creating a chatbot for support, sales, or internal assistance.
日本語の概要は準備中です。原文の説明を表示しています。
Generate UI with AI tools effectively: prompt structure, design-system grounding, iteration technique, and evaluating output quality. Use when using AI to create interfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Track AI visibility — measure whether a brand is mentioned and cited by AI assistants (Gemini, ChatGPT, Perplexity) for target prompts. Runs scans, tracks mention/citation rates over time, detects trends, and identifies opportunities. Uses Gemini API free tier (with grounding) as primary method, web search as fallback. Use when a user wants to: check if AI models mention their brand, track AI citation changes over time, measure AEO content effectiveness, monitor competitor AI visibility, or audit their brand's presence in AI-generated answers. Pairs with aeo-prompt-research-free (identifies prompts) and aeo-content-free (creates/refreshes content). This skill closes the loop by measuring results.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze what search queries Gemini uses when answering a prompt, by running it multiple times with Google Search grounding and reporting frequency distribution. Use when investigating AEO query patterns, understanding how AI models search the web for a topic, or studying the probabilistic nature of AI-triggered search queries.
日本語の概要は準備中です。原文の説明を表示しています。
Use for affordances, hierarchical control, nullspace composition, and information-seeking action selection in embodied agents. NOT for pure symbolic planning, generic RL tuning, or domains without sensorimotor grounding.
日本語の概要は準備中です。原文の説明を表示しています。
Bind NeatContext to the current Kimi Code session, route requests, and load selected context grounding safely.
日本語の概要は準備中です。原文の説明を表示しています。
The kpopper method: a knowledge record (GROUNDING.yaml) for work that gets revisited - what is known, where each piece came from, and what would make each conclusion wrong. Use when asked what kpopper is or how to keep a record, when choosing which kpopper skill fits a moment, or when no narrower one does. The occasions have their own skills: ground (read the record before answering), record (write what the work found), map (map existing materials), annotated-doc (a standalone HTML document with evidence), hub (the record's visual home), consolidate (hypotheses and merges), watch (background checks).
日本語の概要は準備中です。原文の説明を表示しています。
Write what the work found into the project's knowledge record, so the next session inherits it instead of re-deriving it. Use the moment something worth keeping exists: a fact taken from a source, a rule worked out, a decision or conclusion, a measurement, a correction to a recorded value, or a question left open - and check for unrecorded findings before implementation, handoff (including a PR), or finishing work. Record within the user's write authorization. The first write creates GROUNDING.yaml. Covers one-report update, add, set, review, same and distinct, judgments with a falsifier, and background capture.
日本語の概要は準備中です。原文の説明を表示しています。
Read the project's knowledge record before answering from memory or from the files. Use before answering about the project's state, a number, a date, a decision, a source, a deadline or what was agreed - even a casual 'what's the situation with X' or 'is that quote still current'; before changing a recorded value; and whenever the opener or a grounding line names entries. After finding relevant IDs, prefer kpop context to read them with their declared dependencies and checks. Uses pull for concise readings or when the checked reader is unavailable, affects for changed inputs, and search when no ID is known. A missing id is not absence. Not for showing the record's page (the hub skill). Requests come in any language.
日本語の概要は準備中です。原文の説明を表示しています。
Adaption AI SDK for synthetic data augmentation and dataset adaptation. Use when building data pipelines with the Adaption Python SDK, uploading datasets (local files, Hugging Face, Kaggle), running augmentation/adaptation jobs, configuring brand controls (hallucination mitigation, safety categories, length), recipe specifications (reasoning traces, deduplication, preference pairs, prompt rephrase), evaluating dataset quality, downloading results, or any workflow involving `pip install adaption`, `from adaption import Adaption`, Adaptive Data, or the adaptionlabs.ai API. Also trigger when the user mentions synthetic data generation for fine-tuning, dataset augmentation pipelines, DPO preference pair generation, or grounding-based hallucination reduction on training data.
日本語の概要は準備中です。原文の説明を表示しています。
Default material, information-density hierarchy, clean-rendering, negative-prompt hygiene, and evidence-preserving photo-repair layer for IM2 / GPT Image 2 / gpt-image-2 / image_gen. Use for clean generation/redraws, artifact cleanup, focal-detail control, atmospheric depth, physically coherent light paths, air scattering, volumetric light, light ratio, material realism, architecture/terrain/hard-surface scene mass and structural grounding, and 企业/公司活动/门店/团队合影/商品/餐饮/证件文档照片修复. Preserve identity, headcount, placement, product facts, text, logo, QR, date, price, and scene evidence; prefer residual blur over invented restoration detail.
日本語の概要は準備中です。原文の説明を表示しています。
Run a live investigation as an operator-driven query loop: the operator runs each query on the live system and pastes the result back, and you guide the investigation one labelled query at a time. Use alongside support-assist (which covers what to investigate) whenever someone is pasting query or command output back from a deployment, especially during an incident. Covers labelling, pacing, making each query decide the next step, version-grounding, and keeping queries cheap and correctly classified.
日本語の概要は準備中です。原文の説明を表示しています。
E2B Desktop Sandbox with autonomous computer use — cloud Linux environments for browser automation, visual UI grounding, screenshot analysis, and shell execution. Supports Browser Use cloud sessions, Playwright integration, and LLM-driven desktop control. Use when asked about sandboxes, computer use, browser automation, E2B, desktop control, visual testing, or cloud Linux environments.
日本語の概要は準備中です。原文の説明を表示しています。