search
name: search
What this skill does
name: search description: PRIMARY tool for gathering context. Search tasks before any action. ## CRITICAL: Use This First **Search is your PRIMARY tool for gathering context.** Before starting ANY work: ```bash trekker search "<single keyword>" ``` This finds related past work using FTS5 full-text search. ## IMPORTANT: FTS5 is NOT Semantic Search Trekker uses FTS5 full-text search, NOT semantic/AI search. This means: - **Use single, specific keywords** - not phrases or sentences - **Multi-word queries use AND logic** - `"fix authentication bug"` requires ALL three words present, returning FEWER results - **Search multiple times** with different keywords for broader coverage - **Pick the most distinctive word** from what you're looking for | BAD (too many words) | GOOD (single keyword) | |----------------------|-----------------------| | `trekker search "fix login authentication bug"` | `trekker search "authentication"` | | `trekker search "user cannot access account"` | `trekker search "account"` | | `trekker search "performance optimization slow"` | `trekker search "performance"` | | `trekker search "deployment pipeline issues"` | `trekker search "deployment"` | ## When to Use (ALWAYS) - **Before creating tasks** - find existing work - **Before starting work** - gather context - **When investigating issues** - find related bugs - **When user describes problem** - understand history - **When resuming work** - recover context ## Commands ```bash # Search with a single keyword trekker search "authentication" # Try multiple keywords separately for broader coverage trekker search "login" trekker search "password" # Filter by type trekker search "deployment" --type task # Filter by status trekker search "memory" --status todo,in_progress # Rebuild index if needed trekker search "caching" --rebuild-index ``` ## Workflow: Before ANY Task Operation ``` 1. SEARCH: trekker search "<single keyword>" 2. BROADEN: Try 2-3 related keywords if first search has no results 3. REVIEW: Check if similar work exists 4. DECIDE: Update existing OR create new 5. SYNC: Mirror to TodoWrite after Trekker ``` ## Trekker is Primary Remember: Trekker is the source of truth. - Search Trekker FIRST - Create in Trekker FIRST - Then mirror to TodoWrite
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.