Skip to content
Back to skills

Search

ASecurity

PRIMARY tool for gathering context. Search tasks before any action.

  • 83 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 24, 2026
ai-agentsgobashperformance

Security analysis

A100/100

Scanned October 24, 2026

npx -y skills add obsfx/trekker --skill search --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Search?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Search
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/obsfx-search/badge)](https://www.skillsdirectory.com/skills/obsfx-search)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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

# 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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.