ogrep
Semantic code search - finds code by meaning, not just keywords. Use when: - User asks WHERE or HOW something is implemented ("where is X handled", "how does Y work") - You need to understand code behavior without knowing exact function names - Exploring unfamiliar codebases where you don't know the terminology yet - User asks a conceptual question about the codebase NOT for: exact string matching, known file paths, import lookups, or simple identifier searches — use grep/Glob for those.
What this skill does
## Mandatory: Use the Search Agent **YOU MUST dispatch the ogrep-search agent for any semantic code search.** Announce: "Dispatching ogrep search agent to find [topic]." Then use the Agent tool with `subagent_type: "ogrep-search"`: ``` Agent tool: description: "Search codebase for [topic]" prompt: "Search for [specific query]. Focus on [what you're looking for - e.g., implementation details, architecture, data flow, error handling]." subagent_type: "ogrep-search" ``` The agent will: 1. Call `ogrep_query(summarize=true)` for a cheap file-level overview 2. Narrow to the most relevant files 3. Expand specific chunks for evidence 4. Return synthesized findings with file:line references **Saves context vs. running ogrep commands directly in your conversation.** ## When to Use **Use ogrep when:** - "Where is error handling done?" - "How does caching work here?" - "What validates user input?" - Exploring unfamiliar code - User asks a conceptual question about the codebase - You'd need to guess multiple terms for grep **Use grep/Glob instead when:** - You know the exact class/function name (`class ErrorHandler`) - Looking for specific imports or string literals - Simple identifier searches **Rule of thumb:** If you'd need to guess multiple terms for grep, dispatch the ogrep agent. ## Direct MCP Access (Simple Queries) For simple, quick lookups you CAN call MCP tools directly without dispatching the agent: ``` ogrep_query(query="where is auth?") ogrep_status() ``` This is appropriate for quick checks. For deeper exploration, always dispatch the agent. ## Direct CLI Access (Discouraged) You CAN run `ogrep` commands directly via Bash, but DON'T — MCP tools are faster (persistent process, warm models) and return structured data. Always prefer MCP tools or the agent. Exception: `ogrep index .` for first-time indexing can be run directly if the agent reports no index exists, or use `ogrep_index()` via MCP.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.