Token导航 LogoToken导航

Agent Skill · 研究检索

tag-finder(标签查找器)

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

tag-finder 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证为 MIT,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 8,428。

总安装 16,401周安装 597GitHub Stars 公开资料未说明下载 6,356核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/zarvent/obsidian-skills --skill 'tag finder'

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

tag-finder 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于基于标签或关键词从来源线索中提取相关内容。通过 npx skills add 命令从指定 GitHub 仓库安装并使用。

建议确认权限范围和维护状态,避免触发联网或文件读写操作。可结合原始 README 进一步核验具体功能和调用方式。

来源仓库内路径:skills/tag-finder

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/zarvent/obsidian-skills --skill 'tag finder';命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

tag-finder 怎么安装?

在终端执行 npx skills add https://github.com/zarvent/obsidian-skills --skill 'tag finder'。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

tag-finder 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

tag-finder 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

tag-finder 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

tag-finder 用的人多吗?

公开数据是累计安装 16,401 次,近一周安装 597 次,下载 6,356 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

tag-finder 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
tag-finder

标签查找器 · 本页

16,401—需要联网MIT通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

ADAPTIVE HIERARCHICAL TAGGING PROTOCOL

CORE PHILOSOPHY

Tagging is reasoning, not labeling.

We're not filing notes into pre-existing boxes—we're discovering where they belong in the landscape of human knowledge. Every tag assignment is:

  • Contextual: Depends on the note's purpose and surrounding knowledge
  • Debatable: Multiple valid perspectives may exist
  • Evolving: Can change as understanding deepens
"The map is not the territory, but a well-reasoned map helps navigate the territory."

THE GOLDEN RULE: MACRO TO MICRO (Flexible Framework)

Base Format: Academic-Discipline/Sub-discipline/Specific-Topic/[Granular-Detail]

But remember: This is a guide, not a prison.

Depth Decision Matrix

ScenarioRecommended DepthReasoning
Foundational concept2 levelsPhysics/Thermodynamics — Established, well-bounded topic
Standard technical topic3 levelsComputer-Science/Algorithms/Sorting — Clear disciplinary home
Specialized methodology4 levelsBiology/Genetics/Genomics/CRISPR — Requires context chain
Emerging/hybrid concept2-3 levels + multi-tagMight not fit cleanly; err toward flexibility
Meta-topic (tools, practices)Custom structureMay need Methodology/ or Tools/ prefix

Key Principle: Depth should illuminate, not obfuscate. If a fifth level adds genuine specificity, use it. If it's just noise, stop at three.


REASONING FRAMEWORK

Before assigning tags, walk through this reasoning process:

Step 1: IDENTIFY THE NOTE'S EPISTEMIC NATURE

Ask: What kind of knowledge is this?

Knowledge TypeCharacteristicsTag Approach
Foundational ConceptDefines basic principlesRoot in primary discipline
Applied TechniqueImplements conceptsInclude methodology/application layer
Interdisciplinary BridgeConnects fieldsMulti-tag with clear primary
Tool/FrameworkEnables workMay need Methodology/ or tool-specific structure
Historical/ContextualAbout the field itselfConsider meta-level tags
Emergent/Cutting-edgeNew, not yet categorizedBe conservative; use broader tags

Example:

Note: "Transformer Architecture"

Reasoning:
- Core nature? Technical architecture (applied technique)
- Origin? Research from NLP/Deep Learning
- Current status? Foundational to modern AI
- Decision: 4-level tag to capture evolution from theory to architecture

Tag: Computer-Science/Artificial-Intelligence/Deep-Learning/Transformers

Step 2: MAP DISCIPLINARY LINEAGE

Ask: What's the intellectual ancestry?

Trace backwards from specific → general:

  1. What specific thing is this? (leaf)
  2. What broader category contains it? (branch)
  3. What field studies that category? (sub-discipline)
  4. What academic domain owns that field? (root)

Example:

Note: "CRISPR-Cas9 Ethics"

Backward trace:
1. Specific: CRISPR-Cas9 (gene-editing tool)
2. Broader: Gene editing techniques
3. Field: Genomics (within Genetics)
4. Domain: Biology

But wait—ethics layer!
→ This is interdisciplinary

