gety-local-search

This skill should be used when the user wants to search for local files or documents on their computer. Trigger phrases include "帮我找文件", "搜索本地文件", "查找文档", "本...

Security Scan

The skill's instructions match a local-file-search purpose (it calls a 'gety' CLI), but metadata lacks provenance and fails to declare the required external CLI or installation steps — the mismatch and unknown source warrant caution.

Purpose & Capability

SKILL.md describes a local-search skill that operates by invoking a 'gety' CLI — this is coherent with the stated purpose. However the skill metadata does not declare the gety binary as a required dependency, provides no homepage/source, and includes no install instructions; those omissions reduce provenance and make it unclear how the CLI will be obtained or whether it is trustworthy.

Instruction Scope

Runtime instructions stay within the stated scope: list connectors, run search, fetch document content, handle exit codes. They implicitly instruct the agent to run shell CLI commands that will access local indexed files and to add connectors (directories). The instructions do not direct data to external endpoints or request unrelated environment variables, but adding connectors can expose arbitrary filesystem paths to the search engine — the agent will therefore potentially read local content as intended.

Install Mechanism

This is an instruction-only skill with no install spec. That is low risk for disk writes by the skill itself, but the skill assumes an external 'gety' CLI is present and running. Because there is no source/homepage or guidance for obtaining a trusted binary, users may need to install software from an unknown origin — this is a provenance concern rather than direct code-injection from the skill.

Credentials

The skill requests no environment variables, credentials, or config paths. That is proportionate to its purpose. Note that the CLI operations will access local files (as expected) but no extra secrets or unrelated credentials are being requested by the skill itself.

Persistence & Privilege

The skill does not request always:true or other elevated persistence. It's user-invocable and allows normal autonomous invocation. It does not modify other skills or system configuration in the provided instructions.

What to consider before installing

This skill is a thin wrapper for the third-party 'gety' CLI. Before installing/using it: 1) Verify where the gety binary comes from (official site, package repo) and that you trust that source — the skill metadata does not provide a homepage or install instructions. 2) If you must install gety, prefer official release channels and inspect the binary/package. 3) Be cautious when adding connectors: avoid indexing sensitive directories (password stores, SSH keys, system configs) unless you understand how gety stores and secures indexed data. 4) If you want the agent to run searches, consider running initial gety commands yourself to confirm expected output and exit codes. 5) If provenance cannot be established, do not install or run the CLI — the skill otherwise behaves as described but relies on external software of unknown trustworthiness.

Overview

To search local files and documents indexed by Gety, use the gety CLI. Gety is an AI-powered local file search engine that supports semantic search across all indexed content on the user's machine.

Quick Start

To perform a basic search:

gety search "<query>"

To get structured JSON output (useful for further processing):

gety search "<query>" --json

Core Operations

Searching Documents

To search indexed content, use gety search with the user's query. Key options:

Option	Description
-n, --limit <n>	Max results to return (default: 10)
--offset <n>	Pagination offset (default: 0)
-c, --connector <name>	Filter by connector name (repeatable or comma-separated)
-e, --ext <ext>	Filter by file extension (e.g. pdf,docx)
--match-scope <scope>	Filter by match type: title, content, semantic
--sort-by <field>	Sort by default or update_time
--sort-order <dir>	ascending or descending
--update-time-from <iso8601>	Filter by update time (from)
--update-time-to <iso8601>	Filter by update time (to)
--no-semantic-search	Disable semantic search (enabled by default)

Examples:

# Basic search
gety search "meeting notes"

# Search with more results and pagination
gety search "roadmap" -n 20 --offset 20

# Filter by connector and file type
gety search "security review" -c "Folder: Work" -e pdf,docx

# Sort by most recently updated
gety search "design system" --match-scope title,content --sort-by update_time --sort-order descending

# JSON output for processing
gety search "project plan" --json

Fetching a Specific Document

To retrieve detailed content of a specific document by its connector ID and document ID:

gety doc <connector_id> <doc_id>
gety doc <connector_id> <doc_id> --json

Managing Connectors

Connectors define which local directories Gety indexes.

# List all available connectors
gety connector list

# Add a new directory to index
gety connector add /path/to/folder --name "Folder: Work"

# Remove a connector by ID
gety connector remove folder_1

Workflow

1. Receive the user's search request — identify the query intent (file name, content topic, file type, date range, etc.)
2. Run gety connector list if unsure which connectors exist, to understand the indexed scope
3. Run gety search "<query>" with appropriate options based on the user's intent
4. Present results clearly — show file name, location, and a brief description of matched content
5. Fetch full content if needed — use gety doc <connector_id> <doc_id> when the user needs to read the document
6. Handle no-results gracefully — suggest broadening the query, checking connector coverage, or verifying the index is up to date
7. Handle exit codes — check the process exit code after each command:
   • 69: Gety is not running — ask the user to start the Gety desktop app and retry
   • 77: Quota exceeded — inform the user and suggest retrying later
   • 2: Invalid arguments — check command syntax with gety search --help
   • 1: General error — report the error message to the user
   • Full exit code reference: references/gety_cli.md

References

Full CLI documentation is available in references/gety_cli.md.