meta-collect-knowledge

Gathers relevant knowledge from sibling projects and other memory trees into the current project.

1|Updated Jun 23, 2026
One-click install
npx skills add https://github.com/bitranox/bitranox-skills --skill meta-collect-knowledge-bitranox
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: meta-collect-knowledge
Source: https://github.com/bitranox/bitranox-skills/tree/main/plugins/bitranox/skills/meta-collect-knowledge
Command: npx skills add https://github.com/bitranox/bitranox-skills --skill meta-collect-knowledge-bitranox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Memory cascades only flow down one ancestor chain, so lessons filed in a sibling project or a separate knowledge tree never reach the current project on their own. This Skill performs the inbound gather: it finds knowledge stored elsewhere that is relevant to the current project and imports it safely, without dangling cross-tree references or leaked credentials. ## Core Features & Use Cases - Three-stage gather pipeline: a cheap deterministic keyword grep (gather_scan.py) finds candidates grouped by knowledge tree, a context-isolated subagent inspects them for genuine relevance, and imports follow strict tree rules (lift to a common ancestor, copy locally, or labeled copy across trees). - Privacy scrubbing: secrets and PII are stripped before anything crosses a project or tree boundary, while concrete operational detail is preserved. - Debounce tracking: a (project, topic) record via --mark/--seen flags prevents re-gathering the same topic on every trigger. - Use Case: When seeding a brand-new project, run the gather with the project's scope descriptor to pull in relevant lessons from your other projects so the new project starts informed instead of blank. ## Quick Start Ask the AI to collect knowledge relevant to this project from your other projects and memory trees, for example by saying "collect knowledge about deployment lessons from my other projects".

Frequently Asked Questions about meta-collect-knowledge

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

FAQPage Schema
How do I collect knowledge from my other projects into the current one?▼

Run the gather with a topic or the project's scope descriptor: gather_scan.py performs a keyword grep across other projects' memory stores, a subagent inspects candidates for relevance, and useful items are imported as lifts or labeled copies following the tree rules.

Why doesn't knowledge from a sibling project reach my current project automatically?▼

Memory cascades only flow down one ancestor chain, so knowledge filed in a sibling project or a different knowledge tree is invisible to the current project. This Skill exists precisely to bridge that gap with an explicit, audited inbound gather.

Can I gather knowledge across different knowledge trees?▼

Yes, when the cross_tree_search knob is enabled or you pass --cross-tree explicitly. Cross-tree imports are always self-contained labeled copies, never references, because trees share no ancestor and a cross-tree link would dangle.

How does the gather avoid leaking secrets between projects?▼

A mandatory privacy scrub runs on anything crossing a project or tree boundary before it is written. Credentials and PII are stripped, while concrete operational detail like paths and hostnames is kept because that is the useful part.

What happens if I trigger a gather for the same topic twice?▼

A debounce record in gathered-topics.tsv tracks (project, topic) pairs. The --seen flag reports whether a pair was already gathered and --mark records it, but neither blocks a scan you explicitly request.

When should I not run a knowledge gather?▼

Do not run a blind gather without a topic or scope descriptor, since it imports noise that later has to be pruned. At a brand-new project, first infer the descriptor from the README, directory name, or package metadata.