agentleFS
yapeepeeyapeepee/agent-harnesses/inquiry-graph-harness/SKILL.md

inquiry-graph

Skill1 starsChanged 2 months agoLicence not identifiedView on GitHub

追問圖 — a question-graph harness over the user's Obsidian vault (`inquiry/`). Every question the user asks an AI becomes a node; follow-ups anchor to a specific atom of the parent answer; the question stack (the "return address") is printable; closing a node requires the user's own restatement, which is back-propagated to the parent and up to the root's big picture; cross-tree links the user did not notice are proposed for ratification and drawn on Obsidian canvases. Use whenever the user asks a conceptual or technical question they want recorded, says part of an answer is unclear ("A3 不懂", "P1 是什麼", "這裡不懂", "我不知道哪裡不懂"), asks where they are in a chain of follow-ups ("/where", "我問到哪了", "回到大問題"), wants to close a question ("/resolve", "懂了,收掉這題"), asks whether questions connect ("/weave", "這跟之前問的有關嗎"), or wants the canvas regenerated ("/map"). Trigger on "/ask", "/where", "/resolve", "/weave", "/map", "追問", "追問圖", "記進追問圖", "連回大圖", "先不追". Do NOT trigger for ordinary coding work — only when the user invokes a command or explicitly asks to record, locate, close, or connect a question.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.