learn

Aggregate and index project learnings across sessions in JSONL stores.

5|1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/forbotsake/forbotsake --skill learn-forbotsake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learn
Source: https://github.com/forbotsake/forbotsake/tree/main/.claude/skills/gstack/learn
Command: npx skills add https://github.com/forbotsake/forbotsake --skill learn-forbotsake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage project learnings across sessions by reviewing, searching, pruning, and exporting what gstack has learned. Use it when you need to remember past patterns, surface insights, or share knowledge with teammates.

Core Features & Use Cases

  • Review and prune learnings across sessions to keep knowledge fresh.
  • Search and filter learnings by key phrases, type, or date.
  • Export learnings to markdown or JSONL for documentation, onboarding, or audits.
  • Proactively surface patterns or warnings based on past runs to guide decisions.

Quick Start

Summarize the most recent learnings and export a concise report for this project.

Frequently Asked Questions about learn

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

FAQPage Schema
What is the best way to prune stale knowledge management entries?

You can export project learnings to markdown or JSONL formats, providing concise reports for documentation, team onboarding, or compliance audits.

Can I export project learnings to markdown for documentation?

You can export project learnings to markdown or JSONL formats, providing concise reports for documentation, team onboarding, or compliance audits.

How do I surface patterns from past project runs to guide decisions?

You surface patterns from past project runs by indexing aggregated learnings, allowing the system to proactively surface insights or warnings based on historical data to guide decisions.

Why do I need to prune stale entries from a learnings store?

You need to prune stale entries from a learnings store to keep knowledge fresh, ensuring that retrieved patterns and insights accurately reflect current project contexts and dependencies.