以下为本文档的中文说明该技能用于回答用户关于Logseq知识库管理仓库的问题通过研究源代码、文档、测试用例、运行时行为和历史Git记录来提供准确答案。Logseq是一个开源的知识管理和笔记应用此技能深入理解其代码库结构和设计理念。开发者可以利用此技能快速获取Logseq的技术细节包括功能实现原理、API使用方法和配置选项说明。适用于Logseq的贡献者、插件开发者和深度用户需要了解项目内部机制的场景。该技能大幅减少了在大型代码库中查找信息的时间提供即时的、准确的问答服务帮助用户更高效地参与Logseq社区的开发和维护工作。该技能提供了详细的操作指南和最佳实践帮助用户快速上手并深入掌握。通过系统的功能模块划分和丰富的应用场景说明用户可以在实际项目中有效运用该技能提升工作效率。该技能注重实用性和可操作性涵盖从基础配置到高级功能的完整知识体系满足不同层次用户的学习需求。持续更新和优化的内容确保用户始终能够接触到最新的技术发展和行业实践。通过此技能的学习和应用用户可以减少摸索时间快速获得可用的解决方案将精力集中在核心业务逻辑和创新工作上从而在技术快速迭代的环境中保持竞争力。该技能的模块化设计使其易于扩展和定制用户可以根据自身需求灵活调整应用方式实现最大化的价值产出。该技能整合了常见的设计模式和最佳实践提供了清晰的学习路径和参考资料帮助用户在短时间内建立起完整的知识框架并有能力在实际项目中灵活运用所学内容解决问题。Logseq Answer MachineUse this skill to answer questions from the Logseq repo itself. Produce evidence-backed explanations, not product changes.GuardrailsDo not implement features, fix bugs, refactor code, create migrations, or make permanent behavior changes while using this skill.Default to read-only investigation: source search, file reading, docs, tests, command output, REPL probes, and UI observation.If a question turns into an implementation or bugfix request, stop using this skill and switch to the appropriate implementation/debug workflow.If any temporary edit is necessary for exploration, keep it minimal, explain why it is needed, avoid user data, and revert it after the question has been explored.Revert every exploration-time modification before the final answer. Do not leave temporary logs, probes, config changes, generated debug files, or test edits in the worktree.Respect all applicableAGENTS.mdfiles before any file edit, including temporary logs.Clearly separate observed facts, source-backed conclusions, runtime experiment results, and inference.Investigation WorkflowRestate the question as the exact behavior, subsystem, or data flow to explain.Read rootAGENTS.mdand any relevant directory-specificAGENTS.mdfiles for touched paths.Locate evidence with fast repo search:Usergorrg --filesfor symbols, namespaces, routes, commands, UI labels, config keys, schema keywords, and tests.Prefer primary repo evidence: source files, tests, docs, migrations, EDN config, package manifests, and scripts.Use git history only when the question asks about intent, regression timing, or historical behavior.Build a concise evidence map:owning namespace/filecaller/callee chain or data flowrelevant tests and fixturesdocs or agent-guide referencesruntime surface: CLI, Desktop renderer, Electron main, db-worker-node, web app, server/worker, or mobileRun experiments only when static evidence is insufficient or the user asks for runtime confirmation.Answer in outline form with file and command references precise enough for another engineer to verify.Runtime ExperimentsChoose the narrowest tool that can verify the claim.CLI behavior: Load.agents/skills/logseq-cli/SKILL.mdbefore running or interpretinglogseqcommands. Use disposable graphs or explicit user-approved graph paths for mutating commands.Desktop, renderer, Electron, or db-worker-node internals: Load.agents/skills/logseq-repl/SKILL.mdand use the correct REPL target for focused probes.Web app behavior: Use theChromeskill when browser cookies/profile state or the web UI is needed.Desktop UI behavior: Use thecomputer-useskill when the local Desktop app window must be operated directly.Temporary logging: Add only targeted logs when REPL/UI observation cannot expose the needed state. Revert all logging changes and re-check the diff before finalizing.Record exact commands, REPL expressions, UI steps, and observed outputs when they materially support the answer. If a relevant experiment cannot run, state the blocker and do not present the claim as verified.Answer FormatProduce the final answer as a detailed outline. Keep it proportional to the question, but include these sections when useful:1. Short Answer - Direct conclusion in one or two bullets. 2. Evidence - path/to/file.ext:line: what this proves. - command or REPL probe: observed result. 3. How It Works - Step-by-step control flow, data flow, state transition, or runtime interaction. 4. Runtime Verification - What was tested through CLI, REPL, Chrome, or Desktop UI. - What could not be tested and why. - Whether any temporary modifications were made and confirmation that they were reverted. 5. Edge Cases and Open Questions - Important limitations, ambiguity, or repo areas not covered. 6. Practical Takeaways - Where to look next, which tests cover it, or what constraints matter.Usethe active conversation language for explanatory prose, while keeping code, identifiers, file paths, command names, and quoted repo text exact.