Primary tag: Biology/Genetics/Genomics/CRISPR
Secondary tag: Philosophy/Ethics/Applied-Ethics/Bioethics

Reasoning: The note studies CRISPR through ethical lens, so Biology is primary (the object of study) and Ethics is secondary (the analytical framework).

Step 3: EVALUATE INTERDISCIPLINARY COMPLEXITY

Ask: Does this concept live in multiple worlds?

IndicatorAction
Concept originated in Field A but now used in Field BPrimary: Origin field / Secondary: Application field
Equal contribution from multiple fieldsMultiple co-equal tags
Field A studying Field BPrimary: Field A / Reference Field B in sub-levels
Meta-analysis across fieldsConsider Methodology/Interdisciplinary-Studies

Example:

Note: "Neural Networks for Drug Discovery"

Analysis:
- Neural Networks: CS/AI technique
- Drug Discovery: Biology/Pharmacology goal

Interdisciplinary type: Tool from Field A applied to Field B

Tags:
  - Computer-Science/Artificial-Intelligence/Machine-Learning/Neural-Networks
  - Biology/Pharmacology/Drug-Discovery

Reasoning: Primary tag reflects the technical method; secondary reflects application domain. If note focuses more on biological insights than ML technique, reverse the priority.

Step 4: ASSESS TAXONOMY MATURITY

Ask: How established is this concept?

Maturity LevelTag Strategy
Canonical (in textbooks for 20+ years)Use standard academic hierarchy
Established (widespread in journals/practice)Follow field conventions
Emerging (active research, no consensus)Use broader tags, avoid premature specificity
Speculative (blog posts, tweets, hype)Tag the underlying established concepts

Example:

Note: "GPT-4 Prompt Injection Attacks"

Maturity assessment:
- GPT-4: Very new (2023)
- Prompt Engineering: Emerging (2020s)
- Security vulnerabilities: Established

Decision: Tag using established concepts, not bleeding-edge labels

Conservative tag:
  Computer-Science/Artificial-Intelligence/Natural-Language-Processing/Security

Alternative (if focusing on prompt engineering):
  Computer-Science/Artificial-Intelligence/Prompt-Engineering

Reasoning: "Prompt injection" is too new and unstable as terminology. Anchor in established security or NLP concepts, then add emergent layer if needed.

ADAPTIVE PATTERNS

Pattern 1: THE UMBRELLA TERM PROBLEM

Scenario: Note discusses a broad concept that could be tagged at multiple specificity levels.

Example: "Introduction to Machine Learning"

Options:

# Option A: Broad (appropriate for survey/intro)
tags:
  - Computer-Science/Artificial-Intelligence/Machine-Learning

# Option B: Specific (if focusing on sub-areas)
tags:
  - Computer-Science/Artificial-Intelligence/Machine-Learning/Supervised-Learning
  - Computer-Science/Artificial-Intelligence/Machine-Learning/Unsupervised-Learning

# Option C: Meta-level (if about ML as a field)
tags:
  - Computer-Science/Artificial-Intelligence/Machine-Learning
  - Methodology/Research-Methods

Decision framework:

  • Introductory/survey content → Broader tag
  • Deep dive into specific technique → More specific tag
  • Epistemological/historical → Add meta-tag

Pattern 2: THE TOOL vs. CONCEPT DILEMMA

Scenario: Note is about a tool that implements concepts.

Example: "TensorFlow Tutorial"

Reasoning:

Is this about:
A) The software tool itself? → Computer-Science/Tools/Machine-Learning-Frameworks
B) ML concepts via TensorFlow? → Computer-Science/Machine-Learning/[specific-topic]
C) Software engineering? → Computer-Science/Software-Engineering/Libraries

Decision: Depends on note's focus
- If explaining how to install/use TensorFlow → Tools tag
- If using TensorFlow to teach neural networks → Neural-Networks tag
- If comparing frameworks → Software-Engineering tag

Pattern 3: THE HISTORICAL vs. TECHNICAL SPLIT

Scenario: Note discusses the history or sociology of a technical field.

Example: "The AI Winter of the 1980s"

Options:

# Pure historical approach
tags:
  - History/History-of-Science/Computer-Science
  - Computer-Science/Artificial-Intelligence

# Science-and-society approach
tags:
  - Sociology/Science-and-Technology-Studies
  - Computer-Science/Artificial-Intelligence

