Token导航 LogoToken导航TokenDH.com
研究检索操作浏览器clawhub未标认证来源可访问clear审计提醒

openclaw-skill-intelligence-ingestionOpenClaw 技能 intelligence ingestion

Agent Skill

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

总安装

16,944

周安装

706

GitHub Stars

公开资料未说明

下载量

5,648
OpenClaw

安装说明

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

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:openclaw-skill-intelligence-ingestion(OpenClaw 技能 intelligence ingestion)
来源仓库:https://github.com/2233admin/openclaw-skill-intelligence-ingestion
安装命令:
openclaw skills install openclaw-skill-intelligence-ingestion
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install openclaw-skill-intelligence-ingestion

简介

自动分析 URL 内容并生成黑曜石笔记更新内存。

  • 适合快速捕获外部信息与战略价值点。
  • 支持文章、推文等多种内容类型接入。
  • 需配置正确的 API 密钥与访问权限。
  • 注意隐私数据过滤与存储合规要求。openclaw-skill-intelligence-ingestion 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

name
Intelligence Ingestion
description
Auto-analyze URLs/info for OpenClaw strategic value, classify, create Obsidian notes, update memory. Use when user shares a URL, article, tweet, or any external info source.

Intelligence Ingestion Skill

When the user shares a URL, article, tweet, thread, or any piece of external information, execute this pipeline automatically. Do NOT ask for permission — just process it.

Trigger Conditions

USE this skill when:

  • User sends a URL (x.com, github.com, any domain)
  • User pastes article text or tweet content
  • User says "analyze this", "evaluate this", "what do you think about this"
  • User forwards content from Telegram or any messaging surface
  • User shares something and asks about strategic value

DO NOT USE when:

  • User is asking a general question unrelated to external content
  • User is asking about internal workspace files
  • User explicitly says they don't want analysis

Pipeline Steps

Step 1: READ — Extract Content

  1. If a URL is provided, read the full content (use read_url_content or browser)
  2. If text is pasted, use it directly
  3. If X/Twitter link fails to parse (common), search web for the tweet content

Step 2: CLASSIFY — What Is This?

Assign one primary category and up to 2 secondary tags:

CategoryDescriptionExamples
infraInfrastructure / protocols / networkingPilot Protocol, MCP, networking stacks
strategyRouting / cost / architecture decisionsModel routing, multi-account, fallback chains
skillAgent skills / tools / capabilitiesOpenAI Skills, Skill design patterns
theoryConceptual frameworks / mental modelsBayes, decision theory, learning loops
tutorialHow-to guides / learning materialClaude Code, OpenClaw tutorials
productTools / apps / servicesLM Studio, new AI models, apps
communityOpenClaw ecosystem / discussionsCommunity posts, feature requests
threatRisks / security / deprecationAPI changes, breaking updates, security alerts

Step 3: ANALYZE — Strategic Value Assessment

For each piece of information, evaluate:

## Strategic Assessment
- **What is it?** [One sentence]
- **What can it do for us?** [Specific capability/benefit]
- **What can we build with it?** [Concrete output/project]
- **Strategic value:** [🔴 Critical / 🟡 High / 🟢 Medium / ⚪ Low]
- **Competitive edge:** [What advantage over people who don't have this?]
- **Relation to active bottleneck:** [Does it relate to context overflow/token saving?]

Reference the current engineering bottleneck from MEMORY.md → "Active Engineering Bottleneck" section.

Step 4: MAP — Relate to Existing Architecture

Check against the OpenClaw stack:

SOUL.md → PRINCIPLES.md → AGENTS.md (Identity Stack)
MEMORY.md (System State + Bottleneck)
TOOLS.md (Coprocessors: Codex, Antigravity, LM Studio)
Pilot Protocol (Context Separation Layer - P0)

Determine which layer this information impacts and note dependencies/synergies with existing components.

Step 5: STORE — Write Obsidian Note

Create a note at:

/Volumes/T7 Shield/Obsidian_Vault/20_Intelligence/YYYYMMDD_AuthorOrSource_ShortTitle.md

Follow this template exactly:

# [Title]

**Source:** [Link](URL)
**Date:** YYYY-MM-DD
**Category:** [Primary Category] / [Secondary Tags]
**Strategic Value:** [🔴/🟡/🟢/⚪] + one-line reason
**Relation to Active Bottleneck:** [Yes/No + how]

---

## Summary
[2-3 paragraphs of core content]

## Key Takeaways
[Numbered list of actionable insights]

## Impact on OpenClaw Architecture
[How this relates to our stack]

## Action Items
[What to do next, if anything]

---

**Keke's Note:** [Opinionated analysis in Keke's voice — direct, no-BS, relate to 阳哥's goals]

Step 6: REMEMBER — Update Memory

  1. Always append to today's daily log: ~/.openclaw/workspace/memory/YYYY-MM-DD.md
  2. If strategic value is 🔴 Critical: Also update MEMORY.md (Pending Work or Active Bottleneck)
  3. If it suggests a new principle: Flag for potential PRINCIPLES.md update
  4. If it's a new tool/service: Flag for potential TOOLS.md update

Step 7: RESPOND — Summarize to User

Reply with a concise summary:

📥 已摄取: [Title]
📂 类别: [Category]
🎯 战略价值: [🔴/🟡/🟢/⚪] [One-line reason]
💾 已存档: Obsidian → 20_Intelligence/[filename]
📝 已记录: memory/YYYY-MM-DD.md
🔗 关联: [Which existing component it relates to]
⚡ 建议行动: [Next step, if any]

Edge Cases

  • Multiple URLs in one message: Process each separately, create separate Obsidian notes
  • Duplicate/similar content: Check if similar note exists, merge or reference instead of duplicating
  • Non-English content: Analyze in original language, write notes in Chinese (matching existing vault style)
  • Paywalled/inaccessible content: Note as "content unavailable" and work with whatever user provided
  • User provides their own analysis: Incorporate their judgment, don't overwrite — they know their system best

Quality Checklist

Before completing, verify:

  • [ ] Obsidian note created with correct filename format
  • [ ] Daily memory log updated
  • [ ] Source URL preserved in note
  • [ ] Strategic value assessed against current bottleneck
  • [ ] Keke's Note written with genuine analysis (not generic)
  • [ ] User received confirmation summary

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

补充不同宿主或平台的使用分布数据

能力 5

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

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

平台分布

OpenClaw

93.71%
按下载量换算5,293

安全审计

VirusTotal

可疑

ClawScan

可疑

Static analysis

未展示

权限和风险

操作浏览器

该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

安装前确认

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

来源信息

继续浏览同类 Skills