Auto-sync: 2026-04-22 19:20
This commit is contained in:
@@ -7,7 +7,13 @@ This wiki is a living synthesis of curated sources spanning AI agents, cloud inf
|
||||
### Multi-Agent AI Systems
|
||||
The wiki covers two major multi-agent frameworks: **The Agency** (agency-agents) and **OpenClaw**. The Agency provides 147 specialized agents across 12 business divisions (Engineering, Design, Finance, Game Dev, Marketing, Paid Media, Product, Project Management, Testing, Support, Spatial Computing, Specialized). OpenClaw focuses on autonomous agents with persistent memory and workflow orchestration via n8n.
|
||||
|
||||
Key concepts: [[Agent Personality]], [[Agent Specialization]], [[Multi-Agent Coordination]], [[Multi-Tool Integration]], [[MCP Tool Interface Design]], [[Workflow Architecture]]
|
||||
**[[multi-channel-assistant]]**:基于 [[OpenClaw]] 的多渠道个人助理方案——以 Telegram Topic 路由为统一入口,整合 Google Workspace(gog)、Slack、Todoist、Asana,实现"说一句话完成全套工作"。核心价值:消除应用切换疲劳,AI 主动推送定时提醒(如每周垃圾清理、公司周报)。
|
||||
|
||||
**[[phone-based-personal-assistant]]**:通过 ClawdTalk + Telnyx 将任意手机变成 AI 助理语音入口——拨打电话即可与 [[OpenClaw]] 对话,支持日历查询、Jira 任务更新、网络搜索等技能,无需智能手机 App 或浏览器,覆盖驾驶、步行等双手占用场景。与 [[multi-channel-assistant]] 互补:文字入口覆盖图文交互,语音入口覆盖无屏场景。
|
||||
|
||||
**Inbox De-clutter**:基于 [[OpenClaw]] 的 Newsletter 自动整理方案——每天 20:00 通过 Cron Job 阅读过去 24 小时的新邮件,生成精华摘要并附原文链接,根据用户反馈持续学习偏好。需前置 Gmail OAuth Setup。与 [[custom-morning-brief]] 属同一 Cron Job + AI 摘要模式的 Newsletter 垂直场景。与 [[email-triage]] 属同一方法论的不同实现。
|
||||
|
||||
Key concepts: [[Email Triage]], [[Newsletter Digest]], [[Preference Learning]], [[Cron Job]], [[Multi-Agent Coordination]], [[Multi-Tool Integration]], [[MCP Tool Interface Design]], [[Workflow Architecture]], [[Shared Memory Architecture]], [[Private Context]], [[Single Control Plane]], [[Scheduled Task Flywheel]], [[Parallel Agent Execution]], [[Topic-Based Routing]], [[Voice Interface]], [[Telephony Integration]], [[PM Delegation Pattern]], [[CEO Pattern]], [[Shared State Coordination]], [[Git-as-Audit-Log]]
|
||||
|
||||
### Cloud Transformation & DevOps
|
||||
Cloud Transformation Programme (CTP) materials cover AWS landing zones, EKS, Terraform, GitOps, FinOps, observability, security, and enterprise architecture. Key themes: 3 Lines of Defence framework, ITSM, container hardening, backup & DR strategies. DevOps culture focuses on four pillars: Collaboration, Automation (CI/CD, IaC), Continuous Improvement (Kaizen), and Customer-Centricity. Agile practices (Scrum, Kanban) are symbiotic with DevOps. Emerging trends: DevSecOps, GitOps, Serverless DevOps, AI/ML-driven automation, and Edge Computing DevOps.
|
||||
@@ -19,11 +25,15 @@ Home office setup guides cover a complete multi-node home network infrastructure
|
||||
|
||||
Key concepts: [[Docker-Image]], [[Docker-Save]], [[Docker-Load]], [[Docker Compose]], [[Docker Engine]], [[Docker 用户组]], [[APT 仓库配置]], [[GPG 密钥验证]], [[it-tools]], [[RSSHub]], [[内网穿透]], [[反向代理]], [[TCP隧道]], [[Caddy]], [[frp]], [[Symbolic Link]], [[软链接策略]], [[目录映射]], [[Prometheus]], [[PromQL]], [[Prometheus告警规则]], [[Grafana]], [[node_exporter]], [[cAdvisor]], [[blackbox_exporter]], [[Alertmanager]], [[Uptime Kuma]], [[Netdata]], [[VictoriaMetrics]], [[合成监控]], [[Exporter]], [[时序数据库]], [[TUI]], [[Process Management]], [[System Monitoring]], [[容器资源限制]], [[容器重启策略]], [[端口映射]], [[媒体服务器]], [[转码缓存]], [[只读挂载]], [[增量备份]], [[永久挂载]], [[挂载点检查]], [[Cron定时任务]], [[进程管理]], [[Socket 登录]], [[用户权限]], [[固件刷入]], [[过渡固件]], [[JFFS双清]], [[策略组分流]], [[故障转移]], [[订阅机制]], [[PUID/PGID]], [[桥接网络]], [[Socket Activation]], [[UFW 防火墙]], [[开机自启]], [[VPN Panel]], [[Xray]], [[BBR]], [[Web Proxy Protocol]], **[[全盘镜像备份]]**, **[[裸机恢复]]**, **[[NFS网络备份]]**, **[[UEFI启动]]**, [[指纹浏览器]], [[IP纯净度]], [[虚拟信用卡]], [[接码平台]], [[账号隔离]], **[[云盘挂载]]**, **[[NAS套件管理]]**, [[Root权限修复]], [[SPK套件格式]], [[launchd]], [[Gatekeeper]], **[[图床]]**, **[[S3-兼容对象存储]]**, **[[Docker堆栈]]**, **[[逻辑备份]]**, [[systemd]], [[Ubuntu Server]], **[[BI平台]]**, [[数据可视化]], **[[systemd-logind]]**, **[[HandleLidSwitch]]**, [[休眠目标]], [[pmset]], [[caffeinate]], [[Wake-on-LAN]], [[Headless 服务器]], [[系统睡眠管理]]
|
||||
|
||||
**Self-Healing Infrastructure Agent**: 基于 [[OpenClaw]] 的家庭服务器自动驾驶代理(代号 "Reef")——通过 SSH 访问家庭网络所有机器,配置 Cron Job 系统(15个活跃任务)实现 24/7 全天候自动化:每 15 分钟检查看板、每小时健康监控+邮件分拣、每 6 小时知识库录入+自检、每日 8AM 晨报(天气/日历/系统状态)、每周安全审计。Agent 可自动执行 SSH、Terraform、Ansible、kubectl 命令修复基础设施问题——"在你知道问题前就修复它"。核心安全策略:TruffleHog pre-push hooks + 私有 Gitea CI 扫描_pipeline + 1Password 专用 AI vault + 每日安全审计(防特权容器/硬编码 secrets/过度权限)。知识提取具有复利效应——一位用户从 ChatGPT 历史中提取了 49,079 条原子事实。Key concepts: [[Morning Briefing]], [[Email Triage]], [[Local-first Git]], [[Defense-in-Depth]], [[Self-Healing-Systems]], [[Agentic AI]], [[Infrastructure-as-Code]], [[Gitea]], [[TruffleHog]], [[ArgoCD]], [[Loki]], [[Gatus]], [[K3s]]
|
||||
|
||||
### YouTube Automation
|
||||
A practical tip for extracting YouTube Channel IDs: use `view-source:` prefix in browser to access channel page source, search for `channel_id` string in the page source to find the RSS Feed URL containing the channel ID. Can be used in [[n8n]] workflows for YouTube subscription monitoring.
|
||||
|
||||
**AI-Powered Daily Digest**: [[daily-youtube-digest]] provides a fully automated pipeline — AI Agent periodically checks subscribed channels for new uploads → extracts video transcripts via [[TranscriptAPI.com]] → generates key-point summaries → delivers a daily digest. Runs on [[OpenClaw]] via the `youtube-full` skill (installable from [[ClawHub]]), using 0-credit free API calls for channel checking and 1 credit per transcript for summarization. Supports two modes: channel-based (e.g., @TED, @Fireship, @LexFridman) and keyword-based (e.g., "Claude Code", "AI agents").
|
||||
|
||||
**[[Daily Reddit Digest]]**:AI Agent 驱动的 Reddit 每日精选摘要自动化——通过 [[OpenClaw]] + `reddit-readonly` skill,每日定时抓取指定 Subreddit 的热门/最新/最高赞帖子,AI 记忆用户偏好并持续优化精选规则(如排除表情包类内容)。纯读取模式,无需认证。属 [[Daily YouTube Digest]] 同款模式(定时 + AI 摘要 + 偏好学习)的 Reddit 垂直场景。
|
||||
|
||||
**Multi-Agent Content Factory**: [[content-factory]] 是基于 Discord 频道的多 Agent 内容工厂,通过 Research Agent → Writing Agent → Thumbnail Agent 链式协作,实现内容创作全流程自动化(研究→写作→设计)。每天定时运行,创作者次日醒来即可收获成品内容。[[OpenClaw]] 提供 sessions_spawn/sessions_send 能力支撑多 Agent 编排。
|
||||
|
||||
Key concepts: [[Channel ID]], [[RSS Feed]], [[YouTube Automation]], [[Daily-Digest]], [[Transcript-Based Summarization]], [[TranscriptAPI.com]], [[Chained Agents]], [[Content Automation]]
|
||||
@@ -53,6 +63,18 @@ Key concepts: [[国家中小学智慧教育平台]], [[tchMaterial-parser]], [[C
|
||||
### AI Tools & Prompt Engineering
|
||||
Covers Claude Code, Claude Code Templates (npx 一键安装 Skills/Agents/MCP via `npx claude-code-templates@latest --skill=<path> --yes` from aitmpl.com), OpenCode, [[Cursor]], [[Trae]], Gemini CLI, Vibe Coding, RAG, multi-agent workflows, NotebookLM, Nano Banana prompting, and video generation tools.
|
||||
|
||||
**Custom Morning Brief**:基于 [[OpenClaw]] 的晨间简报自动化——每天定时(例 8AM)通过 Telegram/Discord/iMessage 推送结构化报告,内容涵盖:新闻研究(AI/创业/科技方向)、当日待办事项(集成 Todoist/Apple Reminders/Asana)、主动任务推荐(AI 自主思考可帮助完成的事项)、睡前完成的完整草稿(脚本/邮件/商业方案,而非仅标题)。核心洞察:**主动任务推荐**是整个系统最有价值的部分——AI 主动思考如何帮助用户,而非被动等待指令;完整草稿(full draft)比标题建议节省大量时间;用户只需发消息即可调整简报内容,无门槛个性化。与 [[self-healing-home-server]] 的 Morning Briefing 属同一模式的不同垂直场景。
|
||||
|
||||
**Health & Symptom Tracker**:基于 [[OpenClaw]] 的食物敏感性自动追踪方案——通过 Telegram 话题记录食物和症状,Cron Job 每日三餐定时提醒(8AM/1PM/7PM),OpenClaw 自动解析消息并带时间戳写入 Markdown 日志,每周分析关联模式识别潜在触发因素。无需专用 App,完全自托管。
|
||||
|
||||
**AI-Powered Earnings Tracker**:基于 [[OpenClaw]] 的财报季自动化追踪方案——每周日 6PM 扫描财报日历并过滤用户关注公司(NVDA/MSFT/GOOGL/META/AMZN/TSLA/AMD),Telegram 投递预览列表;用户确认后为每家公司调度一次性 Cron Job,财报发布后自动搜索、格式化摘要(beat/miss、营收、EPS、AI 亮点、指引)并投递。与 [[Daily YouTube Digest]] 同属 Cron Job + AI 摘要 + Telegram 投递模式的不同实例。
|
||||
|
||||
**Event Guest Confirmation**:基于 [[OpenClaw]] + [[SuperCall]] 的活动嘉宾自动确认方案——通过 AI 语音电话批量外呼客人,确认出席状态并收集备注(饮食禁忌、Plus-One、到达时间等),通话完成后生成出席确认/未出席/未接听三分类摘要。核心价值:真人电话比短信/文字消息回复率更高;SuperCall 的沙盒 persona 设计确保 AI 只拥有预设上下文,无法访问用户 Agent 或数据,无 Prompt Injection 风险;每通电话独立重置,无对话间信息混淆。与 [[phone-based-personal-assistant]] 同属 AI 电话外呼场景,但 [[SuperCall]] 的独立沙盒设计更适用于确认类单一任务。
|
||||
|
||||
**Market Research & Product Factory**:基于 [[OpenClaw]] 的"创业自动驾驶"方案——通过 [[Last 30 Days Skill]] 挖掘 Reddit 和 X 近30天真实用户痛点,按频率排序TOP需求,分析现有方案缺口,然后直接让 OpenClaw 构建可分享的 Web 应用 MVP。核心价值:**发短信就能完成从市场调研到产品原型的全流程**,无需技术背景。与 [[content-factory]] 同属 Alex Finn 启发的 OpenClaw 高阶用法,但前者侧重内容创作,后者侧重产品机会发现。
|
||||
|
||||
**Pre-Build Idea Validator**:基于 [[OpenClaw]] + [[idea-reality-mcp]] 的 AI 项目启动前竞争分析门控——在写代码之前自动扫描 GitHub/Hacker News/npm/PyPI/Product Hunt 五个数据源,返回 `reality_signal` 分数(0-100)评估赛道拥挤度:高分数(>70)触发 STOP(展示竞品+询问是否继续/转向),低分数(<30)直接构建。核心价值:**在投入时间前发现已解决的同类问题**,是单兵创业者最重要的决策门控。与 [[market-research-product-factory]] 互补:后者挖痛点找方向,前者在动手前验证赛道的竞争密度。
|
||||
|
||||
**Claude Code 调用方法**:[[claude-code调用方法总结]] 详细记录了 Hermes Agent 通过 `terminal` 工具调用 Claude Code 的两种模式——Print Mode(`claude -p`,适合绝大多数任务)和 TMUX 交互模式(适合超长任务)。核心参数包括 `--permission-mode bypassPermissions`(跳过所有权限确认)和 `--add-dir`(加载 SKILL.md)。关键结论:当任务需要 Claude Code 的 Skill 时,应使用 `terminal` 调用 `claude -p` 而非 `delegate_task`。
|
||||
|
||||
**播客制作自动化**:[[podcast-production-pipeline]] 提供 AI Agent 全自动播客制作流水线,覆盖「录前研究→大纲脚本→录制→时间戳笔记→社媒推广包→SEO描述」全链路。与 [[Content Factory]] 配合可将播客内容复用为博客、Newsletter、视频片段等多格式资产。
|
||||
@@ -63,7 +85,7 @@ Covers Claude Code, Claude Code Templates (npx 一键安装 Skills/Agents/MCP vi
|
||||
|
||||
**会议记录自动化**:[[meeting-notes-action-items]] 提供 AI Agent 自动将会议转录文本(Otter.ai、Google Meet、Zoom)转换为结构化摘要,自动从会议中提取行动项并创建 Jira/Linear/Todoist/Notion 任务,同时发送 Slack/Discord 摘要,支持截止日提醒。核心洞察:**自动任务创建**比摘要本身更有价值,无法转化为追踪任务的会议记录只是"文档剧场"。
|
||||
|
||||
Key concepts: [[MeetingNotes]], [[ActionItemTracking]], [[TaskAutomation]], [[TranscriptProcessing]], [[RAG从入门到精通系列]], [[Agent Personality Design]], [[Vibe Coding]], [[Design-to-Code Workflow]], [[Multi-AI Review]], [[CodeWeaver]], [[LLM Wiki]], [[多智能体系统可靠性]], [[Plan Mode]], [[Build Mode]], [[Workspace]], [[AGENTS.md]], [[SOUL.md]], [[USER.md]], [[IDENTITY.md]], [[TOOLS.md]], [[BOOTSTRAP.md]], [[HEARTBEAT.md]], [[MEMORY.md]], [[Agent-Memory]], [[Claude Code Templates]], [[MCP(Model Context Protocol)]], [[Remote-SSH]], [[Bind Mount]], [[Attach 容器]], [[Docker 用户组]], [[SSH Config]], [[SSH 免密登录]], [[Vibe-Kanban]], [[OpenCode]], [[nvm]], [[pm2]], [[单一职责原则]], [[DRY原则]], [[模块化编程]], [[微服务架构]], [[Redis缓存]], [[消息队列]], [[输入-处理-输出模型]], [[并发编程]]
|
||||
Key concepts: [[MeetingNotes]], [[ActionItemTracking]], [[TaskAutomation]], [[TranscriptProcessing]], [[RAG从入门到精通系列]], [[Agent Personality Design]], [[Vibe Coding]], [[Design-to-Code Workflow]], [[Multi-AI Review]], [[CodeWeaver]], [[LLM Wiki]], [[多智能体系统可靠性]], [[Plan Mode]], [[Build Mode]], [[Workspace]], [[AGENTS.md]], [[SOUL.md]], [[USER.md]], [[IDENTITY.md]], [[TOOLS.md]], [[BOOTSTRAP.md]], [[HEARTBEAT.md]], [[MEMORY.md]], [[Agent-Memory]], [[Claude Code Templates]], [[MCP(Model Context Protocol)]], [[Remote-SSH]], [[Bind Mount]], [[Attach 容器]], [[Docker 用户组]], [[SSH Config]], [[SSH 免密登录]], [[Vibe-Kanban]], [[OpenCode]], [[nvm]], [[pm2]], [[单一职责原则]], [[DRY原则]], [[模块化编程]], [[微服务架构]], [[Redis缓存]], [[消息队列]], [[输入-处理-输出模型]], [[并发编程]], [[Pain Point Mining]], [[Startup MVP Pipeline]], [[Agent-Driven Market Research]], [[Last 30 Days Method]], [[Pre-Build Validation]], [[Reality-Signal]], [[Competition-Analysis]], [[Pivot-Strategy]], [[Agent-Build-Gate]]
|
||||
|
||||
### Productivity & Knowledge Management
|
||||
Obsidian plugins, blogwatcher RSS monitoring, Quartz static site generation, project management systems, and personal CRM frameworks. QuickAdd plugin enables quick note capture via hotkeys for rapid idea recording.
|
||||
@@ -226,7 +248,7 @@ Key concepts: [[Django ORM]], [[Django REST Framework]], [[Django Admin 定制]]
|
||||
|
||||
## Conflict Areas
|
||||
|
||||
1. **Kanban vs Event Sourcing**: Kanban emphasizes visual team collaboration; Event Sourcing emphasizes auto-tracking and context preservation. [[Project State Management]] vs traditional PM tools.
|
||||
1. **Kanban vs Event Sourcing**: Kanban emphasizes visual team collaboration; Event Sourcing emphasizes auto-tracking and context preservation. **[[Project State Management]]**(事件驱动看板替代方案)vs 传统 PM 工具。核心差异:手动拖拽 vs 自然语言输入;静态快照 vs 全历史保留;无上下文 vs 完整决策链。**[[Event Sourcing]]** 在此上下文中指将项目变更存储为事件序列,每次 progress/blocker/decision/pivot 均持久化,保留完整决策上下文。
|
||||
|
||||
2. **Kuaishou vs Douyin**: Kuaishou emphasizes authenticity and balanced algorithm; Douyin emphasizes polished content and central recommendation. Same country, opposite platform strategies.
|
||||
|
||||
@@ -243,3 +265,5 @@ Key concepts: [[Django ORM]], [[Django REST Framework]], [[Django Admin 定制]]
|
||||
8. **macOS vs Linux 睡眠管理**:macOS 使用 `pmset` 命令配置电源管理(sleep/displaysleep/standby/hibernatemode),Linux/Ubuntu 使用 `systemd-logind` 的 `HandleLidSwitch=ignore` 配置。两者目标相同(防止服务器睡眠),但工具链完全不同,不可互换但互为参考。[[mac-mini-服务器配置-防止自动锁屏与睡眠]] vs [[ubuntu禁用合盖休眠]]。
|
||||
|
||||
9. **数据库备份方案**:pg_dump 逻辑备份 vs rsync 文件级备份。pg_dump 是热备份标准(零停机、跨平台迁移能力强),但不能备份运行中数据库的物理文件目录;rsync 适合 Docker 卷备份但需确保数据库一致状态。[[MinIO + Zipline 图床安装]] 使用 pg_dump 逻辑备份 PostgreSQL + Hyper Backup 文件备份 MinIO 目录,两者互补。
|
||||
|
||||
10. **SuperCall 沙盒 Persona vs 通用语音 Agent**:[[event-guest-confirmation]] 中使用的 [[SuperCall]] 强调独立沙盒设计——AI persona 只持有预设的 persona name、goal、opening line,无法访问外部系统;[[phone-based-personal-assistant]] 侧重通用个人助手场景,需要访问更多上下文。**[[Sandboxed Persona]]** 适用于确认类单一任务(安全、无注入风险);通用语音 Agent 适用于需要跨系统协调的复杂助手场景。
|
||||
|
||||
Reference in New Issue
Block a user