knowledge

Consolidate cross-layer session knowledge into a deduplicated layer briefing file.

3|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/willietran/autoboard --skill knowledge-willietran
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge
Source: https://github.com/willietran/autoboard/tree/main/skills/knowledge
Command: npx skills add https://github.com/willietran/autoboard --skill knowledge-willietran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Curate cross-session knowledge between layers — deduplicate, filter by relevance, resolve conflicts, and brief next-layer sessions.

Core Features & Use Cases

  • Deduplicate repeated findings across sessions to produce a concise briefing.
  • Filter knowledge by dependency and relevance to direct next-layer tasks.
  • Resolve conflicting patterns and document architectural decisions for coherence.

Quick Start

Aggregate completed session knowledge into the layer-{N}-knowledge.md for the next layer, ensuring deduplication and coherence.

Frequently Asked Questions about knowledge

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

FAQPage Schema
How do I consolidate cross-layer knowledge into a concise briefing?

To consolidate cross-layer knowledge, apply curation logic to completed session status files and prior layer knowledge to generate a new layer knowledge file. This enforces deduplication and conflict resolution to ensure a coherent, reusable knowledge base.

What is the best way to deduplicate repeated findings across multiple sessions?

The best way to deduplicate repeated findings across sessions is to process completed session status files through a curation workflow. This filters knowledge by relevance and resolves conflicting patterns to produce a concise briefing.

How do I resolve conflicting architectural patterns during knowledge curation?

To resolve conflicting patterns during knowledge curation, the process evaluates cross-layer session data and documents the resulting architectural decisions. This ensures coherence and maintains a reusable knowledge base for next-layer tasks.

How do I filter session knowledge by dependency relevance for the next layer?

To filter session knowledge by dependency relevance, apply curation rules to completed session status files and prior layer knowledge files. This filters irrelevant data, directing next-layer tasks with a concise, actionable briefing.

When do I need to generate a layer knowledge file for my project?

You need to generate a layer knowledge file when transitioning between project layers and requiring a coherent briefing. It consolidates completed session status files and prior layer knowledge, ensuring deduplication and documented architectural decisions.