Atlas Scan — Discover and Review

Scan user projects for Atlas metadata and repository ownership via GitHub.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/CortaLabs/atlas --skill atlas-scan-discover-and-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Atlas Scan — Discover and Review
Source: https://github.com/CortaLabs/atlas/tree/main/.claude/skills/atlas-scan
Command: npx skills add https://github.com/CortaLabs/atlas --skill atlas-scan-discover-and-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the discovery and initial review of user projects within the Atlas framework, ensuring that only relevant and owned repositories are considered for further processing.

Core Features & Use Cases

  • Project Discovery: Scans configured directories to identify all potential projects.
  • Metadata Extraction: Gathers initial metadata from projects, distinguishing between explicitly configured and inferred data.
  • Ownership & Visibility Check: Flags non-owned repositories and checks Git visibility.
  • Card Coverage Assessment: Reports on the percentage of owned repositories that have associated cards.
  • Use Case: Before generating portfolio cards, use this Skill to get a clear overview of all projects Atlas can find, identify which ones are owned by you, and understand the current state of card coverage.

Quick Start

Run the Atlas scanner against your projects directory to see discovered repositories and their metadata.

Frequently Asked Questions about Atlas Scan — Discover and Review

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

FAQPage Schema
How do I scan my projects to check repository ownership and visibility before generating portfolio cards?

To scan projects for repository ownership and visibility, this Skill auto-detects Git visibility via the gh CLI and checks ownership against your authenticated GitHub user and organizations. It filters out upstream clones or forks so only owned repositories proceed to card generation.

What is the best way to discover all repositories in my projects directory and extract their metadata?

The best way to discover repositories and extract metadata is by running the Atlas scanner against your configured directory. It identifies all potential projects, gathers inferred and explicit metadata, and reports the percentage of owned repositories with associated cards.

Does the repository ownership check work with forks and upstream clones?

The repository ownership check explicitly filters out forks and upstream clones. It validates ownership against the authenticated GitHub user and their organizations, ensuring non-owned repositories are excluded from card generation.

Do I need the gh CLI to detect Git visibility for my repository metadata scan?

Yes, you need the gh CLI installed and authenticated to detect Git visibility during the repository metadata scan. The scanner relies on it to automatically determine public or private status and verify ownership against your GitHub user.

Why are some of my discovered repositories excluded from the card generation process?

Discovered repositories are excluded from card generation when ownership validation fails. The scanner checks repositories against your authenticated GitHub user and organizations, intentionally filtering out non-owned repositories like upstream clones.

Can I use Atlas Scan to assess card coverage for my owned repositories?

You can use this Skill to assess card coverage by scanning your projects directory. It reports the exact percentage of owned repositories that already have associated cards, giving you a clear overview before generating new ones.