AutoRAG is a TypeScript-based RAG (Retrieval-Augmented Generation) agent platform with a CLI, local-first indexing, and a plugin-based datasource skill system. It provides an `AutoRAGAgent` that orchestrates document retrieval across multiple methods (BM25, vector, hybrid) and external data sources (Slack, Discord, Gmail, GitHub, KakaoTalk, Obsidian, cloud drives, etc.) via connector-backed skills. The agent uses a Pi agent loop with tools for search, memory, and feedback, and includes a web UI for datasource management. The repository also contains a legacy Python RAG pipeline (`legacy/autorag/`) with YAML-driven node-based evaluation, but the primary development is on the TypeScript version. Key architectural patterns include a parser registry with extension-based dispatch, a retrieval method registry with parallel execution and result merging, a memory subsystem with persistent feedback and insight extraction, and a portable spawn utility for cross-platform child process execution. The system is designed for privacy: remote embedding egress is rejected, and filesystem paths are kept opaque in diagnostics.
This repository is a curated awesome-list of open-source operations and DevOps tools, organized into 82 categories with 653 entries. It is not a software application; it is a structured dataset of YAML metadata files that are transformed into bilingual README tables via a GitHub Action using Go templates. The data lineage is: contributors add YAML files under items/<category>/<tool>.yaml with fields kind, owner, repo, desc, and desc_en; on push to main, the generator workflow runs the eryajf/yaml-readme action to fetch live GitHub metadata (license, stars, creation/update dates) and render README.md and resources/README-en.md from the provided templates. The repository serves as a discovery resource for engineers evaluating ops tools, answering questions like 'what are the best open-source tools for a given ops category?' and 'what is the license, star count, and last update of a tool?'. It is actively maintained with recent commits, a YAML linting CI, and a clear contribution guide. The reusable assets are the templating pattern and CI workflows, which can be adapted to any curated list or structured-data-to-document pipeline.
This repository is a curated list of open-source sysadmin tools, functioning as a knowledge base rather than an executable application. It contains no source code, API endpoints, or data processing pipelines. The content consists entirely of Markdown documentation linking to external software projects across categories like backups, monitoring, configuration management, and virtualization. The PR template explicitly redirects contributions to a separate repository (`awesome-sysadmin-data`), indicating this repo may serve as a mirror or legacy interface while the active data management occurs elsewhere. The repository structure is flat, containing only documentation files (README.md, LICENSE.txt) and GitHub issue templates. There are no executable components, unit tests, or dependency manifests. While the content is valuable for discovery, it lacks the engineering substance required for software reuse. The metadata (links, descriptions, licenses) is static and human-curated, making it a dataset of software recommendations rather than a data pipeline. The repository is actively maintained based on the provided commit history (2026-06-20), though the workflow is split between this repo and the `-data` variant. Technical drift is minimal as Markdown content does not degrade, though external links may rot over time. Reproducibility is high as the content is static and fully documented within the file itself.