개인지식 시스템

지정된 접근 문자를 입력하면 이 브라우저에서 열람이 허용됩니다.

정적 사이트용 간단 게이트입니다. 강한 보안은 Cloudflare Access를 권장합니다.

← All Notes

Agent Skills Agent Skills 70-agent-skills/hermes/knowledge-repo-ingest.md

knowledge repo ingest

Hermes Workflow: knowledge-repo-ingest

Trigger examples:

  • "지식에 쌓아줘"
  • "이거 지식에 쌓아줘"
  • "이 대화 PKM에 반영해줘"
  • "이 유튜브 분석해서 지식저장소에 넣어줘"
  • "방금 나온 인사이트 저장해줘"
  • "knowledge repo 업데이트해줘"
  • "agent-knowledge-base에 저장해줘"

Repo Wrapper

  • Canonical repo: https://github.com/malda231125/agent-knowledge-base
  • Default local path: /opt/data/agent-knowledge-base
  • The Astro/Cloudflare Pages wrapper is a read layer over the Markdown graph. The Markdown folders and AGENTS.md remain the source of truth.

Workflow

  1. Locate or clone the repo wrapper. If /opt/data/agent-knowledge-base is missing and GitHub auth is available, clone the canonical repo.
  2. Read README.md for the human-facing architecture and wrapper conventions.
  3. Read AGENTS.md. Treat it as the source of truth for folder semantics and data-loading rules.
  4. Read the relevant schema in 60-schemas/ before creating a new note type.
  5. Identify the input type: source, conversation, insight, decision, map, or project context.
  6. Route the input through the repository's data-loading contract:
    • external source / YouTube / article / paper / meeting / chat -> primary artifact in 10-sources/
    • reusable non-obvious takeaway -> 20-insights/
    • durable term/framework/model -> 30-concepts/
    • durable user/team choice -> 50-decisions/
    • topic navigation / MOC -> 40-maps/
    • unclassified raw material only temporarily -> 00-inbox/
  7. Search existing concept notes and aliases before creating new concepts.
  8. Create/update the knowledge graph, not just one file: source -> claims -> concepts/insights/decisions/maps.
  9. Preserve Obsidian wikilinks and YAML frontmatter.
  10. Run a lightweight consistency check:
  • required frontmatter exists
  • no obvious duplicate concept titles
  • durable claims cite sources
  • raw source, interpretation, and decisions are separated
  • folder choice matches the data-loading contract
  1. Show git diff to the user when interactive.
  2. Commit with a clear prefix when approved or when explicitly asked to commit.

Default Commit Prefixes

  • source: add ...
  • insight: add ...
  • concept: update ...
  • decision: record ...
  • map: update ...