Learn

Sources

GitLab Wikis (via glab API)

The primary source for OSDU knowledge. Use the GitLab wiki API:

# List pages in a project wiki
glab api "projects/<url-encoded-path>/wikis?per_page=100" --hostname community.opengroup.org

# List pages in a group wiki
glab api "groups/<url-encoded-path>/wikis?per_page=100" --hostname community.opengroup.org

# Fetch a single page
glab api "groups/<url-encoded-path>/wikis/<slug>" --hostname community.opengroup.org

Known OSDU wiki sources:

URLs

When given a URL, use WebFetch to retrieve content, then distill into a knowledge note.

Pasted Content

When the user pastes content directly, treat it as the source material and distill.

Protocol

Step 1: Discover

List available pages from the source. Filter out noise:

Include — pages about architecture, services, APIs, governance, strategy, processes, standards, patterns, and the most recent release notes (latest 1-2 milestones only).

Exclude — upload/attachment pages, sidebar navigation, historical release/tagging notes (keep only the latest), duplicate or redirect pages.

Present the filtered list to the user and confirm which pages to ingest.

Step 2: Fetch & Assess

For each selected page:

1. Fetch the raw content via API
2. Assess whether it has enough substance for a knowledge note (skip stubs, redirect pages, pages that say "moved to X")
3. If the content is thin, note it and skip

Step 3: Distill

Transform raw wiki content into a vault knowledge note. This is the critical step — do NOT copy-paste raw wiki markdown. Instead:

1. Extract durable concepts — strip navigation boilerplate, redundant headers, and formatting artifacts (GitLab-specific syntax like [[_TOC_]])
2. Summarize where appropriate — tables of services/APIs can be preserved as-is, but long prose sections should be condensed to the key points
3. Preserve links — keep URLs to GitLab repos, API docs, and external references. Convert GitLab wiki internal links to their full URLs
4. Add context — include a one-line summary at the top explaining what this knowledge is and why it matters
5. Split or consolidate — one note per topic when content is substantial (~500+ words of real content). Consolidate thin related pages into a single concept note when they don't stand alone. Too coarse = every RAG search returns an omnibus doc. Too fine = related context scattered across dozens of files.

Step 4: Write

Create the knowledge note following brain skill conventions:

Frontmatter:

---