project

Track external repositories and link them via flat symlinks.

2|3|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/laris-co/nat-agents-core --skill project-laris-co
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project
Source: https://github.com/laris-co/nat-agents-core/tree/main/bundles/skills/project
Command: npx skills add https://github.com/laris-co/nat-agents-core --skill project-laris-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track external repositories and quickly access them across study and development workflows by centralizing tracking with flat symlinks that point to ghq clones, ensuring a single source of truth.

Core Features & Use Cases

  • Learn: clone a repo for study and create a flat symlink under ψ/learn.
  • Incubate: clone a repo for active development and create a flat symlink under ψ/incubate.
  • Find & List: enumerate tracked repos and locate their ghq origins or linked paths.

Quick Start

Clone a repo for study or development with ghq get and link it as a flat symlink under ψ/learn or ψ/incubate.

Frequently Asked Questions about project

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

FAQPage Schema
How do I track external repositories locally using flat symlinks?

Track external repositories by cloning them with ghq and creating flat symlinks under ψ/learn or ψ/incubate, maintaining a single source of truth. This centralizes access across study and development workflows.

What is the difference between learn and incubate workflows for cloned repos?

Learn clones a repository for study and symlinks it under ψ/learn, while incubate clones for active development and symlinks under ψ/incubate. Both use flat symlinks pointing to ghq clones for consistent tracking.

Do I need ghq installed to clone and link repositories in my workspace?

Yes, ghq is required for cloning external repositories. You also need a ψ workspace with flat symlinks configured to learn and incubate directories to maintain the single source of truth.

How do I find and list tracked repositories and their ghq origins?

Use the find and list workflows to enumerate tracked repositories and locate their ghq origins or linked paths. This enables rapid discovery across all ghq-tracked repos in your workspace.

Can I maintain a single source of truth when studying and developing across multiple cloned repos?

Yes, by using flat symlinks that point to ghq clones, you maintain a single source of truth. The ψ workspace centralizes tracking so both learn and incubate workflows reference the same repository.

What's the best way to organize ghq-cloned repositories for both study and development?

Organize ghq-cloned repositories by creating flat symlinks under ψ/learn for study or ψ/incubate for development. This approach separates workflows while keeping a single source of truth for each tracked repo.