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

obsidian-attachment-janitorObsidian attachment janitor 搜索

Agent Skill

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

总安装

275

周安装

11

GitHub Stars

公开资料未说明

下载量

89
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/plimeor/agent-skills --skill obsidian-attachment-janitor

简介

用于查找、检索和筛选 Obsidian attachment janitor 相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。

  • 适用于需要根据关键词或任务场景从来源线索中筛选相关信息的场景。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装并使用。
  • 安装前建议确认权限范围和维护状态,注意可能触发联网或文件读写操作。
  • obsidian-attachment-janitor 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Obsidian Attachment Janitor

Clean up and organize attachments in the Obsidian vault. Two jobs:

  1. Find and delete unreferenced attachments
  2. Rename referenced attachments with consistent, searchable names

Naming convention

YYYY-MM-DD description.ext
  • Date prefix: from the referencing note's filename. Extract the YYYY-MM-DD portion only (ignore time like 1230 in 2026-03-09 1230...)
  • Description: short English kebab-case phrase describing what the attachment is, based on the embedding context in the note. Keep it under 5 words.
  • Extension: preserved from original

When the same note embeds multiple attachments, differentiate by what each one depicts, not by index number. Read the surrounding text to understand each attachment's role.

Example — a blog post note 2026-03-09 1230 让 AI 接管笔记维护.md embeds 4 images:

OriginalNew
Gemini_Generated_Image_5tv8tg5tv8tg5tv8.png2026-03-09 ai-note-maintenance-cover.png
Gemini_Generated_Image_fdvb4qfdvb4qfdvb.png2026-03-09 agent-system-overview.png
CleanShot 2026-03-09 at 20.40.27@2x.png2026-03-09 pr-diff-screenshot.png
CleanShot 2026-03-10 at 23.45.40@2x.png2026-03-10 sentinel-report-screenshot.png

Notice the last one uses 2026-03-10 — the date comes from the attachment's own CleanShot timestamp when it differs from the note date and is clearly identifiable. Prefer the note's date when in doubt.

Workflow

Step 1: Build reference map

  1. List all files in Attachments/
  2. Search all .md files for ![[filename]] embeds

- Exclude .agents/skills/ — documentation examples, not real references - Strip parameters: ![[file.png|300]]file.png, ![[file.png|alt text]]file.png

  1. Result: a map of attachment filename → [referencing note paths]

Step 2: Classify

  • Unreferenced: zero references → candidate for deletion
  • Referenced, datable: referencing note has YYYY-MM-DD in filename → candidate for rename
  • Referenced, undatable: referencing note has no date prefix (e.g., Private/Career/Portfolio/ notes) → skip rename, keep as-is

Step 3: Generate rename plan

For each datable attachment:

  1. Read the referencing note to understand the embedding context
  2. Extract YYYY-MM-DD from the note filename
  3. Generate a descriptive English kebab-case name
  4. Check for naming collisions — if two files would get the same name, make descriptions more specific rather than adding numbers

Skip if the attachment already matches the convention.

Step 4: Present plan

Show the user three lists:

  1. Delete — unreferenced attachments with file sizes
  2. Renamecurrent name → new name with the referencing note for context
  3. Skip — attachments kept as-is with reason (undatable, already named well, etc.)

Wait for explicit user confirmation before executing anything.

Step 5: Execute

Use the Obsidian CLI for both operations — it handles reference updates automatically.

For deletions:

obsidian delete path="Attachments/filename.png" permanent

For renames:

obsidian rename path="Attachments/old-name.png" name="new-name.png"

Always use path= instead of file= — the file= parameter resolves like a wikilink and fails on filenames with special characters (spaces, @, underscores, hashes).

Step 6: Verify

Run a quick scan to confirm no broken embed references were introduced. Report summary: X deleted, Y renamed, Z skipped.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

36.56%
按下载量换算33

Claude

27.19%
按下载量换算24

Cursor

18.37%
按下载量换算16

Gemini CLI

9.67%
按下载量换算9

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills