重要前提
安装AI Skills的关键前提是:必须科学上网,且开启TUN模式,这一点至关重要,直接决定安装能否顺利完成,在此郑重提醒三遍:科学上网,科学上网,科学上网。查看完整安装教程 →
Telos by danielmiessler/personal_ai_infrastructure
npx skills add https://github.com/danielmiessler/personal_ai_infrastructure --skill TelosTELOS(目的性演化与生命操作系统)是一个全面的上下文收集系统,包含两个应用:
~/.claude/skills/CORE/USER/TELOS/执行工作流时,请同时执行以下两项操作:
发送语音通知 :
curl -s -X POST http://localhost:8888/notify
-H "Content-Type: application/json"
-d '{"message": "Running the WORKFLOWNAME workflow from the Telos skill"}'
> /dev/null 2>&1 &
输出文本通知 :
Running the WorkflowName workflow from the Telos skill...
完整文档: ~/.claude/skills/CORE/SkillNotifications.md
执行工作流时,直接输出此通知:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
Running the **WorkflowName** workflow from the **Telos** skill...
| 工作流 | 触发词 | 文件 |
|---|---|---|
| 更新 | "add to TELOS", "update my goals", "add book to TELOS" | Workflows/Update.md |
| 访谈提取 | "extract content", "extract interviews", "analyze interviews" | Workflows/InterviewExtraction.md |
| 创建叙事要点 | "create narrative", "narrative points", "TELOS report", "n=24" | Workflows/CreateNarrativePoints.md |
| 撰写报告 | "write report", "McKinsey report", "create TELOS report", "professional report" | Workflows/WriteReport.md |
注意: 对于常规的项目分析、仪表板、依赖关系映射和执行摘要,该技能会直接处理,无需单独的工作流文件。
示例 1:更新个人 TELOS
User: "add Project Hail Mary to my TELOS books"
--> 调用更新工作流
--> 创建带时间戳的 BOOKS.md 备份
--> 添加带格式化元数据的书籍条目
--> 在 updates.md 中记录带时间戳的更改
示例 2:使用 TELOS 分析项目
User: "analyze ~/Projects/MyApp with TELOS"
--> 扫描目录中的所有 .md 和 .csv 文件
--> 提取实体、关系、依赖
--> 返回包含依赖链和进度指标的分析
示例 3:构建项目仪表板
User: "build a dashboard for TELOSAPP"
--> 启动最多 10 个并行工程师
--> 使用 shadcn/ui + Aceternity 创建 Next.js 仪表板
--> 返回包含依赖关系图、指标卡片、进度表的交互式仪表板
示例 4:生成叙事要点
User: "create TELOS narrative for Acme Corp, n=24"
--> 调用创建叙事要点工作流
--> 分析 TELOS 上下文(情况、问题、建议)
--> 返回 24 个简洁的要点(每条 8-12 个单词)
--> 输出可直接用于演示文稿或客户简报
示例 5:生成麦肯锡风格报告
User: "write a TELOS report for Acme Corp"
--> 调用撰写报告工作流
--> 首先运行创建叙事要点以生成故事内容
--> 将叙事映射到麦肯锡报告结构
--> 生成具有专业样式的基于网页的报告
--> 输出位于 {project_dir}/report - 运行 `bun dev` 查看
--> 白色背景,辅以微妙的 Tokyo Night Storm 强调色
--> 包含:封面页、执行摘要、发现、建议、路线图
{daidentity.name} 如何确定使用哪个 TELOS 上下文:
| 用户请求 | 上下文 | 位置 |
|---|---|---|
| "my TELOS", "my goals", "my beliefs", "add to TELOS" | 个人 TELOS | ~/.claude/skills/CORE/USER/TELOS/ |
| "Alma", "TELOSAPP", "analyze [project]", "dashboard for" | 项目 TELOS | 用户指定的目录 |
| "analyze ~/path/to/project" | 项目 TELOS | 指定的路径 |
关键路径: 所有个人 TELOS 文件都位于:
~/.claude/skills/CORE/USER/TELOS/
个人 TELOS 位于 CORE USER 目录中,而非直接位于 Telos 技能目录下。
所有文件位于 ~/.claude/skills/CORE/USER/TELOS/:
# 查看特定文件
read ~/.claude/skills/CORE/USER/TELOS/GOALS.md
read ~/.claude/skills/CORE/USER/TELOS/BELIEFS.md
# 查看最近更新
read ~/.claude/skills/CORE/USER/TELOS/updates.md
关键: 切勿手动编辑。请使用更新工作流。
工作流: Workflows/Update.md
该工作流提供:
可更新的有效文件: BELIEFS.md, BOOKS.md, CHALLENGES.md, FRAMES.md, GOALS.md, LEARNED.md, MISSION.md, MODELS.md, MOVIES.md, NARRATIVES.md, PREDICTIONS.md, PROBLEMS.md, PROJECTS.md, STRATEGIES.md, TELOS.md, TRAUMAS.md, WISDOM.md, WRONG.md
对于任何项目目录,TELOS 提供:
灵活的文件发现 - 无需特定结构:
# 用户指定目录
"Analyze ~/Cloud/Projects/TELOSAPP"
--> {daidentity.name} 扫描树状结构中任意位置的 .md 和 .csv 文件
# {daidentity.name} 自动查找所有 .md 和 .csv 文件,无论结构如何
自动检测:
发现所有 Markdown 和 CSV 文件:
find $TARGET_DIR -type f \( -name "*.md" -o -name "*.csv" \)
索引:
构建关系图:
生成分析:
输出格式:
关键:构建 UI 时,使用最多 16 个并行工程师。
启动策略: 使用包含 10 个并行 Task 调用的单条消息:
Engineer 1: 项目结构 + 布局 + 导航
Engineer 2: 包含指标卡片的概览页面
Engineer 3: 包含进度跟踪的项目页面
Engineer 4: 包含性能表的团队页面
Engineer 5: 漏洞/问题页面
Engineer 6: 进度时间线可视化
Engineer 7: 数据解析库(MD/CSV)
Engineer 8: 共享组件(卡片、徽章、表格)
Engineer 9: 设计优化和主题
Engineer 10: 集成和测试
技术栈:
功能:
设计:
--background: #ffffff
--foreground: #1a1b26
--primary: #2e7de9
--accent: #9854f1
--destructive: #f52a65
--success: #33b579
--warning: #f0a020
标准项目 TELOS 结构(自动检测):
注意: 文件是可选的。TELOS 会适应任何存在的文件。
可用的可视化:
个人 TELOS:
项目 TELOS:
~/.claude/skills/CORE/USER/TELOS/(位于 CORE USER 目录)
* 项目 TELOS: 用户指定的目录TELOS 是 {principal.name} 的生命操作系统和项目分析框架。一个技能,两个强大的上下文。
记住: 个人 TELOS 文件位于 ~/.claude/skills/CORE/USER/TELOS/(在 CORE USER 目录中)
每周安装
48
仓库
GitHub 星标
9.7K
首次出现
Jan 24, 2026
安全审计
安装于
gemini-cli41
codex41
github-copilot39
opencode38
claude-code36
cursor36
TELOS (Telic Evolution and Life Operating System) is a comprehensive context-gathering system with two applications:
~/.claude/skills/CORE/USER/TELOS/When executing a workflow, do BOTH:
Send voice notification :
curl -s -X POST http://localhost:8888/notify \
-H "Content-Type: application/json" \
-d '{"message": "Running the WORKFLOWNAME workflow from the Telos skill"}' \
> /dev/null 2>&1 &
Output text notification :
Running the **WorkflowName** workflow from the **Telos** skill...
Full documentation: ~/.claude/skills/CORE/SkillNotifications.md
When executing a workflow, output this notification directly:
Running the **WorkflowName** workflow from the **Telos** skill...
| Workflow | Trigger | File |
|---|---|---|
| Update | "add to TELOS", "update my goals", "add book to TELOS" | Workflows/Update.md |
| InterviewExtraction | "extract content", "extract interviews", "analyze interviews" | Workflows/InterviewExtraction.md |
| CreateNarrativePoints | "create narrative", "narrative points", "TELOS report", "n=24" | Workflows/CreateNarrativePoints.md |
| WriteReport | "write report", "McKinsey report", "create TELOS report", "professional report" | Workflows/WriteReport.md |
Note: For general project analysis, dashboards, dependency mapping, and executive summaries, the skill handles these directly without a separate workflow file.
Example 1: Update personal TELOS
User: "add Project Hail Mary to my TELOS books"
--> Invokes Update workflow
--> Creates timestamped backup of BOOKS.md
--> Adds book entry with formatted metadata
--> Logs change in updates.md with timestamp
Example 2: Analyze project with TELOS
User: "analyze ~/Projects/MyApp with TELOS"
--> Scans all .md and .csv files in directory
--> Extracts entities, relationships, dependencies
--> Returns analysis with dependency chains and progress metrics
Example 3: Build project dashboard
User: "build a dashboard for TELOSAPP"
--> Launches up to 10 parallel engineers
--> Creates Next.js dashboard with shadcn/ui + Aceternity
--> Returns interactive dashboard with dependency graphs, metrics cards, progress tables
Example 4: Generate narrative points
User: "create TELOS narrative for Acme Corp, n=24"
--> Invokes CreateNarrativePoints workflow
--> Analyzes TELOS context (situation, problems, recommendations)
--> Returns 24 crisp bullet points (8-12 words each)
--> Output is slide-ready for presentations or customer briefings
Example 5: Generate McKinsey-style report
User: "write a TELOS report for Acme Corp"
--> Invokes WriteReport workflow
--> First runs CreateNarrativePoints to generate story content
--> Maps narrative to McKinsey report structure
--> Generates web-based report with professional styling
--> Output at {project_dir}/report - run `bun dev` to view
--> White background, subtle Tokyo Night Storm accents
--> Includes: cover page, executive summary, findings, recommendations, roadmap
How {daidentity.name} determines which TELOS context:
| User Request | Context | Location |
|---|---|---|
| "my TELOS", "my goals", "my beliefs", "add to TELOS" | Personal TELOS | ~/.claude/skills/CORE/USER/TELOS/ |
| "Alma", "TELOSAPP", "analyze [project]", "dashboard for" | Project TELOS | User-specified directory |
| "analyze ~/path/to/project" | Project TELOS | Specified path |
CRITICAL PATH: All personal TELOS files are located at:
~/.claude/skills/CORE/USER/TELOS/
Personal TELOS lives in the CORE USER directory, NOT directly under the Telos skill directory.
All files located in ~/.claude/skills/CORE/USER/TELOS/:
# View specific file
read ~/.claude/skills/CORE/USER/TELOS/GOALS.md
read ~/.claude/skills/CORE/USER/TELOS/BELIEFS.md
# View recent updates
read ~/.claude/skills/CORE/USER/TELOS/updates.md
CRITICAL: Never manually edit. Use the Update workflow.
Workflow: Workflows/Update.md
The workflow provides:
Valid files for updates: BELIEFS.md, BOOKS.md, CHALLENGES.md, FRAMES.md, GOALS.md, LEARNED.md, MISSION.md, MODELS.md, MOVIES.md, NARRATIVES.md, PREDICTIONS.md, PROBLEMS.md, PROJECTS.md, STRATEGIES.md, TELOS.md, TRAUMAS.md, WISDOM.md, WRONG.md
For any project directory, TELOS provides:
Flexible file discovery - no required structure:
# User specifies directory
"Analyze ~/Cloud/Projects/TELOSAPP"
--> {daidentity.name} scans for .md and .csv files anywhere in tree
# {daidentity.name} automatically finds all .md and .csv files regardless of structure
Auto-detection:
Discover all markdown and CSV files:
find $TARGET_DIR -type f \( -name "*.md" -o -name "*.csv" \)
Index:
Build relationship graph:
Produce analytics:
Output Formats:
CRITICAL: When building UIs, use up to 16 parallel engineers.
Launch Strategy: Use single message with 10 Task calls in parallel:
Engineer 1: Project structure + layout + navigation
Engineer 2: Overview page with metrics cards
Engineer 3: Projects page with progress tracking
Engineer 4: Teams page with performance tables
Engineer 5: Vulnerabilities/issues page
Engineer 6: Progress timeline visualization
Engineer 7: Data parsing library (MD/CSV)
Engineer 8: Shared components (cards, badges, tables)
Engineer 9: Design polish and theme
Engineer 10: Integration and testing
Tech Stack:
Features:
Design:
--background: #ffffff
--foreground: #1a1b26
--primary: #2e7de9
--accent: #9854f1
--destructive: #f52a65
--success: #33b579
--warning: #f0a020
Standard Project TELOS Structure (auto-detected):
Note: Files are optional. TELOS adapts to whatever exists.
Available Visualizations:
Personal TELOS:
Project TELOS:
~/.claude/skills/CORE/USER/TELOS/ (in CORE USER directory)TELOS is {principal.name}'s life operating system AND project analysis framework. One skill, two powerful contexts.
Remember: Personal TELOS files live at ~/.claude/skills/CORE/USER/TELOS/ (in the CORE USER directory)
Weekly Installs
48
Repository
GitHub Stars
9.7K
First Seen
Jan 24, 2026
Security Audits
Gen Agent Trust HubFailSocketPassSnykPass
Installed on
gemini-cli41
codex41
github-copilot39
opencode38
claude-code36
cursor36
GitHub Actions 官方文档查询助手 - 精准解答 CI/CD 工作流问题
49,000 周安装