Pinecone serverless vector database -- index management, vector operations, metadata filtering, namespaces, hybrid search, inference API
日本語の概要は準備中です。原文の説明を表示しています。
3,133 件 ・ 関連度順
概要と使いどころ
Pinecone serverless vector database -- index management, vector operations, metadata filtering, namespaces, hybrid search, inference API
日本語の概要は準備中です。原文の説明を表示しています。
Chroma vector database -- collection management, automatic embedding, metadata filtering, document storage, query patterns
日本語の概要は準備中です。原文の説明を表示しています。
Audit technical, on-page, and AI-search SEO for pages, sites, and content. Use when the user asks for `/seo-audit`, `/ai-seo`, SEO review, keyword targeting, heading structure, metadata, internal linking, content gaps, AEO, GEO, LLMO, or competitor SEO comparisons.
日本語の概要は準備中です。原文の説明を表示しています。
Use for a whole-corpus, read-only audit of tracked stablecoin static metadata and domain sidecars, especially after catalog changes or when factual or internal-consistency drift needs review.
日本語の概要は準備中です。原文の説明を表示しています。
Read a Prisma Next structured error envelope and route to the right recovery — code, domain, severity, why, fix, meta. Use for error, exception, my emit failed, my query won't typecheck, my query crashed, my migration won't apply, MIGRATION.HASH_MISMATCH, BUDGET.ROWS_EXCEEDED, BUDGET.TIME_EXCEEDED, RUNTIME.ABORTED, PLAN.HASH_MISMATCH, CONTRACT.MARKER_MISSING, PN-RUN-3001, PN-RUN-3002, PN-RUN-3030, PN-MIG-2001, PN-CLI-4011, PN-SCHEMA-0001, drift, capability missing, planner conflict, prisma studio, EXPLAIN, query log, db.end, db.close, script won't exit, hangs, close connection, pool.end, client is closed.
日本語の概要は準備中です。原文の説明を表示しています。
Run bounded, read-only semantic advisory sidecar passes for candidate mapping, issue triage, upstream diffs, evidence verification triage, and meta audit hints. Enforces monthly spend limits with explicit fallback to worker-luna.
日本語の概要は準備中です。原文の説明を表示しています。
Publish a new post (announcement, link, or LaTeX-style meta report) to the Gaia site. Use when you want to add any update to the registry's public feed and landing page.
日本語の概要は準備中です。原文の説明を表示しています。
Consult this skill BEFORE proposing a fix to any CLI gap or schema gap that touches evidence, trust magnitude, evidence types, evidence grades, the TM formula, or star-level promotion gates. Also read it whenever an issue mentions citations, stars, commits, contributors, views, reviewers, percentile, arxiv, github-stars-own, repo-own, social-signal, benchmark-result, peer-review, self-attestation, fusion-recipe, verifier-attestation, or proxy-containment — those are the 10 canonical evidence types and the raw inputs that feed their formulas. Also read it when asked whether a skill qualifies for a given star level (0★–6★): the Star Bar and promotion gates live in `META.md`, not in the TM methodology page. Reading both prevents proposing a calibration that satisfies the TM grade threshold but violates a Star Bar installability or link requirement.
日本語の概要は準備中です。原文の説明を表示しています。
Fuse all of a contributor's named skills into a single fusion node (suite capstone) in the registry. Use when the user says "fuse <contributor>'s skills", "create a suite for <contributor>", "build a capstone for <user>", "fuse all of <user>'s named skills", "create a suite fusion", "consolidate <contributor> into one skill", or explicitly types /gaia-fuse-full-suite. Also triggers when a contributor has accumulated 3+ named skills and the user asks what to do next with them, or when someone asks "can we make a suite from these?". This skill: collects component IDs from registry/named/<contributor>/, verifies nodes exist, researches evidence and appraises Trust Magnitude, runs `gaia dev fuse` to write the fusion node and suite manifest, validates, and opens a PR on a review/meta/ branch.
日本語の概要は準備中です。原文の説明を表示しています。
Post-review intake closing skill. After an intake is resolved (whether accepted via review/meta PR merge or rejected/deferred at triage/evidence review), run this skill to post standardized, personalized closing comments on the PR (if any) and each intake issue. Comments include: evidence pipeline findings with /trust-appraise TM output, per-row artifact scores, decisions rationale, path-to-promotion/acceptance guidance, and a mandatory badge status note including the universal Powered by Gaia badge. Use after curation completes, before or immediately after merge for accepted intakes, or immediately upon rejection.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a prioritized review queue of registry skills and catalog items that need attention. Use this skill whenever someone asks: "what needs review?", "what's overdue for audit?", "where are the weak spots in the registry?", "what should I audit next?", "run a health check on the registry", "show me flagged skills", "find problems in the registry", "what skills need fixing?", or "triage the registry". This is the triage layer — it surfaces candidates ranked P0–P4 so that focused work (via /gaia-audit) targets the right things first. Run this before any audit pass. Also invoke proactively when a PR changes registry/named/ at scale, or before a release, to catch regressions early.
日本語の概要は準備中です。原文の説明を表示しています。
Skippable Phase 0 of the Gaia evidence verification pipeline. Use only on declared need for higher-quality Stage-2 evidence: a promotion candidate, or a skill that gaia-meta-sweep flagged as under-evidenced. Given a skill id, source repo/context, and needed evidence types (benchmark-result, arxiv, peer-review, social-signal), it runs Firecrawl searches, scrapes top hits to markdown, and appends discovered sources into Phase 1 inputs. Missing benchmark evidence is recorded as benchmark-source candidates first, not direct scoring rows. Trigger phrases: "discover evidence", "find new evidence", "Phase 0", "run ev-discovery", "search for benchmarks/papers", "under-evidenced", "promotion candidate needs stronger proof". This is the ONLY ev-* skill that searches the web for NEW evidence; other ev-* skills aggregate or verify known sources. Requires Firecrawl to be usable (`firecrawl --status` authenticated OR FIRECRAWL_API_KEY set); skips gracefully when neither holds.
日本語の概要は準備中です。原文の説明を表示しています。
Phase 5 of the feature-pipeline suite. Use this after /fp-iterate prints the M4 stop hook confirming CI is green. Fetches origin/main, runs gaia dev diff to surface any skill-registry changes the PR introduced that are unrelated to its stated purpose (accidental drift), then prints the final pipeline summary including a CI churn report (via /ci-churn). Also invoke standalone whenever you want to audit whether a branch has unexpected registry drift — e.g. before merging any review/meta or cli/ branch, or when a reviewer asks "did this PR touch anything it shouldn't?". Triggers: "check for drift", "drift check", "final summary", "pipeline done", "wrap up the pipeline", "fp-drift", "Phase 5".
日本語の概要は準備中です。原文の説明を表示しています。
Generate one or more standalone Meta image-ad creatives via ChatGPT Image 2 (gpt-image-2) through the Novoads API. Locks the model, auto-strips platform chrome, enforces edge-safe layouts and glyph-safety inside body text. Use when the user asks for a "gpt-image-2 ad", "ChatGPT Image ad", "Image 2 ad creative", "make a static image ad with GPT", or anchors on a need for typography-heavy / dense-text / UI-mimicry ad creatives (chat threads, comparison tables, fake search results, iOS dialogs, Slack snapshots, ChatGPT-conversation ads, Apple Notes lists). Does NOT trigger on Nano Banana cues — use nano-banana-image-ad for those.
日本語の概要は準備中です。原文の説明を表示しています。
Generate one or more standalone Meta image-ad creatives via Nano Banana Pro through the Novoads API. Locks the model, auto-strips platform chrome, enforces edge-safe layouts. Use when the user asks for a "Nano Banana ad", "Gemini image ad", "nano-banana-pro ad creative", "make a static image ad with Gemini", or anchors on a need for photoreal / lifestyle / multi-reference / handheld-object / clay-texture ad creatives (sticky-note flatlays, held-whiteboard signs, lifestyle portraits, ingredient collages, OOH photography). Does NOT trigger on ChatGPT Image cues — use chatgpt-image-ad for those.
日本語の概要は準備中です。原文の説明を表示しています。
Strip workflow notes, engineering meta text, status remarks, workspace references, and other process-facing language from any final deliverable such as a PPT, DOCX, PDF, report, manuscript, or submission package. Use when preparing a final export, submission-ready artifact, or client-facing handoff.
日本語の概要は準備中です。原文の説明を表示しています。
Captures and analyzes malware network traffic from a detonation: extracting C2 endpoints, HTTP/DNS patterns, TLS metadata (JA3/SNI), and beaconing from a PCAP to build network IOCs and detection. Activates for requests to analyze malware PCAP, extract C2 from traffic, or study network behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Generate and maintain browser demos of Pulp audio plugins (both web ABIs — WAM and WCLAP) from one declarative config, so every demo mounts the SAME shared player and the two ABIs stay in lockstep. Invoke it whenever you publish/update a browser demo of a Pulp plugin, add a plugin to a demo gallery, stand up a new gallery, or touch demo pages/hosting. It runs a deterministic generator (config → stamped WAM+WCLAP site + owned-files manifest) and a blocking validator (config schema, cross-origin-isolation coverage, OG metadata, regeneration ownership). Customization is declarative config in <repo>/.pulp-web-demo/config.json (schema bundled) plus at most two typed module seams; the shared player (pinned @danielraffel/web-player) holds all UX behavior and is never vendored. Works in Claude and Codex.
日本語の概要は準備中です。原文の説明を表示しています。
EPUB ebook creation and processing — structure, metadata, validation — use when generating or parsing ebooks.
日本語の概要は準備中です。原文の説明を表示しています。
Building robust document ingestion — chunking, metadata, and multi-format pipelines for search and RAG.
日本語の概要は準備中です。原文の説明を表示しています。
Build with Meta's Code Llama — open code models for generation, infilling, and long-context code tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews game audio code for Wwise/FMOD integration safety, custom DSP plugin correctness, and audio middleware usage. Use when the user asks to review a Wwise plugin, check an FMOD DSP effect, audit game audio middleware integration, or asks "is my game audio code safe?". Trigger on phrases like "review my Wwise plugin", "check FMOD DSP effect", "is my game audio code safe", "review my audio middleware integration", or when you see AkPluginInfo, FMOD_DSP_DESCRIPTION, IMetaSoundSource, or Execute/process callbacks in game audio code.
日本語の概要は準備中です。原文の説明を表示しています。
Meta-orchestrator — dispatches to the right skill for the task. Use before any non-trivial work.
日本語の概要は準備中です。原文の説明を表示しています。
Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness.
日本語の概要は準備中です。原文の説明を表示しています。