Skip to content
cccskills
FreePublished on GitHub

wiki-query

Answer questions against a persistent markdown wiki and optionally file the answer back into the wiki. Use this when the user asks what their wiki says about a topic, wants a comparison across notes, or wants citations grounded in the wiki.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md1.5 KB
  • agents/openai.yaml546 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Wiki Query

Use this skill when the user is asking the wiki a question.

Use the vault tool first

Start with interpreter_vault instead of wandering the file tree blindly.

Preferred sequence:

  1. interpreter_vault with action="search_notes" for the user query and likely synonyms.
  2. interpreter_vault with action="resolve_link" if the user references a page by wikilink-like name.
  3. interpreter_vault with action="note_context" for the strongest candidate notes.
  4. Read index.md if it exists and still helps you orient.
  5. Read only the specific wiki pages and source pages needed to answer.

Answer standard

  • Answer from the wiki layer, not from vague memory of raw files.
  • Cite claims inline with ([[Page Name]]).
  • Follow [[wikilinks]] when a page clearly points to another relevant page.
  • If the answer is a useful synthesis, comparison, or analysis artifact, offer to file it back into the wiki as a new page.

Hard rules

  • Do not rewrite the wiki unless the user asks you to file the answer back.
  • Prefer durable citations to page names that already exist in the workspace.
  • If the wiki is thin or missing needed coverage, say so plainly and suggest the next ingest or lint action.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Build a period-end accrual schedule by computing each accrual, citing support, and drafting journal entries for controller approval. Use during month-end close; this drafts entries only and must not post them.

The English summary is being prepared. Showing the original description.

openinterpreter/interpreter-workstation28Updated Oct 18, 2026

Audit a spreadsheet for formula accuracy, errors, and common financial-model mistakes. Use for selected ranges, single sheets, or whole-workbook model checks including balance-sheet balance, cash tie-out, roll-forwards, and logic sanity.

The English summary is being prepared. Showing the original description.

openinterpreter/interpreter-workstation28Updated Oct 18, 2026

Use this skill when the user needs advanced Playwright control of an already running browser session through Interpreter's app-managed browser bridge and the `builtin-js-repl` `js_repl` tool, after simple browser page work cannot be handled by the unified `builtin-interpreter` browser page tools.

The English summary is being prepared. Showing the original description.

openinterpreter/interpreter-workstation28Updated Oct 18, 2026

Drive a native desktop app through Interpreter's builtin-cua-driver. Use get_app_state, click/type/scroll/drag, and verify by calling get_app_state again when the user asks to operate a real desktop app, browser chrome, native dialog, menu, secure prompt, file chooser, or hidden/background window.

The English summary is being prepared. Showing the original description.

openinterpreter/interpreter-workstation28Updated Oct 18, 2026

doc

Free

Create, inspect, and edit Word documents (`.docx`) with local code-execution tools. Use for document drafting, structured edits, tables, comments, and layout-sensitive Word deliverables.

The English summary is being prepared. Showing the original description.

openinterpreter/interpreter-workstation28Updated Oct 18, 2026

Design or revise Interpreter UI for non-developers with an ultra-minimal, utilitarian style inspired by the OpenAI website and ChatGPT, not the developer platform. Use when simplifying settings, onboarding, chat, forms, empty states, or helper copy; when removing extra containers, labels, or visual noise; when replacing technical wording with plain language; when clarifying hierarchy and making the main user action obvious; when making every visible label and status understandable to an average HR admin or other non-technical user; when hiding implementation details such as logs, IDs, endpoints, paths, or protocol names; or when a screen must respect the app's existing CSS variables and light/dark theme behavior.

The English summary is being prepared. Showing the original description.

openinterpreter/interpreter-workstation28Updated Oct 18, 2026

See all skills by openinterpreter

Report a problem with this skill