source-harvest

Extract and classify source components from external repositories into Adopt/Enrich/Defer/Ignore categories.

2|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/infinitegameplayer/sovereign-ecosystem --skill source-harvest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-harvest
Source: https://github.com/infinitegameplayer/sovereign-ecosystem/tree/main/Council%20Chamber/Skills/Source%20Harvest
Command: npx skills add https://github.com/infinitegameplayer/sovereign-ecosystem --skill source-harvest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extract actionable patterns from external repositories by reading the actual source code (not just READMEs or descriptions) to inform governance and integration decisions.

Core Features & Use Cases

  • Inventory and classify source components (skills, hooks, commands, configs, protocols) from public or accessible repos.
  • Apply a governance framework to decide whether to Adopt, Enrich, Defer, or Ignore for each component, then generate structured harvest artifacts.
  • Produce a harvest report, recommended ecosystem edits, and records for deferred items; supports monitoring via Sovereign Tech Watch.

Quick Start

Identify a target repository, read its source files to inventory components, classify each item, and draft the harvest report for review.

Frequently Asked Questions about source-harvest

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

FAQPage Schema
How do I extract actionable patterns from external repositories by reading source code?

Source code extraction reads actual repository files to inventory components, classify each item, and draft governance artifacts rather than relying on READMEs. This approach informs integration decisions by analyzing the real implementation logic of plugins or tools.

What is the best way to classify repository components for ecosystem governance?

Classifying repository components for governance involves inventorying source files and applying an Adopt, Enrich, Defer, or Ignore framework to each item. This generates structured harvest artifacts and records for deferred items to guide ecosystem edits.

Can I evaluate external plugin governance implications without reading the entire codebase?

Evaluating governance implications requires reading actual source code to inventory components accurately. You classify each identified component into Adopt, Enrich, Defer, or Ignore categories to produce actionable harvest reports and recommended ecosystem edits.

Does source code analysis work for generating harvest reports on public repos?

Source code analysis supports inventorying components from public or accessible repos to generate structured harvest reports. It classifies items into Adopt, Enrich, Defer, or Ignore, and optionally logs records for deferred items via Sovereign Tech Watch.

When do I need source code review instead of README analysis for repository integration?

Source code review is needed when integration decisions require understanding actual implementation logic rather than descriptions. It reads real source files to classify components and draft ecosystem edits, ensuring governance decisions reflect true repository behavior.