How do I install the Semble skill?

Run npx get-skill add minishlab/semble in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Semble safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Semble?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Semble free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Semble?

MinishLab (@minishlab) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Semble by minishlab — Agent Skill

Name: Semble
Rating: 4.2 (5 reviews)
Author: MinishLab

Semble

Code search for the current repository. Use this before Grep, Glob or find whenever you need to locate code, such as where something is implemented, which file defines a function, class or symbol, how a feature works, or where docs and config live.

MinishLab Updated Nov 11, 2026

File contents

Use semble search to find code by describing what it does or naming a symbol/identifier, instead of grep:

semble search "authentication flow" ./my-project --max-snippet-lines 10  # first 10 lines only, concise
semble search "save_pretrained" ./my-project                          # full chunk content
semble search "save model to disk" ./my-project --top-k 10           # more results

Results are cached automatically on first run and invalidated when files change.

Use --content docs to search documentation and prose, --content config for config files (yaml, toml, etc.), or --content all to search code, docs, and config:

semble search "deployment guide" ./my-project --content docs
semble search "database host port" ./my-project --content config
semble search "authentication" ./my-project --content all

Use semble find-related to discover code similar to a known location (pass file_path and line from a prior search result):

semble find-related src/auth.py 42 ./my-project

path defaults to the current directory when omitted; git URLs are accepted. Pass several paths or URLs to search related repos together, e.g. when this project calls a service defined in a sibling repo. Result paths are then prefixed with the repo name and the output includes a repos map from prefix to location:

semble search "invoice endpoint" ./service-a ../service-b

If semble is not on $PATH, use uvx --from "semble[mcp]" semble in its place.

Workflow

Start with semble search to find relevant chunks. The index is built and cached automatically.
Use --content docs for documentation, --content config for config files, or --content all for everything.
Navigate directly to the returned file and line. Do not re-search or grep for the same content.
Optionally use semble find-related with a promising result's file_path and line to discover related implementations.
If the answer may live in a dependent or sibling repo, pass all relevant repo paths to one semble search call.
Use grep only when you need every occurrence of a literal string across the whole repo (e.g., all callers of a renamed function).

---name: sembledescription: Code search for the current repository. Use this before Grep, Glob or find whenever you need to locate code, such as where something is implemented, which file defines a function, class or symbol, how a feature works, or where docs and config live.metadata: source: https://skillmd.com/skills/minishlab/semble---Use `semble search` to find code by describing what it does or naming a symbol/identifier, instead of grep:```bashsemble search "authentication flow" ./my-project --max-snippet-lines 10 # first 10 lines only, concisesemble search "save_pretrained" ./my-project # full chunk contentsemble search "save model to disk" ./my-project --top-k 10 # more results```Results are cached automatically on first run and invalidated when files change.Use `--content docs` to search documentation and prose, `--content config` for config files (yaml, toml, etc.), or `--content all` to search code, docs, and config:```bashsemble search "deployment guide" ./my-project --content docssemble search "database host port" ./my-project --content configsemble search "authentication" ./my-project --content all```Use `semble find-related` to discover code similar to a known location (pass `file_path` and `line` from a prior search result):```bashsemble find-related src/auth.py 42 ./my-project````path` defaults to the current directory when omitted; git URLs are accepted. Pass several paths or URLs to search related repos together, e.g. when this project calls a service defined in a sibling repo. Result paths are then prefixed with the repo name and the output includes a `repos` map from prefix to location:```bashsemble search "invoice endpoint" ./service-a ../service-b```If `semble` is not on `$PATH`, use `uvx --from "semble[mcp]" semble` in its place.### Workflow1. Start with `semble search` to find relevant chunks. The index is built and cached automatically.2. Use `--content docs` for documentation, `--content config` for config files, or `--content all` for everything.3. Navigate directly to the returned file and line. Do not re-search or grep for the same content.4. Optionally use `semble find-related` with a promising result's `file_path` and `line` to discover related implementations.5. If the answer may live in a dependent or sibling repo, pass all relevant repo paths to one `semble search` call.6. Use grep only when you need every occurrence of a literal string across the whole repo (e.g., all callers of a renamed function).

Frequently asked questions