Skill rating
26 skills. The A–F grade combines safety (60%) and quality (40%); tests add a bonus. The rating refreshes automatically from open catalogs.
ManufacturingLogistics and warehouseProcurementQuality controlContact centreField serviceFinanceCustomer supportindustry shortcuts
| # | Grade | Skill | Score ▾ | Safety | Quality | Process | Tests | Popularity | Updated |
|---|---|---|---|---|---|---|---|---|---|
| 1 | A | Extract text, tables, metadata, and images from 107 document formats (PDF, Office, images, HTML, email, archives, academic) using Xberg. Use when writing code that calls Xberg APIs in Python, Node.js/ | 100 | 92 | C | — | — | 11 d ago | |
| 2 | A | Use when extracting tabular data from PDFs, spreadsheets, or images. Covers layout-aware table detection, table model selection, output formats (markdown / JSON cells), and known limits. | 100 | 91 | B | — | — | 11 d ago | |
| 3 | A | Use when extracting from many files at once with shared config, bounded parallelism, per-file overrides, and error recovery. Covers the `batch` command, `--file-configs`, `--max-concurrent`, and outpu | 100 | 91 | C | — | — | 11 d ago | |
| 4 | A | Use when extracting keywords (YAKE/RAKE) from documents — and, secondarily, when detecting document language or generating embeddings for RAG and search. Covers the keyword config (and its feature gat | 100 | 88 | D | — | — | 11 d ago | |
| 5 | A | Use when extracting text from scanned PDFs, photographed pages, or images that have no embedded text layer. Covers OCR backends, language packs, force-OCR, and performance tuning. | 100 | 88 | C | — | — | 11 d ago | |
| 6 | A | Use when choosing an output format for extracted documents — plain text, markdown, djot, HTML, JSON, or DocTags. Maps consumer (LLM, parser, archive) to the right `--format` / `--content-format` pair. | 100 | 88 | C | — | — | 11 d ago | |
| 7 | A | Use when splitting extracted text into chunks for LLM context windows or RAG ingestion. Covers chunk size, overlap, markdown/yaml/semantic chunkers, tokenizer-based sizing, and the standalone `chunk` | 100 | 88 | C | — | — | 11 d ago | |
| 8 | C | Per-format Xberg extractors (Office XML, PDF, archives, ...): parsers, security budgets, metadata helpers. Use when changing or adding one. | 100 | 54 | C | — | — | 11 d ago | |
| 9 | C | Xberg plugin traits, typed registries, priority collisions, lifecycle and Alef Python plugin bridges. Use for plugin-system work, not parsing. | 100 | 51 | D | — | — | 11 d ago | |
| 10 | C | How Xberg resolves config: CLI and server/MCP precedence, file walk-up, inline JSON, overrides. Use when adding a setting or one does not take effect. | 100 | 51 | D | — | — | 11 d ago | |
| 11 | C | Xberg OCR backends, preprocessing, caching, page acceptance, hOCR, tables, cross-backend quality. Use for OCR behavior or A/B quality work. | 100 | 50 | B | — | — | 11 d ago | |
| 12 | C | Xberg MIME detection and extractor routing (core/mime.rs, FORMATS registry). Use when a file routes to the wrong extractor or a format is added. | 100 | 51 | D | — | — | 11 d ago | |
| 13 | C | Xberg text chunking (ChunkerType, ChunkingConfig wire names), embeddings and RAG. Use when changing chunking or embeddings code or config. | 100 | 51 | C | — | — | 11 d ago | |
| 14 | C | Xberg core extraction orchestration: cache, extractor fallback, post-processing, concurrency, quality invariants. Use for pipeline changes. | 100 | 47 | C | — | — | 11 d ago | |
| 15 | C | Xberg on top of the shared Alef workflow: output locations, alef.toml sections, regen-breaking core edits, FFI JSON bridge. Use when editing bindings. | 100 | 47 | C | — | — | 11 d ago | |
| 16 | C | Which xberg-io repo owns a cross-repo fix or API, and coordinating compatible sibling changes. Use when work spans sibling repositories. | 100 | 47 | C | — | — | 11 d ago | |
| 17 | C | Xberg extraction benchmarks: running, quality scoring, fixtures, ground truth. Use for the Benchmarks workflow or benchmark-harness work. | 100 | 47 | C | — | — | 11 d ago | |
| 18 | C | crates/xberg-wasm build constraints: wasm-target features, sync-only APIs, SyncExtractor, size limits. Use for wasm32 build or runtime failures. | 100 | 48 | F | — | — | 11 d ago | |
| 19 | C | Xberg workspace layout: version source, members and excluded crates, packages/, tools/, ignore allowlists. Use when placing code or adding a crate. | 100 | 47 | D | — | — | 11 d ago | |
| 20 | C | Xberg REST API server (axum routes, middleware, cache endpoints) and MCP surface. Use when changing an endpoint, server startup or MCP tools. | 100 | 47 | C | — | — | 11 d ago | |
| 21 | C | Xberg PDF extraction: native/Pdfium backend selection, rendering, encryption, OCR fallback, capability gaps. Use for PDF engine work. | 100 | 47 | C | — | — | 11 d ago | |
| 22 | C | The test_documents corpus (submodule, bucket-fetched): read_test_fixture, missing fixtures, A/B controls. Use on a fresh clone or a missing fixture. | 100 | 48 | F | — | — | 11 d ago | |
| 23 | C | Cargo features: shared otel/mcp/allocator contract, then Xberg's ORT-free targets, aggregates, PDF backend, parity guard. Use when editing [features]. | 100 | 47 | D | — | — | 11 h ago | |
| 24 | D | Xberg TS/JS tooling: pnpm vs npm lockfiles, Vitest, napi-rs, wasm-pack, integration packages. Use for TS/JS package or tooling changes. | 100 | 43 | D | — | — | 11 d ago | |
| 25 | D | xberg's e2e fixture schema: fields, categories, calls, inputs, mock responses, assertions. Use when adding or editing an xberg e2e fixture. | 100 | 43 | D | — | — | 11 h ago | |
| 26 | D | Xberg release on top of the shared release-workflow: task version:sync to bindings and chart, CI/Publish/Benchmarks readiness. Use before a release. | 100 | 38 | D missing files | — | — | 11 h ago |