wiki-query

Retrieve recency-ranked, freshness-verified answers from organizational knowledge bases.

3|1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/rijnb/knowledge-base-wiki --skill wiki-query-rijnb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-query
Source: https://github.com/rijnb/knowledge-base-wiki/tree/main/.junie/skills/wiki-query
Command: npx skills add https://github.com/rijnb/knowledge-base-wiki --skill wiki-query-rijnb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of retrieving accurate, up-to-date answers from a long-lived knowledge base that mixes current information with outdated, superseded, or historical data, eliminating the risk of relying on stale or retired information for decision-making.

Core Features & Use Cases

  • Recency-aware querying: Automatically re-ranks search results by date to prioritize newer, relevant information, with special handling for historical questions that require older data.
  • Freshness and provenance validation: Flags stale data, respects superseded page markers, and leverages block-level provenance to pull only verified, current claims from canonical wiki pages.
  • Use Case: When you ask "Who leads the X project as of 2024?", the skill will prioritize recent pages, flag any outdated information, cite exact source blocks, and avoid using superseded content as the current answer.

Quick Start

Ask any question about your organization's projects, systems, decisions, people, or historical context, and the skill will return a freshness-verified, cited answer automatically.

Frequently Asked Questions about wiki-query

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I query a knowledge base that contains outdated or superseded information?

Querying a mixed knowledge base requires freshness validation and provenance tracking to separate current data from historical records. The system applies recency re-ranking to prioritize newer pages, flags superseded content, and cites exact source blocks to prevent reliance on outdated information.

How does recency re-ranking work for organizational knowledge retrieval?

Recency re-ranking automatically sorts search results by date to prioritize newer information when answering questions. It incorporates special handling for historical queries, ensuring that older data is appropriately contextualized rather than entirely discarded during the knowledge retrieval process.

What is block-level provenance tracking for wiki queries?

Block-level provenance tracking verifies the exact source blocks of information retrieved from canonical wiki pages. This mechanism ensures that only current, verified claims are pulled for decision intelligence, flagging stale data and respecting superseded page markers to guarantee answer accuracy.

Can I retrieve historical context without getting current project status mixed in?

Yes, historical context can be retrieved by leveraging freshness awareness and recency re-ranking. The system appropriately contextualizes historical data by distinguishing between current and outdated records, allowing you to query past decisions and historical project states without mixing in current updates.

How do I stop getting answers from superseded wiki pages?

To stop getting answers from superseded wiki pages, implement supersession tracking alongside freshness metadata validation. This mechanism respects retired page markers and actively flags stale data, ensuring that your decision intelligence relies solely on current, verified organizational knowledge.