โ† Back to Skills Marketplace
bustes01

๐Ÿ“ก Knowledge & Trends Engine

by shake27 ยท GitHub โ†— ยท v1.0.0 ยท MIT-0
cross-platform โœ“ Security Clean
80
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install knowledge-and-trends-engine
Description
Knowledge accumulation and tech trend analysis engine. Periodically summarizes learned concepts from user interactions, parses content from videos/articles/i...
README (SKILL.md)

๐Ÿ“ก Knowledge & Trends Engine

Knowledge accumulation and tech trend analysis engine. Periodically summarizes learned concepts from user interactions, parses content from shared videos/articles/images, researches latest tech/news trends, and self-iterates via the shared component skills.

Core Workflows

Workflow 1: Concept Summarization (On-demand)

User says: "summarize what we've discussed recently" or "ๅธฎๆˆ‘ๆ€ป็ป“ๆœ€่ฟ‘่Š่ฟ‡็š„ๆฆ‚ๅฟต"

Step 1: Gather Memory Sources

  • Read memory/tier1-public/ for all skill stats and public knowledge entries
  • Read memory/concepts/ for concept files stored from previous sessions
  • Read recent daily notes: memory/YYYY-MM-DD.md (last 7 days)

Step 2: Identify Distinct Concepts Scan all sources and extract unique concepts. For each concept, determine:

  • Category: AI/ML, Finance, Development, Tools, Business, Science, etc.
  • Maturity: new / explored / mastered
  • Related concepts: cross-links to other learned concepts
  • Source: conversation, article, video, image, or self-discovered

Step 3: Generate Summary

# ๐Ÿ“ก Knowledge Summary ยท YYYY-MM-DD

## ๐Ÿ†• New This Period
### Concept A
- Source: conversation about financial modeling
- Key points: {3-5 bullet points}
- Related: Concept B, Concept C
- Status: explored โœ“

## ๐Ÿ“š Concepts in Progress
### Concept D
- Last discussed: YYYY-MM-DD
- Progress: understand basics, need deeper dive
- Suggested next: look into {related topic}

## ๐Ÿ† Mastered Concepts
### Concept E
- Sessions covered: 5
- Last reviewed: YYYY-MM-DD
- Confident: yes

Step 4: Store Use complex-memory-manager to store the summary:

  • T1: memory/tier1-public/concepts-summary-YYYY-MM.md (concept names, relationships, categories)
  • T2: memory/tier2-internal/concepts-detail-YYYY-MM.md (detailed notes, sources, encrypted if personal)

Workflow 2: Parse External Content (On-demand)

User shares content: "watch this video", "read this article", "analyze this image", "่ฟ™ไธชๆฆ‚ๅฟตไฝ ่ฎฐไฝ"

Step 1: Content Analysis

  • For articles (web_fetch URL): extract key concepts, arguments, data points
  • For videos (if URL to YouTube/transcript): extract main thesis, examples, conclusions
  • For images: describe visual content, extract any text, identify key concepts
  • For direct concept explanation: parse the user's textual explanation

Step 2: Concept Structuring For each extracted concept, create a structured note:

# memory/concepts/\x3Cconcept-slug>.md
concept:
  name: "\x3Cconcept name>"
  category: "\x3Ccategory>"
  source:
    type: article | video | image | conversation
    url: "\x3Csource URL if applicable>"
    date: "\x3CYYYY-MM-DD>"
  summary: "\x3C2-3 sentence explanation>"
  key_points:
    - "\x3Cpoint 1>"
    - "\x3Cpoint 2>"
  related_concepts: ["\x3Cconcept A>", "\x3Cconcept B>"]
  practical_applications: "\x3Chow this can be used>"

Step 3: Cross-Link

  • Check memory for existing related concepts
  • Add links in both directions
  • If concept already exists, merge/update rather than duplicate

Workflow 3: Trend Research (Periodic / On-demand)

User says: "what's new in tech" or "่ฐƒ็ ”ๆœ€ๆ–ฐ็š„ๆŠ€ๆœฏ่ถ‹ๅŠฟ"

Step 1: Define Research Scope

  • If user specified: use those keywords
  • If not: use recent concept categories from memory as seed topics
  • Always include: AI/ML, developer tools, security, finance tech

