agent-researcher

Convert labeled Plane research issues into structured wiki updates with diffs.

6|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/Xipher-Labs/walter-os --skill agent-researcher-xipher-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-researcher
Source: https://github.com/Xipher-Labs/walter-os/tree/main/skills/agent-researcher
Command: npx skills add https://github.com/Xipher-Labs/walter-os --skill agent-researcher-xipher-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the manual effort of converting labeled Plane research requests into properly structured, operator-reviewable wiki knowledge updates.

Core Features & Use Cases

  • Autonomous source ingestion: Reads one or more URLs, file paths, or pasted text from the Plane issue description and drafts the corresponding wiki source page.
  • Entity and topic updating: Creates or updates entity stubs (people, companies, concepts, decisions, tools, topics) and updates the relevant topic hub(s).
  • Operator-gated safe publishing: Produces a Plane comment plus a wiki diff, ending with an explicit completion marker so the runner can commit only under the correct approval mode.
  • Use Case: When you receive a Plane issue labeled lane:research with an article link, it ingests that source into wiki/sources and refreshes the related entity/topic pages in one coherent batch.

Quick Start

Run the researcher agent in the Walter Council for a Plane issue that has labels lane:research and context:work, and provide the source URL(s) in the issue description.

Frequently Asked Questions about agent-researcher

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

FAQPage Schema
How do I convert labeled Plane research issues into structured wiki knowledge?▼

To convert Plane research issues into wiki knowledge, this Skill ingests URLs, file paths, or pasted text from the issue description and drafts source pages plus entity updates automatically. It produces a Plane comment and wiki diff for operator approval.

How does entity extraction work when ingesting research sources into a wiki?▼

Entity extraction works by creating or updating entity stubs like people, companies, concepts, and tools from the ingested source content, then linking them to relevant topic hubs within the wiki directory structure for operator review.

What is the best way to automate knowledge base curation from issue tracking platforms?▼

Automating knowledge base curation from issue tracking is best handled by reading labeled issues, ingesting linked sources, and generating structured wiki diffs with explicit completion markers for operator-gated publishing and wiki index rebuilding.

Can I use this to ingest URLs and file paths directly into a wiki directory?▼

Yes, you can ingest URLs and file paths directly into a wiki directory. The Skill reads provided sources from the Plane issue and writes exclusively under the wiki/ path, including wiki/log.md updates and index rebuilds.

How do I prevent recursive ingestion when updating wiki sources from research issues?▼

To prevent recursive ingestion when updating wiki sources, the Skill enforces explicit rules against re-ingesting already processed content and uses terminal result markers to stop runner loops after drafting the diff for operator approval.

Do I need operator approval before publishing wiki updates from research issues?▼

Yes, operator approval is required before publishing. The Skill produces a Plane comment and wiki diff ending with an explicit completion marker, ensuring the runner commits only under the correct approval mode without exceeding token limits.