add-knowledge-source

Add documents, repositories, and web pages to the AI Asset Registry.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/solaius/ai-asset-registry --skill add-knowledge-source
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-knowledge-source
Source: https://github.com/solaius/ai-asset-registry/tree/main/.claude/skills/add-knowledge-source
Command: npx skills add https://github.com/solaius/ai-asset-registry --skill add-knowledge-source

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of bringing new source material into the AI Asset Registry so knowledge stays organized, traceable, and consistent as the project grows.

Core Features & Use Cases

  • Source Ingestion: Handles documents and references from Google Docs, PDFs, transcripts, GitHub repositories, URLs, blog posts, and Jira tickets.
  • Classification and Routing: Distinguishes between decided, proposal, exploratory, reference, and blog-example content so it is documented with the right level of authority.
  • Registry Updates: Guides updates to the knowledge registry, component docs, stakeholder lists, open questions, and source indexes with clear attribution.
  • Use Case: When a teammate shares a new design doc or blog link, use this Skill to analyze it, classify its status, identify impacted areas, and record it in the right project documentation.

Quick Start

Use the add-knowledge-source skill to analyze this new document and update the AI Asset Registry with its key metadata, affected areas, and source index entry.

Frequently Asked Questions about add-knowledge-source

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

FAQPage Schema
Can I ingest GitHub repositories and Jira tickets into the registry?

Yes, you can ingest GitHub repositories and Jira tickets alongside Google Docs, PDFs, web pages, and transcripts. The Skill extracts metadata from these sources and applies source classification for accurate registry updates.

What is source classification in a knowledge registry?

Classifying knowledge sources separates decided, proposal, exploratory, reference, and blog-example content. This ensures materials are documented with the correct authority level for accurate reference management.

Does adding a knowledge source require mapping affected project areas?

Yes, adding a knowledge source requires mapping affected project areas. The process identifies impacted components, updates stakeholder lists and open questions, and generates an impact report with clear attribution.

What is the best way to track project reference material from shared links?

The best way to track project reference material from shared links is to analyze the URL or blog post, classify its status, identify impacted documentation areas, and record it directly in the source index.