Token导航 LogoToken导航

Agent Skill · 研究检索

telos(telos 搜索)

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

telos 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为执行命令;许可证为 MIT,暂无第三方扫描结果,按安装量在研究检索类的 73,675 个 Skill 里排第 73,192。

总安装 140周安装 6GitHub Stars 公开资料未说明下载 49核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

AgentSkills.tonpx skills
npx skills add zpankz/mcp-skillset --skill "telos"

这个 Skill 是做什么的

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

用于查找、检索和筛选相关信息。telos 属于研究检索类 Skill,可作为该场景下的辅助能力补充。适合在关键词搜索或任务场景中快速定位候选结果。可结合来源仓库和原始 README 核验具体用法。安装前建议确认权限范围和维护状态。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。注意是否会触发联网、命令执行或文件读写操作。

来源仓库内路径:skills/telos

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add zpankz/mcp-skillset --skill "telos";命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

telos 怎么安装?

在终端执行 npx skills add zpankz/mcp-skillset --skill "telos"。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

telos 支持哪些 AI 工具?

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

telos 需要什么权限?

权限级别是执行命令。安装流程涉及命令执行,可能通过 npx skills add zpankz/mcp-skillset --skill "telos" 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

telos 是免费的吗?

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

telos 用的人多吗?

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

telos 安全吗?

没有查到第三方扫描结果,安全性无法从公开资料判断,安装前请自行审查源码、依赖和命令行为。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 许可证明确为 MIT,商用和分发边界好判断。

先想清楚的地方

  • 需要执行命令,装到常用环境前要先评估影响面。
  • 没有第三方扫描结果,安全性只能靠自己读源码判断。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 不能接受 Skill 在你机器上执行命令的人。
  • 要求有安全扫描结论才肯安装的团队。
  • 需要厂商级技术支持和 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调用外部服务未明确有提醒
telos

telos 搜索 · 本页

140—执行命令MIT未收录

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

SKILL.md 原文

name
telos
description
Teleological physiology analysis framework for understanding biological systems through multi-constraint optimization. Use when analyzing physiological mechanisms, explaining apparent biological "inefficiencies", preparing for medical examinations (CICM/ANZCA Primary), understanding why biological systems are designed the way they are, or when seeking deeper mechanistic understanding beyond descriptive knowledge. Triggers on questions like "why is X designed this way", "what purpose does Y serve", "how is Z optimized", analysis of physiological trade-offs, or exploration of evolutionary/design constraints.

TELOS: Teleological Physiology Framework

Core Principle

Analyze biological systems assuming superior designer intelligence. Apparent inefficiencies are puzzles requiring deeper investigation—elegant solutions often solve multiple problems with single mechanisms.

Epistemological stance: Teleological reasoning is a productive heuristic, not a metaphysical claim. It generates testable predictions about system design and reveals hidden constraints.

Methodological Framework

λτ.ο Pattern (Purpose → Terminal → Observation)

λτ.ο : Constraints × Design → Optimization
     where τ = teleological purpose
           ο = observed mechanism  
           λ = transformation revealing hidden design logic

Every analysis follows: Purpose → Constraints → Optimization → Mechanism

Three-Level Hierarchical Analysis

LevelFocusKey Questions
Strategic (τ)Purpose/functionWhat problem does this solve? What defines "optimal" here?
Tactical (λ)Constraint mappingWhat competing constraints exist? What alternatives were rejected?
Operational (ο)ImplementationHow is this achieved molecularly/cellularly? What quantitative optimizations?

Core Methodology

1. Constraint Mapping

Identify all constraints before seeking optimization:

Physical: Thermodynamics, kinetics, diffusion limits, mechanical forces Chemical: pH, ionic strength, molecular compatibility, reaction rates Energetic: ATP cost, metabolic efficiency, heat dissipation Spatial: Size limits, packing constraints, anatomical boundaries Temporal: Response times, developmental sequences, diurnal rhythms

See references/constraint-taxonomy.md for formal classification.

2. Oscillating Hierarchical Analysis

Atomic Principles
      ↓ zoom out
First Composites (combinations)
      ↓ zoom in
Reinforce Atomic Connections
      ↓ zoom out
Higher Composites (system integration)
      ↓ ... iterate