Step 2: Search & Gather

  • Use web_search with targeted queries for each scope
  • Priority sources: tech blogs (TechCrunch, ArsTechnica), research papers (arXiv), release notes (GitHub), financial news (Bloomberg, Reuters)
  • Limit to last 7 days of content unless user specifies otherwise

Step 3: Trend Analysis For each trend found:

trend:
  title: "\x3Ctrend name>"
  category: "\x3Ccategory>"
  significance: high | medium | low
  description: "\x3C1-2 sentence description>"
  impact: "\x3Cwho/what this affects>"
  source: "\x3CURL>"
  relation_to_existing: "\x3Chow this relates to known concepts>"

Step 4: Learn & Store

  • Store each significant new concept using Workflow 2 format
  • Update memory/tier1-public/trends-DATE.md with all findings
  • Use self-iteration-engine to log the research activity

Workflow 4: Periodic Self-Review (Cron-driven)

When triggered by schedule (default weekly):

  1. Review accumulated concepts from memory/concepts/
  2. Run trend research (Workflow 3) on categories where concepts are stored
  3. Generate combined summary (Workflow 1) including new trends
  4. Identify knowledge gaps โ€” concepts mentioned in trends that have no existing entry
  5. Log iteration via self-iteration-engine
  6. Propose learning topics for next week based on gaps

Memory Structure

memory/
โ”œโ”€โ”€ tier1-public/
โ”‚   โ”œโ”€โ”€ concepts-summary-YYYY-MM.md     # Monthly concept overview (T1)
โ”‚   โ””โ”€โ”€ trends-YYYY-MM-DD.md            # Trend research results (T1)
โ”œโ”€โ”€ tier2-internal/
โ”‚   โ””โ”€โ”€ concepts-detail-YYYY-MM.md      # Detailed encrypted notes (T2)
โ”œโ”€โ”€ concepts/
โ”‚   โ”œโ”€โ”€ \x3Cconcept-slug>.md               # Individual concept files
โ”‚   โ””โ”€โ”€ INDEX.md                        # Master index of all concepts
โ””โ”€โ”€ usage-logs/
    โ””โ”€โ”€ knowledge-and-trends-engine.md  # Delegated to self-iteration-engine

Query Examples

"ๆœ€่ฟ‘ๆˆ‘ไปฌ่Š่ฟ‡ไป€ไนˆๆฅ็€๏ผŸ" โ†’ Workflow 1 (concept summarization)
"็œ‹็œ‹่ฟ™็ฏ‡https://...  ๅธฎๆˆ‘ๆ็‚ผๆ ธๅฟƒๆฆ‚ๅฟต" โ†’ Workflow 2 (content parse)
"ๆœ€่ฟ‘AI้ข†ๅŸŸๆœ‰ไป€ไนˆๆ–ฐๅŠจๅ‘" โ†’ Workflow 3 (trend research)
"ๅฎšๆœŸๆ€ป็ป“" โ†’ Workflow 4 (periodic review)
"่ฟ™ไธชๆฆ‚ๅฟตไฝ ่ฎฐไฝ" + explanation โ†’ Workflow 2, Step 2-3 (direct store)

๐Ÿ“ก ็Ÿฅ่ฏ†่ถ‹ๅŠฟๅผ•ๆ“Ž

็Ÿฅ่ฏ†็งฏ็ดฏไธŽๆŠ€ๆœฏ่ถ‹ๅŠฟๅˆ†ๆžๅผ•ๆ“Žใ€‚ๅฎšๆœŸๆ€ป็ป“ไธŽ็”จๆˆท่ฎจ่ฎบ่ฟ‡็š„ๆฆ‚ๅฟต๏ผŒ่งฃๆž็”จๆˆทๅˆ†ไบซ็š„่ง†้ข‘/ๆ–‡็ซ /ๅ›พ็‰‡ๅ†…ๅฎน๏ผŒ่ฐƒ็ ”ๆœ€ๆ–ฐๆŠ€ๆœฏไธŽๆ–ฐ้—ป็ƒญ็‚น๏ผŒๅนถ้€š่ฟ‡ๅ…ฑไบซ็ป„ไปถๆŠ€่ƒฝๅฎž็Žฐ่‡ช่ฟญไปฃใ€‚

ๆ ธๅฟƒๅทฅไฝœๆต

ๅทฅไฝœๆต1๏ผšๆฆ‚ๅฟตๆ€ป็ป“๏ผˆๆŒ‰้œ€๏ผ‰

