Przejdź do treści
Biblioteka skilli
AI i agenci · Budowanie i kod

knowledge-ingest

/knowledge-ingest

Buduje lokalną bazę wiedzy do wyszukiwania RAG, zamieniając dokumenty, kod i zgłoszenia w strony z podanymi źródłami.

Repozytorium
research-lab ↗
Licencja
MIT
Ostatnia zmiana repozytorium
08.11.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
3
Skrypty
1
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 08.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co sprawdzić przed instalacją
  • 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.

Skrypty: scripts/kb_lint.py

Co robi i kiedy

Buduje lokalną bazę wiedzy do wyszukiwania RAG, zamieniając dokumenty, kod i zgłoszenia w strony z podanymi źródłami.

Wyzwalacze z opisu

remember thisadd to the knowledge basebuild a page for this repo

Argumenty

/knowledge-ingest [repo | <url or path> | <topic>]
Oryginalny opis (EN)

Builds the local knowledge base for retrieval (RAG) together with its curated router. Use when the user says "remember this", "add to the knowledge base", "build a page for this repo", after reading docs, wiki pages, code or tickets that will matter again, after a research round whose conclusions matter beyond its project, or when knowledge-search reported a miss. Distills sources into chunk-friendly topic and project pages with a source on every fact, registers them in the topic map with keywords and section pointers, embeds the new chunks into the vector store, keeps every file inside its si

Jak działa

  1. 1. Read (cheaply)
  2. 2. Distill into the page
  3. 3. Register in the router (same step, not later)
  4. 4. Budgets (keep the router fast)
  5. 5. Write for retrieval
  6. 6. Lint, index, commit, report
Sekcje z nagłówków SKILL.md, w oryginale · 79 linii, 814 słów
Podgląd SKILL.md
---
name: knowledge-ingest
description: >
  Builds the local knowledge base for retrieval (RAG) together with its curated router. Use when the user says "remember this", "add to the knowledge base", "build a page for this repo", after reading docs, wiki pages, code or tickets that will matter again, after a research round whose conclusions matter beyond its project, or when knowledge-search reported a miss. Distills sources into chunk-friendly topic and project pages with a source on every fact, registers them in the topic map with keywords and section pointers, embeds the new chunks into the vector store, keeps every file inside its size budget, and commits.
argument-hint: "[repo | <url or path> | <topic>]"
---

# knowledge-ingest - every page it writes is retrievable from day one

Target: `~/.claude/research-lab/knowledge/` (below: KB). Layout and the topic-block format are
described in the knowledge-search skill. The rule of this skill: **no page without a router entry, no
router entry without a page or a source.**

Argument: `$ARGUMENTS`
- `repo` (or empty inside a git repo without a project page) -> build `KB/projects/<repo>.md`.
- a URL or path -> distill that source into the matching topic.
- a topic name -> collect what this conversation established about it.
- a research folder -> promote the durable conclusions of its `KB/KNOWLEDGE.md` (not the
  journal) into topic pages, each fact pointing back to the experiment or review.

## 1. Read (cheaply)
- Small source (< ~30 KB): read it directly.
- Large source, many pages, or a whole repo: delegate to a subagent (`Explore`) with the question
  "what will someone need to know again?" and take back facts with citations. Do not pull the whole thing into the main context.
- Pages the map marks ⛔: do not crawl them; record the link only.
- Web sources, dates, cross-checks and what wins a disagreement: [SOURCES.md](SOURCES.md).

## 2. Distill into the page
Topic page `KB/topics/<slug>.md`, sections in this order (skip empty ones):
`## Summary` (3-5 lines) · `## Facts` · `## How to` · `## Pitfalls` · `## Contradictions` ·
`## Open questions` · `## Sources`.
- Every fact is one line ending with its source: `(src: <url or path:line> ✅)`.
- Write for retrieval: one subject per `##`/`###` section, a specific heading with the words a
  question would use, sections short enough to stand alone as a chunk (~1.5 KB).
- Do not copy long passages; restate in your own words, quote at most a short phrase.
- Contradicting sources: keep both, say which one wins and why (code > ADR > docs > wiki > chat).
- Say what a section is when it is not a plain sourced fact, on a line under its heading:
  `kind: measurement · scope: ES Q3 2026, spread 0.25 · date: 2026-11-07` (kinds: measurement,
  conclusion, conjecture, expectation, snippet). A fact that turns out wrong or is replaced is not
  deleted: its section gets `status: superseded · supersedes: <old heading>` or `status: invalid`
  with the reason, so search leaves it out but the history stays. Promoted research facts carry the
  kind and scope of the research they came from.
