Agent skill

Product Full-Text Search

by lobehub in lobehub/lobehub

Guides work on LobeHub's own product search: the shared search repository, provider choice, Elasticsearch mappings, change syncing and reindexing.

Custom licenceAuto-check passedBackend & APIs

Install Product Full-Text Search

skills CLI
$ npx skills add lobehub/lobehub --skill full-text-search -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install lobehub/lobehub full-text-search --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/lobehub/lobehub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/full-text-search .claude/skills/full-text-search && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
full-text-search
GitHub stars
83k
Token cost
~4.1k tokens
SKILL.md length
1,933 words
Files
2 (incl. references)
Skills in repo
50
Repo updated
First seen
Licence
Custom licence

At a glance

Guides work on LobeHub's own product search: the shared search repository, provider choice, Elasticsearch mappings, change syncing and reindexing.

  • Works in 6 steps: FTS_SEARCH_DOCUMENT_ENTITIES and shared… → Search document schema, mapping, text… → FtsSearchDocumentBuilder, including soft… → …
  • Adding a searchable entity or field to LobeHub's product search
  • SKILL.md covers Architecture, Provider and Permission…, Changing a Searchable Entity and Capture, Reindex, and Sync, plus 3 more sections
  • Calls bun

What it does

The scope is search over data that LobeHub itself stores, such as agents, topics, messages, files, knowledge bases, documents, chat groups and memories. Web search providers that an agent calls at run time are out of scope. Searches follow one path: routers and services call `createFtsSearchRepo`, which returns an `FtsSearchRepo` that talks to the selected backend and keeps the existing result shapes.

Each part of the stack has a named owner. A server service picks the provider per request and holds the Elasticsearch client, the database package holds the PostgreSQL and Elasticsearch repositories plus document mappings, and a sync outbox captures changes with claims, retries, dead letters and revision fences. A resumable script handles full reindexing. `FTS_SEARCH_PROVIDER` selects `pg_search`, `elasticsearch` or `pg_like` per deployment, and provider errors must surface instead of silently falling back. A reference file covers Elasticsearch mapping migrations.

When your agent uses it

  • Adding a searchable entity or field to LobeHub's product search
  • Changing an Elasticsearch mapping and planning its migration
  • Debugging missing or stale results caused by the search sync outbox
  • Choosing or adding a provider behind the search repository

Example prompts

  • “Add the knowledge base description field to the Elasticsearch document mapping and plan the migration.”
  • “New messages are missing from search results. Check whether the sync outbox has dead letters.”
  • “Add a new value for FTS_SEARCH_PROVIDER and make sure it covers every searchable entity.”

Requirements

  • The LobeHub repository

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. FTS_SEARCH_DOCUMENT_ENTITIES and shared request/result types.
  2. Search document schema, mapping, text fields, filters, fixtures, and mapping parity tests.
  3. FtsSearchDocumentBuilder, including soft deletion and fanout from related source rows.
  4. PostgreSQL and Elasticsearch backend behavior, permission hydration, pagination, and ranking.
  5. Capture functions/triggers or fanout queries in captureInfrastructure.ts.
  6. Reindex checkpoints, Outbox draining, metrics, and self-host documentation.

What it can do on your machine

Read from SKILL.md and the folder at commit 1e86647. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bun

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Product Full-Text Search loads about 4.1k tokens when it runs, and up to ~7.7k if it reads all its reference files. Until then it costs about 47 tokens; SKILL.md has 1,933 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~47
When it runs · the whole SKILL.md, loaded when a task matches
~4.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,933 words (~4,084 tokens).

“This skill covers search over LobeHub-owned product data such as agents, topics, messages, files, knowledge bases, documents, chat groups, and memories. It does not cover the agent's external web search providers under apps/server/src/services/search/ or builtin web-browsing tools.”

— opening of SKILL.md by lobehub, Custom licence
name
full-text-search

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file (references) in .agents/skills/full-text-search of lobehub/lobehub.

  • SKILL.md
  • references/mapping-migrations.md

Open the folder on GitHubat commit 1e86647

Compare with similar skills

Product Full-Text Search next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Product Full-Text Search compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Product Full-Text Search this skilllobehub/lobehub83k—~4.1kAutomated safety check: PassCustom licence
Detecting Debug Endpointsjeremylongshore/tons-of-skills-marketplace2.8k—~2kAutomated safety check: PassMIT
Whodbxiaoyuge886/aigc198—~894Automated safety check: PassMIT
cmux Backend Rulesmanaflow-ai/cmux28k1 repos~682Automated safety check: PassCustom licence
Geoflowyaojingang/GEOFlow3.8k—~722Automated safety check: PassAGPL-3.0
Backend Guidelightly-ai/lightly-studio896—~1.2kAutomated safety check: PassApache-2.0