็”จๆˆท่ฏด๏ผš"ๆ€ป็ป“ๆœ€่ฟ‘่Š่ฟ‡็š„ๆฆ‚ๅฟต"

็ฌฌไธ€ๆญฅ๏ผšๆ”ถ้›†่ฎฐๅฟ†ๆบ

  • ่ฏปๅ– memory/tier1-public/ ไธญ็š„ๆŠ€่ƒฝ็ปŸ่ฎกๅ’Œๅ…ฌๅผ€็Ÿฅ่ฏ†
  • ่ฏปๅ– memory/concepts/ ไธญ็š„ๆฆ‚ๅฟตๆ–‡ไปถ
  • ่ฏปๅ–ๆœ€่ฟ‘7ๅคฉ็š„ๆฏๆ—ฅ็ฌ”่ฎฐ

็ฌฌไบŒๆญฅ๏ผš่ฏ†ๅˆซ็‹ฌ็ซ‹ๆฆ‚ๅฟต ๆ‰ซๆๆ‰€ๆœ‰ๆบๆๅ–ๅ”ฏไธ€ๆฆ‚ๅฟต๏ผŒๅˆคๆ–ญ๏ผš็ฑปๅˆซใ€ๆˆ็†Ÿๅบฆใ€ๅ…ณ่”ๆฆ‚ๅฟตใ€ๆฅๆบ

็ฌฌไธ‰ๆญฅ๏ผš็”Ÿๆˆๆ€ป็ป“ ๆŒ‰ไปฅไธ‹็ป“ๆž„่พ“ๅ‡บ๏ผš

  • ๐Ÿ†• ๆœฌๆœŸๆ–ฐๆฆ‚ๅฟต
  • ๐Ÿ“š ่ฟ›่กŒไธญ็š„ๆฆ‚ๅฟต
  • ๐Ÿ† ๅทฒๆŽŒๆก็š„ๆฆ‚ๅฟต

็ฌฌๅ››ๆญฅ๏ผšๅญ˜ๅ‚จ ๅง”ๆ‰˜ complex-memory-manager ๅญ˜ๅ‚จๆ€ป็ป“

ๅทฅไฝœๆต2๏ผš่งฃๆžๅค–้ƒจๅ†…ๅฎน๏ผˆๆŒ‰้œ€๏ผ‰

็”จๆˆทๅˆ†ไบซๅ†…ๅฎนๆ—ถ๏ผšๆ–‡็ซ URLใ€่ง†้ข‘URLใ€ๅ›พ็‰‡ใ€ๆˆ–็›ดๆŽฅๆฆ‚ๅฟต่งฃ้‡Š

็ฌฌไธ€ๆญฅ๏ผšๅ†…ๅฎนๅˆ†ๆž

  • ๆ–‡็ซ  โ†’ web_fetch ๆๅ–ๅ…ณ้”ฎๆฆ‚ๅฟตใ€่ฎบๆฎใ€ๆ•ฐๆฎ
  • ่ง†้ข‘ โ†’ ๅฆ‚ๆœ‰ๆ–‡ๅญ—็จฟๅˆ™ๆๅ–ไธปๆ—จใ€็คบไพ‹ใ€็ป“่ฎบ
  • ๅ›พ็‰‡ โ†’ ๆ่ฟฐ่ง†่ง‰ๅ†…ๅฎน๏ผŒๆๅ–ๆ–‡ๅญ—๏ผŒๆ‰พๅ‡บๅ…ณ้”ฎๆฆ‚ๅฟต
  • ็›ดๆŽฅ่งฃ้‡Š โ†’ ่งฃๆž็”จๆˆท็š„ๆ–‡ๅญ—่ฏดๆ˜Ž

็ฌฌไบŒๆญฅ๏ผšๆฆ‚ๅฟต็ป“ๆž„ๅŒ– ๆฏไธชๆฆ‚ๅฟตๅˆ›ๅปบ็ป“ๆž„ๅŒ–็ฌ”่ฎฐ๏ผŒๅŒ…ๆ‹ฌๅ็งฐใ€็ฑปๅˆซใ€ๆฅๆบใ€ๆ‘˜่ฆใ€่ฆ็‚นใ€ๅ…ณ่”ๆฆ‚ๅฟตใ€ๅฎž้™…ๅบ”็”จ

