One-click install
npx skills add https://github.com/Houseofmvps/ultraship --skill learn-houseofmvps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learn
Source: https://github.com/Houseofmvps/ultraship/tree/main/skills/learn
Command: npx skills add https://github.com/Houseofmvps/ultraship --skill learn-houseofmvps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the critical problem of lost project context between coding sessions, where valuable insights like debugging root causes, architecture decisions, deployment gotchas, and performance findings are forgotten, leading to repeated mistakes, wasted debugging time, and redundant work across team members.

Core Features & Use Cases

  • Structured Learning Capture: Save categorized, tagged learnings for insights that can't be derived from code alone, such as why a specific queue system was chosen or a niche deployment configuration quirk.
  • Ranked Knowledge Recall: Surface the most relevant prior learnings for a given topic before starting work, ranked by relevance and recency, to avoid repeating past mistakes without dumping the entire knowledge base into context.
  • Compressed Context Loading: Generate a compact, topic-grouped digest of all project learnings to load cheaply at session start, plus export options to share knowledge with team members or back up before major refactors.
  • Use Case: For example, after resolving a tricky Redis connection pool exhaustion issue, save the root cause and fix as a learning; the skill will automatically surface it the next time you work on related backend code, preventing the same bug from recurring.

Quick Start

Use the learn skill to save the root cause and fix for the recent deployment issue you resolved on Railway, tagged with 'deployment' and 'railway' for future retrieval.

Frequently Asked Questions about learn

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

FAQPage Schema
How do I preserve debugging insights and architecture decisions across coding sessions?

To preserve debugging insights across coding sessions, you can capture and organize learnings as tagged JSON files. This structured approach prevents repeated mistakes by retaining institutional context like deployment gotchas and root causes for future ranked recall.

How does ranked knowledge recall work for retrieving past project learnings?

Ranked knowledge recall surfaces the most relevant prior learnings for a given topic based on relevance and recency. This mechanism prevents dumping the entire knowledge base into context, ensuring only the most applicable debugging insights are loaded.

Can I use this to manage engineering knowledge for individual developers and teams?

Yes, this approach applies to capturing, organizing, and retrieving learnings for both individual developers and engineering teams. It preserves institutional context for long-lived software projects, preventing redundant work across team members.

What is the best way to share project learnings with team members before a major refactor?

The best way to share project learnings is to generate a compressed, topic-grouped digest or use export options. This allows you to distribute knowledge or back up institutional context before major refactors.

How do I prevent repeated debugging mistakes when working on long-lived software projects?

You prevent repeated debugging mistakes by saving categorized, tagged learnings for insights that cannot be derived from code alone. The system automatically surfaces these past root causes and fixes the next time you work on related code.

Does managing project knowledge this way require a specific directory structure?

Yes, this knowledge management approach stores learnings as tagged JSON files specifically within the project's .ultraship/learnings directory. This structured storage enables save, search, prune, and export operations for your engineering insights.