revisit

Update existing knowledge base notes with newer related content and connections.

20|5|Updated Nov 18, 2025
One-click install
npx skills add https://github.com/zby/llm-do --skill revisit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revisit
Source: https://github.com/zby/llm-do/tree/main/arscontexta/skills/arscontexta-revisit
Command: npx skills add https://github.com/zby/llm-do --skill revisit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps maintain the freshness and interconnectedness of your knowledge base by revisiting older notes and updating them with newer insights and connections.

Core Features & Use Cases

  • Backward Pass: Identifies and adds connections from newer notes to older ones.
  • Claim Sharpening: Evaluates and refines the core claims of existing notes.
  • Content Updates: Rewrites or splits notes to reflect evolved understanding.
  • Use Case: After writing several new notes on a topic, use this Skill to ensure your foundational notes on that topic are updated to reference these new developments, thereby strengthening the overall knowledge graph.

Quick Start

Use the revisit skill to update old notes with new connections.

Frequently Asked Questions about revisit

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

FAQPage Schema
How do I update old notes with new connections in my knowledge base?

To update old notes with new connections, you need a backward pass process that identifies newer related content and integrates it into foundational notes. This skill evaluates claim evolution and sharpens existing claims to maintain knowledge base interconnectedness.

What is a backward pass in knowledge management?

A backward pass in knowledge management is the process of tracing from newer notes back to older foundational ones. It identifies and adds connections from recent insights to existing notes, ensuring the knowledge graph remains interconnected and claims are sharpened.

How do I refine the core claims of existing notes after writing new content?

To refine the core claims of existing notes, you must evaluate claim evolution against newer related content. This involves sharpening the original statements and potentially rewriting or splitting notes to reflect your evolved understanding of the topic.

Does note revision require semantic search and index browsing?

Yes, effective note revision requires dual discovery using both semantic search and index browsing. This combination ensures comprehensive evaluation of claim evolution and accurate identification of related content for updating old notes.

When should I split content during note revision?

You should split content during note revision when an existing note's core claims have evolved significantly. If new insights overshadow or complicate the original focus, rewriting or splitting the note maintains clarity and strengthens the knowledge graph.