็ฌฌไธ‰ๆญฅ๏ผšไบคๅ‰้“พๆŽฅ ๆฃ€ๆŸฅๅทฒๆœ‰ๆฆ‚ๅฟต๏ผŒๅŒๅ‘้“พๆŽฅ๏ผ›่‹ฅๅทฒๅญ˜ๅœจๅˆ™ๅˆๅนถ/ๆ›ดๆ–ฐ่€Œ้ž้‡ๅค

ๅทฅไฝœๆต3๏ผš่ถ‹ๅŠฟ่ฐƒ็ ”๏ผˆๅฎšๆœŸ/ๆŒ‰้œ€๏ผ‰

็”จๆˆท่ฏด๏ผš"ๆœ€่ฟ‘ๆœ‰ไป€ไนˆๆŠ€ๆœฏ็ƒญ็‚น"

็ฌฌไธ€ๆญฅ๏ผš็กฎๅฎš่ฐƒ็ ”่Œƒๅ›ด ไฝฟ็”จ็”จๆˆทๆŒ‡ๅฎšๅ…ณ้”ฎ่ฏๆˆ–ๅทฒๆœ‰ๆฆ‚ๅฟต็ฑปๅˆซไฝœไธบ็งๅญ

็ฌฌไบŒๆญฅ๏ผšๆœ็ดขๆ”ถ้›† web_search ๅฎšๅ‘ๆœ็ดข๏ผŒไผ˜ๅ…ˆๆฅๆบ๏ผšTechCrunchใ€ArsTechnicaใ€arXivใ€GitHubใ€Bloombergใ€Reuters

็ฌฌไธ‰ๆญฅ๏ผš่ถ‹ๅŠฟๅˆ†ๆž ๅฏนๆฏไธช่ถ‹ๅŠฟ่ฎฐๅฝ•๏ผšๆ ‡้ข˜ใ€็ฑปๅˆซใ€้‡่ฆๆ€งใ€ๆ่ฟฐใ€ๅฝฑๅ“ใ€ๆฅๆบใ€ไธŽ็Žฐๆœ‰ๆฆ‚ๅฟต็š„ๅ…ณ็ณป

็ฌฌๅ››ๆญฅ๏ผšๅญฆไน ไธŽๅญ˜ๅ‚จ ไฝฟ็”จๅทฅไฝœๆต2ๆ ผๅผๅญ˜ๅ‚จๆ–ฐๆฆ‚ๅฟต๏ผŒๆ›ดๆ–ฐ่ถ‹ๅŠฟๆ–‡ไปถ

ๅทฅไฝœๆต4๏ผšๅฎšๆœŸ่‡ชๅฎก๏ผˆCron้ฉฑๅŠจ๏ผ‰

้ป˜่ฎคๆฏๅ‘จๆ‰ง่กŒ๏ผš

  1. ๅฎกๆŸฅ memory/concepts/ ไธญ็š„็งฏ็ดฏๆฆ‚ๅฟต
  2. ๅœจๆœ‰ๆฆ‚ๅฟตๅญ˜ๅ‚จ็š„็ฑปๅˆซไธŠ่ฟ่กŒ่ถ‹ๅŠฟ่ฐƒ็ ”
  3. ็”ŸๆˆๅŒ…ๅซๆ–ฐ่ถ‹ๅŠฟ็š„ๅˆๅนถๆ€ป็ป“
  4. ่ฏ†ๅˆซ็Ÿฅ่ฏ†็›ฒๅŒบ
  5. ้€š่ฟ‡ self-iteration-engine ่ฎฐๅฝ•่ฟญไปฃ
  6. ๅŸบไบŽ็›ฒๅŒบๆๅ‡บไธ‹ๅ‘จๅญฆไน ไธป้ข˜

่ฎฐๅฟ†็ป“ๆž„

