silver-rem

Append project insights to monthly knowledge or lessons files.

6|3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/alo-exp/silver-bullet --skill silver-rem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: silver-rem
Source: https://github.com/alo-exp/silver-bullet/tree/main/forge/skills/silver-rem
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill silver-rem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams capture a knowledge or lessons insight and organize it into project-specific or portable monthly documentation, ensuring critical learnings are preserved and discoverable.

Core Features & Use Cases

  • Classifies insights as project-specific or portable and routes them to docs/knowledge/YYYY-MM.md or docs/lessons/YYYY-MM.md.
  • Creates the monthly file when needed, and updates docs/knowledge/INDEX.md to reflect new entries.
  • Ensures insights are stored as structured headings and header metadata, with clear provenance.

Quick Start

Capture an insight and append it to the current month's knowledge or lessons document.

Frequently Asked Questions about silver-rem

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

FAQPage Schema
How do I capture project insights and save them to monthly documentation?

To capture project insights into monthly documentation, you append learnings to a structured monthly file. The system routes content to docs/knowledge/YYYY-MM.md or docs/lessons/YYYY-MM.md based on whether the insight is project-specific or portable.

What is the best way to organize retrospective notes into knowledge management files?

Organizing retrospective notes into knowledge management files involves categorizing insights as project-specific or portable. The content is then appended to structured monthly markdown files with clear provenance and header metadata for discoverability.

How does appending lessons learned to a monthly markdown file work?

Appending lessons learned to a monthly markdown file works by creating or updating the target YYYY-MM.md file. When a new monthly file is first created, the system automatically updates the knowledge index to reflect the new entry.

Can I use this for architecture reviews and design decisions or just retrospectives?

Yes, you can use this for architecture reviews and design decisions, as well as retrospectives and ongoing project work. It classifies each insight and routes it to the appropriate monthly knowledge or lessons document.

Does capturing project learnings require an existing knowledge index?

No, capturing project learnings does not require an existing knowledge index. The system creates the monthly file when needed and automatically updates docs/knowledge/INDEX.md when a new file is first generated.

What is the difference between project-specific knowledge and portable lessons files?

Project-specific knowledge is routed to docs/knowledge/YYYY-MM.md, while portable lessons are routed to docs/lessons/YYYY-MM.md. This separation ensures critical learnings are preserved and discoverable based on their applicability scope.