Similar skills

  • Detecting Debug Endpoints

    jeremylongshore/tons-of-skills-marketplace

    Probe a target for accidentally-public admin / debug / introspection endpoints — Spring Boot Actuator, Apache server-status, Prometheus metrics, GraphQL playground, Swagger UI, phpMyAdmin…

    2.8k GitHub stars~2k tokensUpdated today
    Backend & APIsAuto-check passed
  • Whodb

    xiaoyuge886/aigc

    Database operations including querying, schema exploration, and data analysis.

    198 GitHub stars~894 tokensUpdated 2 mo ago
    DatabasesAuto-check passed
  • cmux Backend Rules

    manaflow-ai/cmux

    Sets the backend TypeScript and Cloud VM rules for cmux: Effect-based services, thin route handlers, Postgres as source of truth, migrations and provider secrets.

    28k GitHub starsUsed in 1 repo~682 tokens
    Backend & APIsAuto-check passed
  • Geoflow

    yaojingang/GEOFlow

    Operate/develop GEOFlow CLI/Laravel/admin/API, topics/专题 and topic tasks, theme libraries/replication, sites/leads/Agent, channel sync and legacy yao-geoflow-cli/design/template migration.

    3.8k GitHub stars~722 tokensUpdated 2 days ago
    Backend & APIsAuto-check passed
  • Backend Guide

    lightly-ai/lightly-studio

    Read before adding or changing backend code in lightlystudio - FastAPI routes, services, resolvers, SQLModel tables, or database access.

    896 GitHub stars~1.2k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Backend Dev Guidelines

    litefuse/litefuse

    Comprehensive backend development guide for Litefuse's Next.js 14/tRPC/Express/TypeScript monorepo.

    101 GitHub starsUsed in 1 repo~5.8k tokens
    Backend & APIsAuto-check passed

More from lobehub/lobehub

All 50 skills in this repo
  • Builds single-file interactive HTML prototypes rendered with the real LobeHub UI components and written as production-style React, so they can later be split into files.

    83k GitHub stars~1.6k tokensUpdated today
    Auto-check passed
  • Verifies a delivery end to end by driving the real product on a CLI, web, desktop or iOS Simulator surface, capturing evidence and publishing a round with the lh CLI.

    83k GitHub stars~9.7k tokensUpdated today
    Auto-check passed
  • Git Worktree Cleanup

    lobehub/lobehub

    Audits stale Git worktrees and branches with a bundled script, classifies each one, and deletes only after you approve the exact candidates.

    83k GitHub stars~2.8k tokensUpdated today
    Auto-check passed
  • Maintains LobeHub's model-backed alint rule set: writing rules, removing false positives against real code, deciding warn versus error and tracking token cost.

    83k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Guides building LobeHub builtin agent tools, from the manifest and execution runtime to executors, chat UI renders and registry wiring.

    83k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Explains how LobeHub client code fetches data through services, SWR store hooks and cache keys, and when to avoid useEffect fetching or duplicated state.

    83k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

Questions about Product Full-Text Search

What does Product Full-Text Search do?

Guides work on LobeHub's own product search: the shared search repository, provider choice, Elasticsearch mappings, change syncing and reindexing. The scope is search over data that LobeHub itself stores, such as agents, topics, messages, files, knowledge bases, documents, chat groups and memories. Web search providers that an agent calls at run time are out of scope.

When should I use Product Full-Text Search?

Product Full-Text Search fits situations like: adding a searchable entity or field to LobeHub's product search; changing an Elasticsearch mapping and planning its migration; debugging missing or stale results caused by the search sync outbox; choosing or adding a provider behind the search repository.

How do I install Product Full-Text Search in Claude Code?

Run `npx skills add lobehub/lobehub --skill full-text-search -a claude-code`. Or copy the skill folder (.agents/skills/full-text-search in lobehub/lobehub) into .claude/skills/full-text-search in your project. Claude Code loads it when a task matches its description.

How do I install Product Full-Text Search in Codex?

Run `npx skills add lobehub/lobehub --skill full-text-search -a codex`. Or copy the skill folder (.agents/skills/full-text-search in lobehub/lobehub) into .agents/skills/full-text-search in your project. Codex loads it when a task matches its description.

Can I use Product Full-Text Search in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add lobehub/lobehub --skill full-text-search -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/full-text-search, .gemini/skills/full-text-search, .github/skills/full-text-search and .opencode/skills/full-text-search in your project.

What does Product Full-Text Search need to run?

Going by SKILL.md and its folder, Product Full-Text Search needs the command-line tools its instructions call (bun). Our summary lists: The LobeHub repository.

Does Product Full-Text Search access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Product Full-Text Search safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Product Full-Text Search use?

Product Full-Text Search has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Product Full-Text Search use?

About 4.1k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.6k tokens, read only when the agent opens those files.

What are the alternatives to Product Full-Text Search?

Skills that share tags, products or a category with Product Full-Text Search: Detecting Debug Endpoints (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Whodb (xiaoyuge886/aigc, 198 stars), cmux Backend Rules (manaflow-ai/cmux, 28k stars) and Geoflow (yaojingang/GEOFlow, 3.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Product Full-Text Search?

lobehub (a GitHub organization) maintains it in lobehub/lobehub, which has 83,095 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 10, 2026.

Source: lobehub/lobehub on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.