expand-orgs

Map repositories to parent organizations via GitHub API and URL parsing.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/noemotiovon/oss-x --skill expand-orgs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expand-orgs
Source: https://github.com/noemotiovon/oss-x/tree/main/.claude/skills/expand-orgs
Command: npx skills add https://github.com/noemotiovon/oss-x --skill expand-orgs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill automates the process of expanding repositories into their parent organizations by resolving URLs via GitHub API and supplementing unresolved cases with an LLM Web Search.

Core Features & Use Cases

  • Resolve repositories to parent organizations using GitHub metadata and URL parsing.
  • Handle unresolved entries with LLM Web Search and structured human review.
  • Output comprehensive organization mappings including org_name, owner, platform, and confidence.

Quick Start

Run the expansion script to generate organizations from output/data_classify.csv into output/organizations.csv.

Frequently Asked Questions about expand-orgs

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

FAQPage Schema
How do I map GitHub repositories to their parent organizations?

Mapping GitHub repositories to parent organizations is automated by resolving URLs via the GitHub API and supplementing unresolved entries with LLM web search. The script processes repository data to identify the owning organization.

What is the best way to resolve missing organization ownership for ambiguous repository owners?

Resolving missing organization ownership for ambiguous owners requires applying LLM web search and human validation. The skill captures confidence levels for each mapping to ensure accuracy for downstream analytics.

How do I generate a structured organization mapping from a data classification CSV?

Generating a structured organization mapping from a data classification CSV involves running an expansion script that reads output/data_classify.csv. It outputs structured fields including org_name, owner, platform, and confidence into output/organizations.csv.

Does the organization resolution process handle repositories that the GitHub API cannot resolve?

Yes, organization resolution handles unresolved repositories by supplementing GitHub API data with LLM web search. Unresolved entries go through structured human review to verify org ownership before final output.

When should I use LLM web search for organization expansion instead of relying solely on GitHub metadata?

LLM web search for organization expansion applies when repository owners are ambiguous or missing org data from the GitHub API. It supplements unresolved cases before human validation to ensure complete mapping.