gather

Capture external sources as durable local knowledge assets for reuse in future sessions.

9|3|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/corca-ai/charness --skill gather-corca-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gather
Source: https://github.com/corca-ai/charness/tree/main/plugins/charness/skills/gather
Command: npx skills add https://github.com/corca-ai/charness --skill gather-corca-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Durably preserve external sources (Slack threads, Notion pages, Google Docs, Drive files, GitHub content, or arbitrary URLs) as local knowledge assets to be reused in future prompts, instead of re-fetching or re-summarizing each time.

Core Features & Use Cases

  • Create durable artifacts from diverse sources that can be read by future sessions.
  • Prefer primary sources and update existing assets in place when the source identity matches.
  • Integrate with the repo's gather adapter to store artifacts at a configurable location.

Quick Start

Turn a Slack thread into a reusable local knowledge asset for future prompts.

Frequently Asked Questions about gather

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

FAQPage Schema
How do I save Slack threads and Notion pages as local knowledge assets for future prompts?

The Skill enforces a durable-artifact model that captures external sources like Google Docs, GitHub content, or arbitrary URLs and stores them via a configured gather adapter path, creating reusable artifacts for future use.

How does preserving external sources as durable artifacts work for future sessions?

Instead of re-fetching or re-summarizing external content each time, the durable-artifact model stores the captured source locally, allowing future sessions to read and reuse the knowledge asset directly.

Can I update existing local knowledge assets when the source identity matches?

The system prefers primary sources and updates existing assets in place when the source identity matches, maintaining accurate and durable local knowledge artifacts.

Do I need a specific adapter path configured to store artifacts from external sources?

A configured gather adapter path is required to store artifacts locally, enabling the system to save captured external sources as durable knowledge assets for future reuse.

What types of external sources can be turned into reusable local artifacts?

The system captures diverse external sources, including Slack threads, Notion pages, Google Docs, Drive files, GitHub content, and arbitrary URLs, transforming them into durable local knowledge assets.