memory/
โ”œโ”€โ”€ tier1-public/
โ”‚   โ”œโ”€โ”€ concepts-summary-YYYY-MM.md     # ๆœˆๅบฆๆฆ‚ๅฟตๆฆ‚่งˆ๏ผˆๅ…ฌๅผ€๏ผ‰
โ”‚   โ””โ”€โ”€ trends-YYYY-MM-DD.md            # ่ถ‹ๅŠฟ่ฐƒ็ ”็ป“ๆžœ๏ผˆๅ…ฌๅผ€๏ผ‰
โ”œโ”€โ”€ tier2-internal/
โ”‚   โ””โ”€โ”€ concepts-detail-YYYY-MM.md      # ่ฏฆ็ป†ๅŠ ๅฏ†็ฌ”่ฎฐ๏ผˆๅ†…้ƒจ๏ผ‰
โ”œโ”€โ”€ concepts/
โ”‚   โ”œโ”€โ”€ \x3Cๆฆ‚ๅฟตslug>.md                    # ็‹ฌ็ซ‹ๆฆ‚ๅฟตๆ–‡ไปถ
โ”‚   โ””โ”€โ”€ INDEX.md                        # ๆฆ‚ๅฟตๆ€ป็ดขๅผ•
โ””โ”€โ”€ usage-logs/
    โ””โ”€โ”€ knowledge-and-trends-engine.md  # ็”ฑself-iteration-engine็ฎก็†

ๆŸฅ่ฏข็คบไพ‹

"ๆœ€่ฟ‘ๆˆ‘ไปฌ่Š่ฟ‡ไป€ไนˆๆฅ็€๏ผŸ" โ†’ ๅทฅไฝœๆต1๏ผˆๆฆ‚ๅฟตๆ€ป็ป“๏ผ‰
"็œ‹็œ‹่ฟ™็ฏ‡https://...  ๅธฎๆˆ‘ๆ็‚ผๆ ธๅฟƒๆฆ‚ๅฟต" โ†’ ๅทฅไฝœๆต2๏ผˆๅ†…ๅฎน่งฃๆž๏ผ‰
"ๆœ€่ฟ‘AI้ข†ๅŸŸๆœ‰ไป€ไนˆๆ–ฐๅŠจๅ‘" โ†’ ๅทฅไฝœๆต3๏ผˆ่ถ‹ๅŠฟ่ฐƒ็ ”๏ผ‰
"ๅฎšๆœŸๆ€ป็ป“" โ†’ ๅทฅไฝœๆต4๏ผˆๅฎšๆœŸ่‡ชๅฎก๏ผ‰
"่ฟ™ไธชๆฆ‚ๅฟตไฝ ่ฎฐไฝ" + ่งฃ้‡Š โ†’ ๅทฅไฝœๆต2๏ผˆ็›ดๆŽฅๅญ˜ๅ‚จ๏ผ‰
Usage Guidance
Treat this as an incomplete review, not a full approval. Re-run the scan where metadata.json and the artifact directory can be read before installing.
Capability Assessment
โ„น Purpose & Capability
Unable to inspect metadata.json or artifact contents because local file-read commands failed before execution; no artifact-backed purpose mismatch was available to review.
โ„น Instruction Scope
Unable to inspect SKILL.md or runtime instructions; no evidence-backed instruction-scope concern can be reported.
โ„น Install Mechanism
Unable to inspect install specs or manifests; no evidence-backed install concern can be reported.
โ„น Credentials
Unable to inspect declared capabilities or file contents; proportionality could not be confirmed from artifacts.
โ„น Persistence & Privilege
Unable to inspect artifacts for persistence, credential use, or privilege requests; no evidence-backed concern can be reported.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install knowledge-and-trends-engine
  3. After installation, invoke the skill by name or use /knowledge-and-trends-engine
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release: concept accumulation, content parsing, trend analysis, periodic review
Metadata
Slug knowledge-and-trends-engine
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is ๐Ÿ“ก Knowledge & Trends Engine?

Knowledge accumulation and tech trend analysis engine. Periodically summarizes learned concepts from user interactions, parses content from videos/articles/i... It is an AI Agent Skill for Claude Code / OpenClaw, with 80 downloads so far.

How do I install ๐Ÿ“ก Knowledge & Trends Engine?

Run "/install knowledge-and-trends-engine" in the OpenClaw or Claude Code chat to install it in one step โ€” no extra setup required.

Is ๐Ÿ“ก Knowledge & Trends Engine free?

Yes, ๐Ÿ“ก Knowledge & Trends Engine is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does ๐Ÿ“ก Knowledge & Trends Engine support?

๐Ÿ“ก Knowledge & Trends Engine is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created ๐Ÿ“ก Knowledge & Trends Engine?

It is built and maintained by shake27 (@bustes01); the current version is v1.0.0.

๐Ÿ’ฌ Comments