dark-lyre
dark-lyre's work was selected for the XERJ Corpus Hub, the open reference memory AI coding agents search before they write code. When an agent meets the same problem, it gets this implementation back as a worked example, with the author and the repository attached.
Totals across every corpus @dark-lyre appears in; a commit selected for two corpora counts once. Files and lines count the selected commits; each corpus indexes the whole repository at its pinned commit.
What an agent can do with the QQ_BOT corpus
dark-lyre/QQ_BOT: QQ机器人（b站视频解析下载，猫娘聊天，JM下载，随机P站图片）--该项目基于FunEnn前辈https://github.com/FunEnn/ncatbotPlugin 的开源项目改进而来
- Reuse a worked example: the commit “新增多源图片溯源并优化匹配排序，调整猫娘联网问答与月度预算” (25 files · Python).
- Answer from QQ_BOT's real Python source instead of memory (API design and specification).
- Where does QQ_BOT handle “新增多源图片溯源并优化匹配排序，调整猫娘联网问答与月度预算”?
- What does tests do in QQ_BOT?
Search the GitHub repository dark-lyre/QQ_BOT with XERJ (https://hub.xerj.org/corpus/dark-lyre--qq-bot). Run these in a shell, in order, and check each result before the next: 1. xerj --help (success: it prints usage). If xerj is missing: curl -fsSL https://xerj.org/get | sh 2. git clone https://github.com/dark-lyre/QQ_BOT QQ_BOT && git -C QQ_BOT checkout 6cc9f935f3847df52ac6e57edb2023d06b66408d 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./QQ_BOT --url http://127.0.0.1:9200 --prefix qq-bot --progress plain 5. xerj autoindex map --url http://127.0.0.1:9200 Then answer my question from the indexed files and cite the ax_path of every hit. Query syntax: https://xerj.org/llms.txt Licence: MIT. Keep the copyright notice and credit the authors.
corpus dark-lyre--qq-bot · API design and specification
Related corpora: swagger-ui, grpc-gateway, asyncapi-spec, rust-api-guidelines
Search an OpenAPI spec from an agent · Case study: reference coding for agents
Selected work
dark-lyre/QQ_BOT
The corpus is the whole repository at the pinned commit, not only the files of the selected commit.
Not installable yet: this corpus is not in the hub registry until its licence review passes, so xerj corpus add and xerj ask cannot fetch it. It becomes installable when this card says live in the hub.
Sign in with GitHub or Hugging Face to see more: every selected commit in full (commit date, every folder, licence review state, pin) and the pack builds of each corpus.
[](https://hub.xerj.org/contributors/dark-lyre)
Included with the author's permission (email, 2026-10-24), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.