collect

Inventory project artefacts and external sources with provenance tracking.

4|1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/nicolasguelfi/gensem --skill collect-nicolasguelfi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: collect
Source: https://github.com/nicolasguelfi/gensem/tree/main/gse-one/plugin/skills/collect
Command: npx skills add https://github.com/nicolasguelfi/gensem --skill collect-nicolasguelfi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inventory artefacts from internal projects and external sources to provide a centralized view of assets, dependencies, and provenance.

Core Features & Use Cases

  • Internal mode inventories current project artefacts, ensuring alignment with project intent and sprint state.
  • External mode analyzes a local path or GitHub URL to extract modules, docs, and dependencies for governance and reuse decisions.
  • Provenance, licensing, and preflight checks are tracked to support compliance and traceability across backlogs and manifests.

Quick Start

Run COLLECT to inventory artefacts in your project and registered external sources.

Frequently Asked Questions about collect

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

FAQPage Schema
How do I inventory project artefacts and external sources for governance?

Inventorying project artefacts involves scanning internal project files and registered paths or URLs to extract modules, docs, and dependencies for centralized governance. The process enforces frontmatter readiness, sprint traceability, and provenance tracking.

What is the best way to track provenance and licensing for external code sources?

Tracking provenance and licensing for external sources is best handled by evaluating a local path or GitHub URL to extract modules and dependencies. This analysis supports compliance checks and reuse decisions by integrating tracked provenance with project backlogs and manifests.

Can I scan a GitHub URL to evaluate dependencies for my backlog?

Yes, you can scan a GitHub URL to evaluate dependencies for a backlog by using external mode. This mode analyzes the provided URL to extract modules and docs, enforcing preflight checks and dependency awareness to support structured governance decisions.

How does sprint traceability work when scanning internal project artefacts?

Sprint traceability during internal scanning works by enforcing alignment between the current project intent and sprint state. It checks frontmatter readiness and integrates with project manifests to ensure all scanned artefacts are properly traced and governed.

Do I need project manifests and frontmatter to inventory my project assets?

Yes, project manifests and frontmatter are required to inventory project assets effectively. The scanning process enforces frontmatter readiness and integrates with project manifests to ensure structured governance and complete asset traceability.

What are the limitations of backlog and inventory governance for external sources?

Limitations of backlog and inventory governance for external sources include the strict requirement for preflight checks, frontmatter readiness, and provenance tracking. Without proper dependency awareness and registered paths or URLs, structured governance and reuse decisions cannot be enforced.