- Never store secrets, credentials or personal data. Sensitive pages: store a pointer and the
  note "restricted, ask the owner".

Project page `KB/projects/<repo>.md` (from the repo's README, CLAUDE.md, CONTRIBUTING, docs/,
build files and CI config):
`## Purpose` · `## Layout` (entry points with paths) · `## Commands` (exact build / test / lint
lines) · `## Conventions` (with the source file) · `## Decisions` (ADRs, links) · `## Pitfalls` ·
`## Sources`.

## 3. Register in the router (same step, not later)
In `KB/topic-map.md`, create or extend the topic block:
- `keywords:` everything a future question might contain: synonyms, the user's language, module
  and file names, issue key prefixes, abbreviations.
- `read first:` `file#section` pointers to the exact sections, most useful first.
- `sources:` with status marks ✅ / 🔎 / ⛔.
- `updated:` today.
A project page is also registered as a topic block (`## Project: <repo>`).

## 4. Budgets (keep the router fast)
| File | Budget | When exceeded |
|---|---|---|
| topic block in the map | <= 8 lines | split the topic |
| `topic-map.md` | <= 25 KB | move topics into `KB/map/<area>.md` and leave one block per area in the top map (hierarchical routing) |
| topic page | <= 40 KB | split into subtopic pages, each with its own block |
| project page | <= 15 KB | move details into topic pages, keep pointers |

## 5. Write for retrieval
Every chunk is indexed with its page's title and summary, so give a page a specific title and, if
its first sentence does not say what it is about, a `summary: ...` line near the top. State relations
plainly ("billing-api depends on Kafka", "X replaces Y"): the entity graph reads these sentences and
answers "what breaks if Kafka goes down" from them. Keep periods in the title or headings ("Q3 2026"):
questions about a period filter on them.

## 6. Lint, index, commit, report
Run `python3 "${CLAUDE_SKILL_DIR}/scripts/kb_lint.py"`. The `kb_autoindex` hook has already
embedded the new chunks; without hooks run
`python3 "${CLAUDE_SKILL_DIR}/../knowledge-search/scripts/kb_rag.py" index`. Fix every ERROR
(broken pointer, unroutable page, block without keywords) before committing; act on WARN
budgets as the table above says.
If KB is a git repository: `git -C KB add -A && git -C KB commit -m "kb: <topic> (+N facts)"`.
Report in two lines: what was added (pages, facts, keywords) and the new router keywords.
If `.router-log.tsv` shows misses this ingest closes, say which.
Pliki w paczce (3)
  • SKILL.md 5 KB
  • SOURCES.md 2 KB
  • scripts/kb_lint.py 5 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · nikserbur/research-lab90MIT
keshrath/agent-knowledge100MIT
cogni-work/insight-wave100Apache-2.0
evolution-foundation/evo-nexus100Apache-2.0

Migawka bazy z 13.11.2026 · wersja paczki 373f09804e8f (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100rag-knowledge
    Zasila i przeszukuje bazę wiedzy RAG: dodaje dokumenty, zarządza kolekcjami i konfiguruje źródła Google Drive lub S3.
  • 100knowledge-connect
    Zarządza integracją wiedzy przez MCP, bazy wektorowe i konektory A2A: łączy z bazą wiedzy, indeksuje dokumentację i pliki projektu, odpytuje bazę wektorową i buduje potok RAG.
  • 100knowledge-rag
    Dodaje i aktualizuje wpisy TerMinal Knowledge Base oparte na lokalnym serwerze MCP knowledge-rag: wyszukiwanie semantyczne po dokumentach, wczytywanie URL i dokumentów oraz konfiguracja typu wpisu RAG.
  • 100rag-pipeline
    Buduje pipeline RAG lub własną wyszukiwarkę na Discover API Bright Data, wykorzystując wyniki z sieci i sparsowaną treść stron jako warstwę wyszukiwania dla LLM lub bazy wektorowej.
  • 100wiki-ingest
    Kompiluje artykuły, dokumenty i notatki w uporządkowaną bazę wiedzy wiki, pojedynczo lub wsadowo.
  • 90rag-architect
    Projektuje potoki RAG, optymalizuje strategie wyszukiwania, dobiera modele embeddingów i buduje wyszukiwanie wektorowe w bazie wiedzy.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.