What makes Linkly Ai Skills notable?

1.9K downloads. Trust evidence available

How should Linkly Ai Skills be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Linkly Ai Skills

Search, browse, read, and take notes across the user's documents indexed by Linkly AI — local files and linked cloud libraries. Use when the user asks to 'search my documents', 'find files about a topic', 'read a local document', 'what's in this folder', 'list the files in that library', 'browse doc

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.9k

Updated

Oct 9, 2026

Version

0.6.0

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.9K downloads reported by the source. Last updated 10/9/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 9, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 9, 2026
Adoption signal: 1.9K downloadsadoption · observed Oct 9, 2026
Latest release: 0.6.0release · observed Aug 10, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s175vq5g31wx4awyn86nfngmws83h4bn:linkly-ai

Install using `clawhub skill install s175vq5g31wx4awyn86nfngmws83h4bn:linkly-ai` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/linkly-ai/linkly-ai before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-linkly-ai-linkly-ai/snapshot"

Documentation

CLAWHUB

146,890 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: linkly-ai
description: "Search, browse, read, and take notes across the user's documents indexed by Linkly AI — local files and linked cloud libraries. Use when the user asks to 'search my documents', 'find files about a topic', 'read a local document', 'what's in this folder', 'list the files in that library', 'browse document outlines', 'list knowledge libraries', 'save this as a note', 'list my notes', or any task involving searching, listing, reading, or noting stored content (PDF, Markdown, DOCX, PPTX, EPUB, TXT, HTML, images, audio, video). Also triggered by: 'linkly not working', 'cloud library', '搜索我的文档', '查找文件', '这个文件夹里有什么', '列出文件', '知识库搜索', '云端知识库', '记笔记', '我的笔记', '连接不上', '故障排查'. Provides full-text search, container enumeration, structural outlines, paginated reading, and local note capture via CLI or MCP tools."
license: Apache-2.0
---

# Linkly AI — Document Search (Local + Cloud)

Linkly AI indexes documents on the user's local machine (PDF, Markdown, DOCX, PPTX, EPUB, TXT, HTML, images, audio, video) and can also reach cloud libraries the user has linked via Linkly Web. It exposes them through a progressive disclosure workflow: **search → grep or outline → read**. It can also capture and list the user's local Markdown notes.

## Environment Detection

Before executing any document operation, detect what's available and pick a mode. CLI and MCP are **two independent access paths** — check both, don't treat MCP as a CLI fallback.

### 1. Check what's available

