Browse
Installable packages, the resource types built into kdeps, and the versioned assets kdeps runs on, in one catalog. The colored badge on each entry says which kind it is.
404 entries
kdeps harness: invoke-example
kdeps kdeps-component: jina_rerank
Rerank a list of documents by relevance to a query using Jina AI's reranking API. Requires JINA_API_KEY.
kdeps event: judge-iterations
kdeps event: judge-max-rounds
kdeps harness: judge-roster-system
kdeps harness: judge-system
Settle your review of the candidate output. Must be called exactly once, when your review is complete.
kdeps command: judges
kdeps command: kartographer
kdeps manifest: manifests
kdeps command: knowledge
kdeps template: knowledge
kdeps harness: knowledge-extract-system
Read a project card from the knowledge vault: type, status, next step, updated date, and the places on disk it covers (repo, folder, workflow). Cards are the only home of status. Without a name, returns the working directory's project card (created on first use).
Set a card's status and/or next step and stamp its updated date. This is the only place status and the next step are written: never put them in a note. Without a name, updates the working directory's project card (created on first use). Status archived moves the project folder to archive/. add_search_folder links a folder outside the project (docs, a shared library) so recall and search_local cover it too, and indexes it.
Save a new note in the knowledge vault: one idea per note, with frontmatter (type, status, created, summary, tags, links). Refuses a title that already has a note - one home per fact, so edit that note instead. Use for a decision, a gotcha, a concept or a tool worth remembering beyond this session; it goes in the project's folder unless scope says otherwise. Status and next steps go to the card instead.
Find the notes in the knowledge vault related to a query, by walking the vault's link graph from the words of the query (no model involved). Returns note paths with their one-line summaries, best first, within a small token budget. Each turn already carries a recall for the user's request; call this to look up something else (a project, a decision, an error). Then read only the notes you need with read_file.
kdeps command: konfig
kdeps theme: linux
kdeps kdeps-component: list_files
List files and directories in a given directory path. Returns names and types (file/dir). Use to discover project structure before reading or editing files. Omit path to list the current working directory.
llama.cpp llama-server serving GGUF weights over OpenAI-compatible /v1
Official llama.cpp server image (OpenAI-compatible /v1) for GGUF
kdeps model: llamafile
Self-contained .llamafile binary serving OpenAI-compatible /v1
kdeps kdeps-component: load_document
Load a document file and return its content as text. Supports PDF (langchaingo pdf loader), DOCX/EPUB/RTF/ODT (pandoc), HTML (goquery, lynx), CSV, text, directory, notion, markdown (textutil). Use for reading documents into the conversation for analysis or RAG pipelines. Returns document content with optional splitting into chunks. Requires: source (absolute file path). Optional: type (pdf, csv, html, text - auto-detected from extension), columns (CSV column filter), password (encrypted PDF), chunkSize (split into chunks of N characters), chunkOverlap, chunkSplitter (recursive, token, markdown).
Load the full instructions for a named skill. Call this when the user's task matches one of the skills listed in <available_skills>. Returns the skill's complete instructions to follow.
The `load_document` component reads a file, URL, or directory into structured `Document` objects - plain text plus metadata - and optionally splits them into chunks. It is the ingestion step of a RAG pipeline: load, then feed the output into the `vector_store` or `embedding` component for indexing. It is a kdeps component from the `components` asset set: call it with a `component:` resource, no install step. Its call is the kdeps API's `load_document` tool, which runs the native loader executor. A workflow that uses `loader:` directly - primary or in a `before:`/`after:` step - is rejected.