context-engine

349

Context Engine Ai Context Engine Context Engine

Hybrid semantic/lexical code search with neural reranking via MCP tools. Use when Codex needs to search a codebase, find implementations, understand how code works, find callers/definitions, search git history, or store/retrieve knowledge. IMPORTANT - Always prefer these MCP tools over grep/find/cat for code exploration.

lexical-workbench

97

nodetec

Guide for working with the Lexical editor codebase and docs in docs/lexical. Use when implementing or debugging Lexical features: editor state, updates/selection, commands, nodes/serialization, plugins, extensions, transforms, React integration, or theming, especially when the task requires consulting Lexical documentation or source structure in this repo.

memex-search

72

nicosuave

Search, filter, and retrieve Claude/Codex history indexed by the memex CLI. Use when the user wants to index history, run lexical/semantic/hybrid search, fetch full transcripts, or produce LLM-friendly JSON output for RAG.

upgrade-lexical

50

dossierhq

Incrementally upgrade Lexical dependencies and sync copied playground code

Emacs Lisp

15

jkitchin

Expert guidance for writing professional Emacs Lisp code following the community-driven Emacs Lisp Style Guide by Bozhidar Batsov. Covers layout, naming conventions, syntax preferences, macros, documentation, and best practices. Use this skill when writing Emacs configuration, creating Emacs packages, writing interactive commands, developing major/minor modes, or refactoring Emacs Lisp code. Emphasizes: lexical binding, proper naming, documentation standards, autoloading, and community conventions.

LEXICAL ANALYSIS

13

sddevelopment-be

Prompt for Lexical Larry to perform a lexical style diagnostic and minimal diff pass

EDITOR REVISION

13

sddevelopment-be

Prompt for Editor Eddy to revise a draft document using lexical analysis artifacts

mongodb-search

9

romiluz13

MongoDB Search engine architecture, query composition, and search operations. Use when creating Atlas Search indexes, writing $search or $searchMeta pipelines, choosing analyzers, tuning lexical relevance, handling Search alerts/metrics, deploying Search in Community, or orchestrating hybrid search with $rankFusion/$scoreFusion. Triggers on "Atlas Search", "$search", "$searchMeta", "autocomplete", "synonyms", "facet", "compound", "search score", "highlight", "storedSource", "returnStoredSource", "returnScope", "mongot", "searchCoordinator", "Search Max Fields Indexed", "nGram fields", "$rankFusion", "$scoreFusion", and "hybrid search".

mongodb-ai

9

romiluz13

MongoDB Atlas Vector Search and AI integration. Use when creating vector indexes, writing $vectorSearch queries, building RAG applications, implementing hybrid search, or storing AI agent memory. Triggers on "vector search", "vector index", "$vectorSearch", "embedding", "semantic search", "RAG", "retrieval augmented generation", "numCandidates", "similarity search", "cosine similarity", "hybrid search", "$rankFusion", "$scoreFusion", "rerank", "two-stage retrieval", "AI agent", "LLM memory", "quantization", "multi-tenant", "Search Nodes", "explain vectorsearch", "HNSW", "automated embedding", "autoEmbed", "Voyage AI", "voyage-4", "voyage-4-large", "voyage-code-3", "input_type", "asymmetric retrieval", "lexical prefilter", "fuzzy search vector", "phrase filter".

payload

6

b-open-io

This skill should be used when the user asks to "create a post", "edit a post", "update post content", "list posts", "convert markdown to Lexical", "write article to Payload", or mentions Payload CMS content management. Handles both production and local Payload sites via REST API with authentication.

refactor-lexical-ontology

6

JordanGunn

Audit identifiers and namespaces for lexical-semantic and ontological correctness. Detect semantic role misalignment (agent/tool/process/artifact), derivational misuse (e.g., -er agent nouns), and category errors between modules, packages, classes, functions, and data artifacts. Output a single Markdown report with actionable fixes.

audit-lexical-ontology

2

itsAR-VR

Audit identifiers and namespaces for lexical-semantic and ontological correctness; output a Markdown report with actionable fixes.

scry-people-finder

ExoPriors

Use ExoPriors Scry (SQL + lexical + embeddings + optional rerank) to help a human find people worth talking to, based on their interests/values/needs. Use when the task involves: finding people, who should I talk to, networking, people search, person recommendation, expert discovery, outreach targets. NOT for: cross-platform identity resolution without a search goal (use people-graph), academic author lookups (use openalex), or general corpus search (use scry).

tutorial

ExoPriors

Interactive guided tutorial for ExoPriors/Scry. Walks a human+agent pair through their first Scry session: schema discovery, lexical search, semantic embedding, LLM reranking, artifact sharing, and structured judgements. Use when the user says: "getting started with Scry", "walk me through Scry", "Scry tutorial", "learn to use ExoPriors", or invokes /tutorial. NOT for: users who already know Scry and want to run queries (use scry), or users who need a specific research pipeline (use research-workflow).

scry

ExoPriors

Query the ExoPriors Scry API -- SQL-over-HTTPS search across 229M+ entities spanning forums, papers, social media, government records, and prediction markets. Use when the task involves: Scry API, ExoPriors, /v1/scry/query, scry.search, scry.entities, materialized views, corpus search, epistemic infrastructure, 229M entities, lexical search, BM25, structured agent judgements, scry shares, cross-corpus analysis. NOT for: semantic/vector search composition or embedding algebra (use vector-composition), LLM-based reranking (use rerank), cross-platform people graph traversal (use people-graph), OpenAlex academic helpers (use openalex), or the user's own local Postgres / non-ExoPriors data sources.