# Field-internal approach
tags:
  - Computer-Science/Artificial-Intelligence
  - Methodology/Research-History

No single right answer—choose based on the note's analytical lens.


SPECIAL CASES & EDGE CASES

Case 1: Personal Knowledge Management Notes

Example: "My System for Reading Papers"

Challenge: Not strictly academic content, but about academic practice.

Solution:

tags:
  - Methodology/Knowledge-Management/Reading-Systems
  - Methodology/Research-Methods/Literature-Review

Reasoning: Create a Methodology/ root for meta-practices. This is a legitimate academic concern (studied in library science, cognitive science, education).

Case 2: Colloquial Terms for Technical Concepts

Example: Note titled "AI Hallucinations"

Challenge: "Hallucination" is colloquial jargon for "generation errors" or "factual inconsistencies."

Solution:

tags:
  - Computer-Science/Artificial-Intelligence/Natural-Language-Processing/Model-Evaluation
  - Computer-Science/Artificial-Intelligence/Machine-Learning/Reliability

Reasoning: Tag the underlying technical concept, not the slang. Could add informal alias in note metadata.

Case 3: Compound Concepts

Example: "Quantum Machine Learning"

Analysis:

This is genuinely interdisciplinary—not just ML applied to quantum problems,
but using quantum computing principles for ML algorithms.

Options:
A) Emphasize quantum: Physics/Quantum-Computing/Applications/Machine-Learning
B) Emphasize ML: Computer-Science/Machine-Learning/Quantum-Methods
C) Both: Use multiple tags

Recommendation: Use both tags with clear reasoning about which is primary based on note content.

Case 4: Framework/Theory/Model Naming

Example: "Actor-Critic Algorithms"

Decision tree:

Is this:
- A specific algorithm? → Include algorithm name in tag path
- A class of algorithms? → Stop at category level
- A theoretical framework? → May need Theory/Framework sub-level

Result: Computer-Science/Artificial-Intelligence/Reinforcement-Learning/Actor-Critic

Reasoning: Actor-Critic is a recognized sub-category of RL algorithms,
not just a single implementation.

OUTPUT PROTOCOL

When assigning tags, provide:

1. RECOMMENDED TAG(S)

tags:
  - [Primary tag with full path]
  - [Secondary tag if applicable]

2. REASONING CHAIN

Explain your thought process:

  • What is the core concept?
  • What discipline does it originate from?
  • What's the appropriate depth for this specific note?
  • Are there interdisciplinary considerations?
  • Why did you choose this structure over alternatives?

3. ALTERNATIVES & TRADEOFFS

If multiple valid approaches exist, present them:

Alternative A: [tag] — Better if [condition]
Alternative B: [tag] — Better if [condition]

4. CONFIDENCE LEVEL

Be transparent about certainty:

  • High confidence: Canonical, textbook concept
  • Medium confidence: Reasonable interpretation, defensible
  • Low confidence: Emerging topic, multiple valid framings
  • Uncertain: Request clarification about note's focus

EXAMPLE: FULL REASONING PROCESS

User asks: "Help me tag my note about 'Attention Mechanisms in Transformers'"

Response:

tags:
  - Computer-Science/Artificial-Intelligence/Deep-Learning/Attention-Mechanisms

Reasoning Chain:

1. Core concept identification:

  • This is about a specific technical mechanism (attention) within a specific architecture (Transformers)
  • Attention is the defining innovation of Transformers, so both are important

2. Disciplinary lineage:

  • Root: Computer Science (clear university department)
  • Branch: Artificial Intelligence (field of study)
  • Sub-branch: Deep Learning (paradigm within AI/ML)
  • Leaf: Attention Mechanisms (specific technique)

3. Depth justification:

  • 4 levels is appropriate here because:

- Level 1-2: Establishes academic grounding - Level 3: Specifies the ML paradigm (distinguishes from symbolic AI, classical ML) - Level 4: Names the specific mechanism being studied

  • Could go to 5 levels with /Transformers/Attention, but that risks over-specification since attention is broader than just Transformers

4. Interdisciplinary check:

  • This is purely technical CS/AI content
  • No secondary tags needed unless note discusses applications (e.g., linguistics, vision)

5. Alternative considerations:

Alternative A: Computer-Science/Artificial-Intelligence/Natural-Language-Processing/Transformers

  • When to use: If note focuses on Transformers as NLP architecture rather than attention mechanism itself
  • Tradeoff: More specific to domain (NLP), less focused on the core innovation

Alternative B: Computer-Science/Artificial-Intelligence/Machine-Learning/Neural-Networks/Attention

  • When to use: If treating attention as a general neural network component
  • Tradeoff: Less specific about deep learning context

Confidence level: High

  • Attention mechanisms are well-established (2017+)
  • Clear academic consensus on taxonomy
  • Standard terminology in literature

Would recommend Alternative A instead if:

  • Note emphasizes BERT, GPT, or other specific Transformer models
  • Focus is on NLP applications rather than mechanism itself
  • Note discusses linguistic capabilities enabled by attention

ANTI-PATTERNS (Revisited with Nuance)

PatternWhy It Seems WrongWhen It Might Be RightResolution
Multiple tags at same depthSeems redundantGenuinely interdisciplinary topicsUse both if note bridges fields equally
Very deep hierarchy (6+ levels)Over-specificationHighly specialized research notesAcceptable if each level adds real specificity
Shallow tag for complex topicUnder-specificationBroad survey or intro contentAppropriate for overview notes
Custom top-level categoryBreaks conventionMeta-topics, tools, personal systemsUse Methodology/ or Tools/ roots

SELF-REFLECTION PROMPTS

Before finalizing tags, ask yourself:

  1. Clarity test: Could someone unfamiliar with the note understand what it's about from the tags alone?
  2. Retrieval test: If I wanted to find this note in 6 months, what would I search for?
  3. Consistency test: Have I tagged similar notes differently? If so, is there good reason?
  4. Granularity test: Am I at the right zoom level, or too zoomed in/out?
  5. Future-proof test: Will this tag structure still make sense if the field evolves?

MAJOR ACADEMIC DISCIPLINES (Living Reference)

This list guides but doesn't constrain. If a concept doesn't fit cleanly, that's data—not failure.

DisciplineCommon Sub-fieldsNotes
Computer-ScienceAI, Algorithms, Systems, HCI, Security, NetworksOften interdisciplinary with Math, Engineering
MathematicsAlgebra, Analysis, Statistics, Topology, LogicPure vs Applied distinction matters
PhysicsMechanics, Thermodynamics, Quantum, ElectromagnetismHistorical vs modern physics differ in organization
BiologyGenetics, Ecology, Neuroscience, EvolutionaryMolecular vs organismal levels
ChemistryOrganic, Inorganic, Biochemistry, PhysicalOverlaps heavily with Biology, Physics
PsychologyCognitive, Clinical, Social, DevelopmentalEmpirical science vs applied practice
EconomicsMicro, Macro, Behavioral, EconometricsPositive vs normative economics
PhilosophyEthics, Epistemology, Metaphysics, LogicCan be meta-tag for any field
HistoryAncient, Medieval, Modern, RegionalAlso: History of Science, Economic History, etc.
EngineeringElectrical, Mechanical, Civil, SoftwareApplied sciences with disciplinary roots
BusinessMarketing, Finance, Management, StrategyApplied social science
LinguisticsSyntax, Semantics, Phonology, ComputationalBridging humanities and CS
SociologySocial-Theory, Methods, Specialized-FieldsOften studies other disciplines
MethodologyResearch-Methods, Knowledge-Management, StatisticsMeta-level, applies across fields

FINAL PRINCIPLE: EMBRACE UNCERTAINTY

Perfect tags don't exist. Good tags:

  • Reflect current understanding
  • Facilitate retrieval
  • Respect disciplinary conventions
  • Remain open to revision

When in doubt:

  1. Choose the most defensible option
  2. Explain your reasoning
  3. Flag uncertainty
  4. Suggest when to revisit

The goal is useful navigation, not absolute truth.


References

平台分布

OpenCode

28.49%
按下载量换算1,811

Codex

19.84%
按下载量换算1,261

Antigravity

18.09%
按下载量换算1,150

Gemini CLI

12.43%
按下载量换算790

windsurf

8.03%
按下载量换算510

Cursor

3.14%
按下载量换算200

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

继续浏览同类 Skills