Skip to content

feat: add search-retrieval, memory-protocol, and obsidian-vault skills#34

Open
alexeyaudi wants to merge 1 commit into
softaworks:mainfrom
alexeyaudi:main
Open

feat: add search-retrieval, memory-protocol, and obsidian-vault skills#34
alexeyaudi wants to merge 1 commit into
softaworks:mainfrom
alexeyaudi:main

Conversation

@alexeyaudi
Copy link
Copy Markdown

New Skills from Gemini CLI Agent System

Three new skills extracted and generalized from a production Gemini CLI agent setup.

🔍 search-retrieval

Intelligent 4-tool decision tree for external data tasks:

  • Google Grounding → facts, news synthesis
  • SearXNG → structured search with URLs (YouTube, science, news)
  • Gemini fetch → read a specific URL
  • Firecrawl → JS/SPA scraping (use sparingly, 500-req limit)

Includes anti-hallucination rules for links and a critical HTTP encoding note (Python requests over curl).

🧠 memory-protocol

Persistent agent memory via a structured Markdown file:

  • Read-before-answer / write-after-task cycle
  • Structured entry format with scope + expiry
  • /dream consolidation command for files > 200 lines
  • Replace-not-append rule to prevent duplicates

📚 obsidian-vault

Two-layer knowledge architecture for Obsidian + AI agents:

  • Raw Layer (Inbox, Reports, etc.) — type: raw_material, agent write zone
  • Wiki Layer — read-only for agents, written only by Wiki Compiler
  • Three-stage pipeline: Librarian → Wiki Compiler → Semantic Linker
  • Frontmatter format, tag rules, file routing from Inbox

Each skill follows the existing README.md + SKILL.md format from skills/gemini/.

Three new skills extracted from a Gemini CLI agent system:
- search-retrieval: 4-tool decision tree (Grounding/SearXNG/fetch/Firecrawl)
- memory-protocol: persistent agent memory with /dream consolidation
- obsidian-vault: two-layer Raw/Wiki architecture for knowledge bases
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant