wf-search

Search WikiFlow documentation repositories and return ranked summaries.

2|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/liqunx/wikiflow --skill wf-search
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wf-search
Source: https://github.com/liqunx/wikiflow/tree/main/skills/wf-search
Command: npx skills add https://github.com/liqunx/wikiflow --skill wf-search

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

WikiFlow prevents code and documentation from drifting apart by helping you quickly locate the current implementation and the rationale behind past decisions before you plan or change anything.

Core Features & Use Cases

  • Searches the Wiki knowledge base: Quickly finds relevant pages across current implementation, decision logs, and historical/deprecated areas when needed.
  • Returns actionable summaries: Provides ranked matches with concise overviews rather than loading full documents into context.
  • Ensures correct execution context: Enforces that the skill runs in the documentation repository so it reads .wikiflow/config.json and the Wiki index properly.
  • Use case: Before updating a feature, search for the feature name (or a specific page like current/authentication) to understand how it works now and which decisions led to the current design.

Quick Start

Use the skill to query the current implementation and decision history by asking your AI to run wf-search with the topic you care about, such as "登录功能".

Frequently Asked Questions about wf-search

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

FAQPage Schema
How do I search a wiki for current implementation decisions and documentation?

Searching wiki decisions involves retrieving relevant pages from the documentation repository by matching topics against current implementation and decision logs. The skill reads the wiki index and returns ranked summaries with the highest priority given to current content.

What is the best way to find the rationale behind past wiki decisions before changing a feature?

Finding past wiki decisions requires searching the documentation repository's decision logs and historical sections. The skill matches your query against these records, returning concise summaries that explain why the current design was implemented that way.

Does wiki documentation search work without a configuration file in the repository?

Wiki documentation search requires reading the .wikiflow/config.json file to locate wiki paths, so it does not work without this configuration file. You must execute the search within the documentation repository to ensure proper context and index retrieval.

How do I retrieve summary-focused wiki search results instead of loading full documents?

Retrieving summary-focused wiki search results requires querying the documentation repository with a specific topic or page path. The search mechanism returns ranked matches with concise overviews rather than loading full documents into your context window.

Can I search deprecated and historical wiki sections when planning workflow updates?

Searching deprecated and historical wiki sections is supported optionally when planning workflow updates. The search retrieves relevant pages across current implementation, decision logs, and historical areas to support ad-hoc discovery and planning.