ake/paperclip
1
0
Fork 0
mirror of https://github.com/alkimake/paperclip.git synced 2026-06-14 01:50:39 +09:00
Code Issues Projects Releases Packages Wiki Activity
paperclip/packages/plugins/plugin-llm-wiki/skills/wiki-query/SKILL.md
Dotta 508355b8fc
[codex] Add LLM Wiki plugin package to master (#5716) 
## Thinking Path

> - Paperclip orchestrates AI agents for zero-human companies.
> - The plugin system is the extension surface for optional product
capabilities without baking every workflow into core.
> - The LLM Wiki plugin package was reviewed in stacked PR #5592, which
targeted `pap-9173-llm-wiki-rest`.
> - The stack base PR #5597 merged to `master` before #5592 was merged
into that branch, so the plugin package never reached `master`.
> - A direct PR from `pap-9173-llm-wiki-rest` back to `master` would be
noisy because that branch has diverged from current `master`.
> - This pull request reapplies the reviewed
`packages/plugins/plugin-llm-wiki/` package onto current `master` and
updates Docker deps-stage manifest coverage.
> - The branch intentionally no longer changes `pnpm-workspace.yaml`
after maintainer feedback; because the new package is now a root
workspace importer, the remaining integration question is how
maintainers want the root lockfile handled under the current PR policy.

## What Changed

- Added the LLM Wiki plugin package under
`packages/plugins/plugin-llm-wiki/` from the merged PR #5592 head.
- Preserved the post-review cleanup from #5592: generated
design/screenshot artifacts are not committed, and `src/ui/index.tsx` /
`src/wiki.ts` are small public entrypoints.
- Added the new plugin package manifest to the Docker deps stage so
policy can validate package manifest coverage.
- Removed the earlier `pnpm-workspace.yaml` exclusion per maintainer
request, so the plugin is included by the existing `packages/plugins/*`
workspace glob.

## Verification

Current head:
- PGlite migration harness: ran migrations 001-003, verified old
non-space distillation unique constraints were removed, inserted
duplicate cursor and work-item keys in a second space, then reran
migration 003 successfully
- `node ./scripts/check-docker-deps-stage.mjs`
- `git diff --check`

Known current-head install result after removing the workspace
exclusion:
- `pnpm install --frozen-lockfile` fails because `pnpm-lock.yaml` has no
importer for `packages/plugins/plugin-llm-wiki/package.json`.

Previously verified on the same plugin source before the
workspace-exclusion removal:
- `pnpm --filter @paperclipai/plugin-sdk build`
- `cd packages/plugins/plugin-llm-wiki && pnpm install --lockfile=false
&& pnpm test`

## Risks

- The branch now includes `packages/plugins/plugin-llm-wiki` in the root
workspace but does not update `pnpm-lock.yaml`. Root frozen install will
fail until maintainers choose a lockfile path that fits repo policy.
- Committing `pnpm-lock.yaml` directly on this PR conflicts with the
current PR policy check, while excluding the package from
`pnpm-workspace.yaml` was rejected in maintainer feedback.
- The package includes UI code already reviewed in #5592; generated
screenshot/design artifacts were intentionally removed per maintainer
request, so visual review should regenerate screenshots locally if
needed.
- The package depends on plugin host support from #5597, which is
already merged to `master`.

> For core feature work, check [`ROADMAP.md`](ROADMAP.md) first and
discuss it in `#dev` before opening the PR. Feature PRs that overlap
with planned core work may need to be redirected — check the roadmap
first. See `CONTRIBUTING.md`.

## Model Used

- OpenAI GPT-5 Codex via Codex CLI, tool use and local code execution
enabled; context window not exposed.

## Checklist

- [x] I have included a thinking path that traces from project context
to this change
- [x] I have specified the model used (with version and capability
details)
- [x] I have checked ROADMAP.md and confirmed this PR does not duplicate
planned core work
- [x] I have run the targeted checks listed above
- [x] I have added or updated tests where applicable
- [ ] If this change affects the UI, I have included before/after
screenshots
- [x] I have updated relevant documentation to reflect my changes
- [x] I have considered and documented any risks above
- [x] I will address all Greptile and reviewer comments before
requesting merge

Stack context: #5592 was merged into `pap-9173-llm-wiki-rest` after
#5597 had already merged that branch to `master`, so this follow-up PR
is needed to carry the plugin package itself into `master`.

Co-authored-by: Paperclip <noreply@paperclip.ing>
2026-05-11 20:45:41 -05:00

2.8 KiB
Raw Blame History

name: wiki-query description: 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 instead of disappearing into a chat thread.

Wiki Query

Answer a question from what the wiki actually contains, with citations.

Inputs

  • An operation issue with operationType: "query" and the question in the body.
  • The operation issue's target wikiId, spaceSlug, and space root.

Workflow

  1. Open the target space's wiki/index.md first — it is the navigation aid. Identify candidate pages.
  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.
  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.
  4. Answer the question in the operation issue thread. Structure:
    • Direct answer first, in 1–4 sentences.
    • Then the supporting facts as bullet points, each with an inline citation: (see [[wiki/concepts/managed-resources]]) or (see raw/<filename>).
    • If you needed to read a raw source the wiki did not summarise, name that as a gap.
  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.
  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.

Voice

  • Lead with the answer.
  • Cite as you go, not in a footnote block at the end.
  • Use the wiki's terse, factual voice. The query response is itself a candidate for filing into wiki/synthesis/.

Verification

Before closing the operation issue:

  • Every claim in the answer cites a wiki page or raw source.
  • If the wiki was insufficient, that is stated directly with a concrete next step (ingest source X, distill project Y, web search Z).
  • If you wrote a synthesis page, wiki/index.md lists it and wiki/log.md has a query | filed synthesis entry.
  • No file under raw/ was modified.

Tools

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.