wiki-query

Name: wiki-query
Author: getpaperclipai

5stars1forks

How to install wiki-query?

getpaperclipai/paperclip/wiki-query

$npx -y skills add getpaperclipai/paperclip --skill wiki-query

Installs into the current project.

Summary

Use when an operation issue asks you to answer a question from the LLM Wiki — operationType: "query" and a question in the issue body. Answer with citations to wiki pages and raw sources, and offer to file durable synthesis back into wiki/synthesis/ so the work compounds inst

Files · 1

View on GitHub

SKILL.md

1	# Wiki Query
2
3	Answer a question from what the wiki actually contains, with citations.
4
5	## Inputs
6
7	- An operation issue with `operationType: "query"` and the question in the body.
8	- The operation issue's target `wikiId`, `spaceSlug`, and space root.
9
10	## Workflow
11
12	1. Open the target space's `wiki/index.md` first — it is the navigation aid. Identify candidate pages.
13	2. Read the candidate pages end to end with `wiki_read_page`, always passing the operation issue's `wikiId` and `spaceSlug`. Follow `[[wiki-links]]` to neighbouring pages when the question spans entities or concepts.
14	3. Inspect raw sources when a wiki page's claim feels thin. The wiki points to `raw/` precisely so you can verify before answering. Use `wiki_read_source`.
15	4. Answer the question in the operation issue thread. Structure:
16	- Direct answer first, in 1–4 sentences.
17	- Then the supporting facts as bullet points, each with an inline citation: `(see [[wiki/concepts/managed-resources]])` or `(see raw/<filename>)`.
18	- If you needed to read a raw source the wiki did not summarise, name that as a gap.
19	5. Decide whether the answer is durable. If the question forced you to do real synthesis (a comparison, a tradeoff, a definition of something that isn't already a page), offer to file it under `wiki/synthesis/<slug>.md`. Do not write the synthesis page silently — it is opt-in. If the user accepts, write the page, link it from `wiki/index.md`, and append a `query \| filed synthesis` log entry.
20	6. When the wiki cannot answer, say so plainly. Suggest a source the user should ingest, a Paperclip project that would help if distilled, or a web lookup. Never bluff.
21
22	## Voice
23
24	- Lead with the answer.
25	- Cite as you go, not in a footnote block at the end.
26	- Use the wiki's terse, factual voice. The query response is itself a candidate for filing into `wiki/synthesis/`.
27
28	## Verification
29
30	Before closing the operation issue:
31
32	- [ ] Every claim in the answer cites a wiki page or raw source.
33	- [ ] If the wiki was insufficient, that is stated directly with a concrete next step (ingest source X, distill project Y, web search Z).
34	- [ ] If you wrote a synthesis page, `wiki/index.md` lists it and `wiki/log.md` has a `query \| filed synthesis` entry.
35	- [ ] No file under `raw/` was modified.
36
37	## Tools
38
39	`wiki_search`, `wiki_read_page`, `wiki_list_sources`, `wiki_read_source`, `wiki_write_page` (only when filing synthesis). Always include the operation issue's `wikiId` and `spaceSlug`.

People who liked this also viewed

6 picks

Type

wiki-query

5stars1forks

View on GitHub

How to install wiki-query?

getpaperclipai/paperclip/wiki-query

$npx -y skills add getpaperclipai/paperclip --skill wiki-query

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Wiki Query
2
3	Answer a question from what the wiki actually contains, with citations.
4
5	## Inputs
6
7	- An operation issue with `operationType: "query"` and the question in the body.
8	- The operation issue's target `wikiId`, `spaceSlug`, and space root.
9
10	## Workflow
11
12	1. Open the target space's `wiki/index.md` first — it is the navigation aid. Identify candidate pages.
13	2. Read the candidate pages end to end with `wiki_read_page`, always passing the operation issue's `wikiId` and `spaceSlug`. Follow `[[wiki-links]]` to neighbouring pages when the question spans entities or concepts.
14	3. Inspect raw sources when a wiki page's claim feels thin. The wiki points to `raw/` precisely so you can verify before answering. Use `wiki_read_source`.
15	4. Answer the question in the operation issue thread. Structure:
16	- Direct answer first, in 1–4 sentences.
17	- Then the supporting facts as bullet points, each with an inline citation: `(see [[wiki/concepts/managed-resources]])` or `(see raw/<filename>)`.
18	- If you needed to read a raw source the wiki did not summarise, name that as a gap.
19	5. Decide whether the answer is durable. If the question forced you to do real synthesis (a comparison, a tradeoff, a definition of something that isn't already a page), offer to file it under `wiki/synthesis/<slug>.md`. Do not write the synthesis page silently — it is opt-in. If the user accepts, write the page, link it from `wiki/index.md`, and append a `query \| filed synthesis` log entry.
20	6. When the wiki cannot answer, say so plainly. Suggest a source the user should ingest, a Paperclip project that would help if distilled, or a web lookup. Never bluff.
21
22	## Voice
23
24	- Lead with the answer.
25	- Cite as you go, not in a footnote block at the end.
26	- Use the wiki's terse, factual voice. The query response is itself a candidate for filing into `wiki/synthesis/`.
27
28	## Verification
29
30	Before closing the operation issue:
31
32	- [ ] Every claim in the answer cites a wiki page or raw source.
33	- [ ] If the wiki was insufficient, that is stated directly with a concrete next step (ingest source X, distill project Y, web search Z).
34	- [ ] If you wrote a synthesis page, `wiki/index.md` lists it and `wiki/log.md` has a `query \| filed synthesis` entry.
35	- [ ] No file under `raw/` was modified.
36
37	## Tools
38
39	`wiki_search`, `wiki_read_page`, `wiki_list_sources`, `wiki_read_source`, `wiki_write_page` (only when filing synthesis). Always include the operation issue's `wikiId` and `spaceSlug`.

People who liked this also viewed

6 picks

Type