Each oscillation reveals connections and reinforces semantic depth. Build efficiently on prior layers.

3. Multi-Constraint Optimization Detection

When apparent "flaws" appear:

  1. List all constraints the system must satisfy
  2. Identify which constraints conflict
  3. Analyze how the "flaw" resolves the conflict
  4. Quantify the optimization across all dimensions
  5. Consider alternative designs and why rejected

4. Convergence Validation

Optimization claims require:

  • Quantitative support: Measurable efficiency gains
  • Comparative evidence: Similar solutions in unrelated systems
  • Predictive power: Explains otherwise mysterious features
  • Minimal configuration: No simpler solution satisfies all constraints

Analysis Template

## [System Name] Teleological Analysis

### Strategic: Purpose Definition
- Primary function:
- Constraints defining "optimal":
- Success criteria:

### Tactical: Constraint Mapping
| Constraint Type | Specific Constraints | Trade-offs |
|-----------------|---------------------|------------|
| Physical        |                     |            |
| Chemical        |                     |            |
| Energetic       |                     |            |
| Spatial         |                     |            |
| Temporal        |                     |            |

### Operational: Implementation Analysis
- Molecular mechanisms:
- Quantitative optimizations:
- Integration points:

### Synthesis: Multi-Constraint Resolution
- How single mechanism solves multiple problems:
- Alternative designs considered:
- Why current design is minimal energy configuration:

### Validation
- Convergent evidence:
- Predictive implications:
- Falsifiable claims:

Integration Points

With quantitative-physiology

Leverage equations to validate optimization claims quantitatively:

  • Stewart-Hamilton for cardiac output optimization
  • Henderson-Hasselbalch for pH gradient analysis
  • Nernst equation for membrane potential efficiency

With hierarchical-reasoning

Map teleological levels to cognitive architecture:

  • Strategic ↔ Purpose/function analysis
  • Tactical ↔ Constraint identification
  • Operational ↔ Mechanistic implementation

With saq

Generate examination questions testing teleological understanding:

  • Frame mechanisms within design context
  • Test constraint awareness beyond fact recall

With constraints skill

Formalize physiological constraints using:

  • Deontic modalities (what is permitted/required given physics)
  • Juarrero's trichotomy (enabling/governing/constitutive)

Validation Rubrics

CriterionWeakModerateStrong
Constraint mapping1-2 constraints3-4 constraints5+ constraints with interactions
Quantitative supportQualitative onlySome numbersEquation-backed
Alternative considerationNoneMentionedAnalyzed why rejected
Predictive powerDescriptiveExplains known factsPredicts unknown features
ConvergenceSingle exampleRelated systemsPhylogenetically independent

See references/validation-rubrics.md for detailed scoring.

Common Pitfalls

  1. Panglossian fallacy: Assuming everything is optimal. Some features are historical accidents or vestigial.
  2. Single-constraint thinking: Optimizing for one constraint while ignoring trade-offs.
  3. Post-hoc rationalization: Inventing purposes without constraint evidence.
  4. Ignoring alternatives: Not considering why other designs were "rejected."

Quick Reference: Analysis Triggers

Apply teleological analysis when encountering:

  • "Inefficient" or "wasteful" biological processes
  • Anatomical arrangements that seem suboptimal
  • Redundant or apparently unnecessary mechanisms
  • Extreme precision in physiological values (e.g., pH 7.4)
  • Convergent evolution across unrelated lineages

Example Analyses

See references/case-studies.md for worked examples:

  • Intracellular pH gradient (0.6 unit differential)
  • Vertebrate retinal architecture ("inverted" design)
  • Renal countercurrent multiplication
  • Hemoglobin cooperativity

Clinical Applications

Pathological states as constraint violations:

  • Identify which design constraint is broken
  • Predict compensatory mechanisms based on design logic
  • Explain therapeutic targets via intended function
  • Understand why some interventions fail (violate other constraints)

平台分布

windsurf

31.81%
按下载量换算16

OpenCode

24.11%
按下载量换算12

kiro-cli

16.94%
按下载量换算8

Codex

11.25%
按下载量换算6

Claude Code

5.16%
按下载量换算3

安全审计

暂无安全审计结果可展示。

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add zpankz/mcp-skillset --skill "telos" 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

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

继续浏览同类 Skills