Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问clear审计通过

obsidian-linksObsidian links 搜索

Agent Skill

obsidian-links 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

524

周安装

21

GitHub Stars

43

下载量

170
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:obsidian-links(Obsidian links 搜索)
来源仓库:https://github.com/jykim/claude-obsidian-skills
仓库路径:skills/obsidian-links
安装命令:
npx skills add https://github.com/jykim/claude-obsidian-skills --skill obsidian-links
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/jykim/claude-obsidian-skills --skill obsidian-links

简介

用于查找、检索和筛选相关信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词快速定位候选结果。
  • 通过 npx 命令从指定 GitHub 仓库安装,提供链接管理功能。
  • 需确认权限范围和维护状态,避免触发不必要的联网或文件操作。
  • obsidian-links 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Obsidian Wiki Links

Format, validate, and fix wiki links according to vault conventions.

When to Use This Skill

Activate when you need to:

  • Create wiki links to other vault files
  • Add section links to specific headers
  • Format links in YAML frontmatter properties
  • Verify links point to existing files/sections
  • Find and fix broken links
  • Validate link integrity in documents

Core Link Formatting Rules

1. Complete Filename Format

Always use full filename with date prefix:

✅ CORRECT: [[2025-10-31 Project Notes]]
❌ INCORRECT: [[Project Notes]] (missing date)
❌ INCORRECT: [[2025-10-31]] (missing title)

2. Folder Path Conventions

Include folder prefix for clarity:

✅ CORRECT: [[Journal/2025-10-31]]
✅ CORRECT: [[Articles/2025-10-31 Perennial Seller]]
✅ CORRECT: [[Roundup/2025-10-31]]

Rule: Use consistent folder prefixes for clarity and navigation.

3. Section Links

Use exact header text, character-for-character:

Source file header:
## PKM System Maintenance

✅ CORRECT:
[[Journal/2025-10-31#PKM System Maintenance]]

❌ INCORRECT:
[[Journal/2025-10-31#PKM System]] (truncated)
[[Journal/2025-10-31#pkm-system-maintenance]] (slug format)

Critical: Match characters, punctuation, spacing exactly as written.

4. Link to Sources, Not Indices

Always link to original content, not topic aggregations:

✅ CORRECT: [[Articles/2025-08-15 Skill Development]]
❌ INCORRECT: [[Topics/Career#Skill Development]]

Reason: Maintains source attribution and traceability

5. Properties Link Format

Wrap links in quotes when used in YAML lists:

sources:
  - "[[Journal/2025-10-31]]"
  - "[[Articles/2025-10-31 Title]]"

links:
  - "[[Roundup/2025-10-31]]"

attendees:
  - "[[People/John]]"

Link Validation Principles

1. Search Before Link

ALWAYS verify target exists before creating link:

Process:
1. Search for target file using Glob or Grep
2. Verify file exists
3. If section link, read file and verify header exists
4. Create link with exact filename and header text

❌ NEVER:
- Guess at filenames
- Assume files exist
- Fabricate section headers

2. Verify Section Headers

For section links, read source and match exactly:

Steps:
1. Read target file
2. Search for exact header text
3. Copy character-for-character (including special characters)
4. Create section link

If unsure about exact header:
✅ Link to file only: [[Journal/2025-10-31]]
❌ Don't guess: [[Journal/2025-10-31#Guessed Header]]

3. File Existence Checking

Use appropriate tools to verify files:

For specific file:
- Use Glob with full path pattern: "Journal/2025-10-31.md"
- Or Read the file directly

For finding files by keyword:
- Use Glob with pattern: "Articles/**/*keyword*.md"
- Check Topics directory before linking to topics

4. Fix Broken Links Immediately

When you find broken links, fix them:

Process:
1. Identify broken link
2. Search for correct target file
3. Update link with correct path/filename (use Edit tool)
4. Verify section header if applicable
5. Report fix to user

Complete Workflow

Creating New Links (Format + Validate)

Step 1: Determine Target
- Identify file to link to
- Note folder location
- Note complete filename

Step 2: Verify File Exists
- Use Glob: "**/{filename}.md"
- Or Read file directly
- If not found, search by keyword

Step 3: Verify Section (if needed)
- Read target file
- Search for exact header text
- Copy character-for-character
- If unsure, link to file only

Step 4: Format Link
- Use complete filename: [[YYYY-MM-DD Title]]
- Add folder prefix
- Add section if verified: [[File#Exact Header]]
- Wrap in quotes if in YAML property

Step 5: Create Link
- Link points to existing file
- Section header matches exactly (if used)
- Follows folder prefix conventions

Finding and Fixing Broken Links

Step 1: Detection
- Read document content
- Extract all wiki links
- For each link, verify file exists
- For section links, verify header exists

Step 2: Search for Correct Target
- Use context to determine intent
- Search vault with Glob/Grep
- Verify file exists

Step 3: Fix Link
- Use Edit tool to update broken link
- Replace with correct path/filename
- Verify section header if applicable

Step 4: Report
- Show old link (broken)
- Show new link (fixed)
- Explain reason for fix

Special Cases

Journal/Daily Files

Path: Journal/YYYY-MM-DD.md
Format: [[Journal/YYYY-MM-DD]]

Section links:
- Headers may vary by language
- ALWAYS verify exact text before linking
- If unsure, link to file only

Validation:
1. Check file: Journal/YYYY-MM-DD.md
2. Read file content
3. Search for exact header
4. Use exact match or file-only link

Topic Links

CRITICAL: Search Topics directory BEFORE linking

Validation:
1. Use Glob: "Topics/**/*{keyword}*.md"
2. Find matching topic page
3. Use complete category path

Examples:
- [[Topics/Technology/PKM]]
- [[Topics/Career/Skills]]

❌ NEVER link to non-existent topic pages

Person Names

Simple name: [[John]]
With context: [[People/John]] (if folder exists)

Validation: Verify person file exists before linking

Quality Checklist

Before completing link operations:

Formatting:

  • All links use complete filenames
  • Folder prefixes follow conventions
  • Section headers match exactly (character-for-character)
  • Links in YAML properties are wrapped in quotes
  • All links point to sources, not topic indices

Validation:

  • All target files verified to exist
  • Section headers verified (not guessed)
  • Topic links point to existing topic pages
  • Broken links identified and fixed

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

30.25%
按下载量换算51

Codex

24.36%
按下载量换算41

Antigravity

19.43%
按下载量换算33

windsurf

11.79%
按下载量换算20

OpenCode

7.76%
按下载量换算13

Gemini CLI

3.38%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

继续浏览同类 Skills