borrow-from-oss

Mines watched open-source repositories for changes and ranks borrowable ideas in a YAML backlog.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/mistakenot/skills --skill borrow-from-oss-mistakenot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: borrow-from-oss
Source: https://github.com/mistakenot/skills/tree/main/plugins/research/skills/borrow-from-oss
Command: npx skills add https://github.com/mistakenot/skills --skill borrow-from-oss-mistakenot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Keeping up with upstream open-source projects and deciding which of their ideas are worth adopting is manual, noisy work. This Skill tracks repos you admire, investigates only what changed since the last run, and filters every change against your project's profile so only relevant, actionable ideas land in a ranked backlog. ## Core Features & Use Cases - Profile-based relevance filtering: Establishes a one-time project profile (architecture, goals, non-goals) used to reject upstream changes that don't map to your real needs. - Incremental investigation with watermarks: Clones watched repos into .tmp/ and diffs only commits since last_investigated_commit, with a baseline snapshot mode for first runs. - Ranked idea backlog: Writes scored, labelled ideas (change_type, effort, impact, risk, confidence) with a candidate → shortlisted → accepted → implemented lifecycle to docs/research/opensource-ideas.yaml, one doc per project or monorepo sub-project. - Use Case: After adding mattpocock/skills as a source, run an investigation to diff its recent commits, extract three applicable patterns, and get a top-5 shortlist of quick wins to adopt in your own repo. ## Quick Start Track the repository facebook/react for ideas we could borrow and scan it for recent changes worth adopting.

Frequently Asked Questions about borrow-from-oss

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

FAQPage Schema
How do I track an open-source repo for ideas to borrow?▼

Add the repo as a source with its URL and a one-line reason for watching it. The skill clones it into .tmp/, investigates changes since the last watermark commit, filters them against your project profile, and appends scored ideas to docs/research/opensource-ideas.yaml.

How does the skill decide which upstream changes are relevant?▼

It runs every candidate through a profile recording your project's architecture, goals, and non-goals. Changes solving problems you don't have, ideas you can't map to a real subsystem, or items already in the backlog are dropped or marked low confidence.

Does borrow-from-oss work in a monorepo?▼

Yes. It maintains one opensource-ideas.yaml per sub-project, co-located at <sub-project>/docs/research/, each with its own profile, sources, and independent idea ID series. It resolves the correct doc by matching the sub-project or source repo you mention.

How are borrowed ideas scored and ranked?▼

Each idea gets effort (S/M/L) and impact (low/medium/high) labels; the score is impact divided by effort, scaled to 1-10, adjusted for stated-goal alignment and risk or confidence. The top 5 candidates by score are automatically marked shortlisted.

When should I use learning-diary instead of borrow-from-oss?▼

Use learning-diary to mine your own repository's history for lessons learned. Use borrow-from-oss only for investigating external open-source repositories you watch for ideas worth adopting.