expert-agent-builder
Build expert agents from documented domains. Automates the knowledge pipeline: fetch docs, chunk large files, generate summaries, extract beliefs, derive deeper conclusions, review and repair, build FTS5 search indexes.
Install
uv tool install ftl-expert-build
Requires ftl-reasons and either claude or gemini CLI on PATH.
Quick Start
# Bootstrap a new expert agent
expert-build init rhcsa --domain "Red Hat Certified System Administrator"
# Fetch documentation
expert-build fetch-docs https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/ --depth 2
# Generate entries from sources
expert-build summarize --parallel 4
# Extract beliefs for review
expert-build propose-beliefs --parallel 4
# Edit proposed-beliefs.md: LLM marks each as [ACCEPT] or [REJECT]
expert-build accept-beliefs
# Run the full pipeline end-to-end
expert-build pipeline --url https://docs.example.com --parallel 4
Commands
| Command | Description |
|---|---|
init |
Bootstrap a new expert agent repo |
fetch-docs |
Fetch documentation from URLs |
chunk-pdf |
Split PDFs into section-based entries |
chunk-docs |
Split large .md/.py/.txt files by structural boundaries |
summarize |
Generate entries from source documents via LLM |
propose-beliefs |
Extract candidate beliefs from entries via LLM |
accept-beliefs |
Import accepted beliefs into reasons.db |
cert-coverage |
Map certification objectives to beliefs |
exam |
Run practice questions, discover knowledge gaps |
pipeline |
Run end-to-end EEM construction (9 stages) |
derive-review-repair |
Run derive/review/repair loop on existing beliefs |
index-sources |
Build FTS5 chunks database for RAG search |
status |
Show pipeline progress |
Pipeline Stages
1. Ingest (fetch-docs / chunk-pdf)
2. Summarize (LLM summaries of source documents)
3. Extract (propose-beliefs + accept-beliefs)
4-7. Derive → Review → Repair → Deduplicate (convergence loop)
8. Export (network.json + README card)
9. Index (FTS5 search database)
# Full pipeline with parallel LLM calls and recursive source discovery
expert-build pipeline --url https://docs.example.com --parallel 4 --recursive
# Resume after a crash
expert-build pipeline --resume
# Run just the knowledge refinement loop
expert-build derive-review-repair --rounds 5
Working with Large Repos
# Summarize a repo with nested directories
expert-build summarize --input-dir ~/git/my-project --recursive --parallel 4
# Chunk large files before summarizing
expert-build chunk-docs --input-dir ~/git/my-project --recursive
# Build search index
expert-build index-sources --input-dir ~/git/my-project --recursive
expert-build index-sources --input-dir entries/ --recursive --type summary
# Query with reasons
reasons search-sources "kubernetes scheduling" --db rag_fts.db
reasons ask "How does pod scheduling work?" --full-sources rag_fts.db
Features
- Parallel LLM calls —
--parallel Non summarize, propose-beliefs, and pipeline - Recursive file discovery —
--recursivefor nested directory structures - Cost tracking — token counts and costs printed after every command
- Crash resilience — incremental writes, pipeline state file with
--resume - JSON pseudo-tool-calling — structured LLM output with retry for all parsing stages
- Source provenance — every entry tracks its source file, URL, and document ID
- FTS5 indexing — build search indexes compatible with
reasons search-sources
Metadata
Release files for ftl-expert-build 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| ftl_expert_build-0.3.0.tar.gz | 910.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ftl_expert_build-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 953.5 kB
Release files / ftl_expert_build-0.3.0.tar.gz
| Download URL | ftl_expert_build-0.3.0.tar.gz |
|---|---|
| Size | 910.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d57b8612c35e0c621df824172123bae268cb3eca17602a0d5f8180bff73fa1de
|
|
BLAKE2b-256 checksum How to use checksums |
b1e88b4a4e493f7e546552e0cc19c944d3d5ed07d55b1d8112d85dcade58e007
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.12
|
Release files / ftl_expert_build-0.3.0-py3-none-any.whl
| Download URL | ftl_expert_build-0.3.0-py3-none-any.whl |
|---|---|
| Size | 42.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f9d0a568697adf7b1192fb1748041cbaec00390e0d65a950a2772e7895881195
|
|
BLAKE2b-256 checksum How to use checksums |
3343a365be0dc4fe299a7760d7a5d9226a1bdd5fe079f32caa9d2d5987830358
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.12
|
Security for ftl-expert-build 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.