Run both checks independently (skip a check if its prerequisite isn't there):

- **CLI**: if Bash is available, run `linkly --version`. Success → CLI is installed. Then run `linkly status` to confirm the desktop app is reachable; if the status reports a connection problem, run `linkly doctor` (see `references/troubleshooting.md`).
- **MCP**: check whether MCP tools named `search`, `find_paths`, `list`, `outline`, `grep`, `read`, `list_libraries`, `explore`, and `note_save` are accessible in the current environment. Both servers expose all nine: the `linkly-ai` server (local Desktop MCP) and the `linkly-ai-cloud` server (the `mcp.linkly.ai` cloud gateway). The difference is reach, not the tool list — see "Know what your connection reaches" below. `note_save` is the one tool whose reach never varies: it always resolves to the user's Desktop, whichever server it arrived from.

### 2. Pick a mode

| Available            | Action                                                                                                                                                                                                                                                                                                                    |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

_meta.json

{
  "ownerId": "kn7ey1znb4ay61vrkt06b8x8a1826dr7",
  "slug": "linkly-ai",
  "version": "0.6.0",
  "publishedAt": 1786364401931
}

references/cli-reference.md

# Linkly AI CLI Reference

Command-line interface for Linkly AI — search your local documents (and, over `--remote`, your linked cloud libraries) from the terminal.

The CLI connects to the Linkly AI desktop app's MCP server (locally or over LAN), or to the `mcp.linkly.ai` cloud gateway via `--remote`, giving fast access to indexed documents without leaving the terminal.

## Prerequisites

For **local** documents, the **Linkly AI desktop app** must be running with its MCP server enabled (the CLI auto-discovers it via `~/.linkly/port`). Use LAN mode (`--endpoint` + `--token`) or Remote mode (`--remote` with a saved API key) to connect over the network. Linked **cloud** libraries reached via `--remote` do not require the desktop to be online — see below.

Remote mode reaches both your local libraries and your linked cloud libraries through the `mcp.linkly.ai` gateway. Linked cloud libraries are served even when the desktop tunnel is disconnected; local / default-scope calls additionally need the desktop online and its tunnel connected. Reaching **local** content over the tunnel is a Pro feature — on a Free plan those calls return `-32000` telling you the tunnel requires Pro, while linked cloud libraries stay available on all plans.

## Installation

See the [CLI installation guide](https://linkly.ai/docs/en/use-cli) for platform-specific instructions.

## Commands

### list-libraries — List knowledge libraries

```bash
linkly list-libraries
```

Lists all knowledge libraries with document counts. Over `--remote` this includes both local libraries (`local://<id>`) and linked cloud libraries (`cloud://<owner>/<slug>`).

| Option   | Description                            |
| -------- | -------------------------------------- |
| `--json` | Output structured JSON (global option) |

### explore — Overview of indexed documents

```bash
linkly explore [OPTIONS]
```

Get a bird's-eye overview of all indexed documents or a specific library. Returns document type distribution, directory structure with file counts and median word counts, and top keywords with source attribution.

| Option             | Description                                                                                                                               |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
| `--library <name>` | Restrict overview to one library: a local name / `local://<id>`, or `cloud://<owner>/<slug>` (over `--remote`). Omit = all local content. |
| `--json`           | Output structured JSON (global option)                                                                                                    |

Examples:

```bash
linkly explore
linkly explore --library my-research
```

### find-paths — Locate folder paths

```bash
linkly find-paths --patterns <keywords> [OPTIONS]
```

Locate real folder paths in the indexed documents by fuzzy keyword

references/mcp-tools-reference.md

# Linkly AI MCP Tools Reference

The Linkly AI MCP server exposes nine tools: seven read-only document tools (`list_libraries`, `explore`, `find_paths`, `search`, `outline`, `grep`, `read`), one enumeration tool (`list`), and one write tool (`note_save`). Local documents require the Linkly AI desktop app to be running with its MCP server enabled; linked cloud libraries are served directly by the cloud gateway and stay reachable even when the desktop is offline.

**Server name:** `linkly-ai` (local Desktop MCP) or `linkly-ai-cloud` (the cloud gateway at `mcp.linkly.ai`, which exposes both your local libraries — via the desktop tunnel — and your linked cloud libraries). Both servers advertise the same nine tools.

**Notes are Desktop-only.** `note_save`, and `list` with `scope="notes"`, operate on plain Markdown files on the user's computer; there is no cloud notes store. On the cloud gateway both are forwarded to the Desktop over the tunnel — so they need the Desktop online (which over the tunnel also means Pro) and have **no cloud library to fall back on** when it is not. `note_save` has no `library` parameter at all and rejects one as an unknown field; `list` does have one, but passing it alongside `scope="notes"` is rejected.

**`list` is the one tool whose backend depends on its arguments.** `scope="folder"`, `scope="notes"` and a `local://` library are answered by the Desktop; `scope="library"` with a `cloud://owner/slug` is answered by the gateway itself — available on the Free plan, and unaffected by the Desktop being offline.

## Response Metadata

Every successful tool response carries the wallclock time so callers can compute relative dates ("last 7 days", "after July 1, 2024", "in 2024") without relying on training cutoffs:

- **Markdown** output ends with a footer block: `\n---\n[meta] now=<ISO 8601 UTC>` (e.g. `[meta] now=2026-05-07T14:43:14Z`).
- **JSON** output (`output_format: "json"`) includes a top-level `_meta` object: `{ "now": "<ISO 8601 UTC>" }`.

Errors (`isError: true`) do **not** include this metadata — the error body itself conveys the failure cause. When deriving relative dates, prefer the most recent `now` value you've seen over any other source.

## list_libraries

List all knowledge libraries available to the user. Returns **both** local libraries (cataloged on the user's Desktop) and cloud libraries (linked via Linkly Web), plus a note on the default search scope. Local libraries are addressed as `local://<library-id>`; cloud libraries as `cloud://<owner>/<slug>`. This is how you discover which cloud libraries are linked before scoping a `search` / `explore` / `find_paths` call.

### Parameters

No parameters required.

### Response

Returns a Markdown document with up to three sections — **Local libraries**, **Cloud libraries**, and **Default search scope**. Example:

```
## Local libraries

- **my-research** ("AI Research"): AI and ML papers (42 docs, 3 folders)
- **work-notes**: Daily work logs (128 docs, 1 folder

references/search-strategies.md

# Advanced Search Strategies

Linkly AI uses **BM25 + vector hybrid retrieval**. Understanding how both signals work helps you craft better queries.

## How Search Works

- **BM25 (keyword)**: Tokenizes the query (jieba for CJK, lowercase for Latin) and matches terms against title (3x boost), filename (2x), content (1x), and path (0.5x). Multiple keywords use **OR logic** — all matching documents are returned, with higher scores for documents matching more terms.
- **Vector (semantic)**: The entire query string is encoded into a single embedding vector. Documents are ranked by cosine similarity. Results with vector distance > 0.6 are filtered as noise.
- **Hybrid fusion**: Both result sets are merged using RRF (Reciprocal Rank Fusion) with equal 50/50 weighting.
- **Graceful degradation**: If the embedding model is not ready, search falls back to pure BM25.
- **Pre-search path discovery**: when the user names a container by a fuzzy / cross-language word ("in my WeChat", "在 Notion 笔记里"), `find_paths` aggregates indexed paths by keyword and returns top folder candidates — pipe one as `path_glob` to scope the subsequent `search`. See ["Locate the container first"](#locate-the-container-first-with-find_paths) below.
- **Time-aware filtering and sorting**: `search` accepts `modified_after` / `modified_before` (ISO 8601 UTC) for explicit windows and `time_sort` (`newest` / `oldest`) for relative ordering. See ["Constraining by time"](#constraining-by-time) below.

## Enforcing AND across keywords

`search` is OR-only at the BM25 level — `linkly search "auth migration"` returns documents matching `auth` **or** `migration`, ranked by overlap. When the user genuinely needs **all** terms to co-occur, chain `search` and `grep`:

```bash
# Step 1: search retrieves a candidate set scored by partial overlap.
linkly search "auth migration" --limit 30

# Step 2: grep filters that set down to docs that actually contain both.
#   `grep` takes the whole ID list, and `-` reads it from the pipe.
linkly search "auth migration" --limit 30 --json \
  | jq -r '.results[].doc_id' \
  | linkly grep "auth" - --mode count --json \
  | jq -r 'select(.total_matches > 0) | .results[].doc_id' \
  | linkly grep "migration" - --mode count --json \
  | jq -r 'select(.total_matches > 0) | .results[].doc_id'
```

Each stage emits one JSON object per document, so `jq` can drop the non-matching ones before the next `grep` ever sees them.

For a single document, `--exit-code` makes the check a plain conditional:

```bash
linkly grep "auth" "$id" --mode count --exit-code >/dev/null && echo "$id matches"
```

Without `--exit-code`, `grep` exits 0 even on zero matches (success means "the search ran"), so you would have to read the count out of the JSON yourself.

For two terms a faster shortcut is to grep one (the rarer) right after `search`, since the BM25 ranking already biases toward documents matching multiple terms — most top-N results will already satisfy AND.

## Query Crafting Stra

Github ReposUpdated 8h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.