project
Skill121 starsChanged 7 months agoMITView on GitHub
Clone and track external repos. Use when user shares a GitHub URL to study or develop, or says "search repos", "find repo", "where is [project]". For active development, use /incubate.
39 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- saksham10arora-dotcom/everything-claude-codextheir own version, first seen Nov 1, 2026
- kriscard/Skillstheir own version, first seen Oct 28, 2026
- jantichy/claudetheir own version, first seen Oct 27, 2026
- usk6666/yorishiro-proxytheir own version, first seen Oct 25, 2026
- baney75/myelinatetheir own version, first seen Oct 20, 2026
- jurapascal/claude-code-hubtheir own version, first seen Oct 20, 2026
Used with
Projects with it also use ingest, next and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JaimeGBASkillingest
Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base
Also in 5 projects that use this
VercelSkillnext
Next.js renderer for json-render that turns JSON specs into full Next.js applications with routes, layouts, SSR, and metadata. Use when working with @json-render/next, building Next.js apps from JSON specs, or creating AI-generated multi-page applications.
Also in 3 projects that use this
Microsoft AzureSkilllint
Run all linting and spell checking for TypeScript and Rust code. Run this before committing to catch style issues, clippy warnings, and misspellings.
Also in 4 projects that use this
Microsoft AzureSkilltest
Also in 6 projects that use this
OpenAISkillaudit
Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.
Also in 5 projects that use this
GoogleSkillteach
Teach the user a new skill or concept, within this workspace.
Also in 4 projects that use this
- +2 more from Azure
Other versions39 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- l3rowniecakez/Claude_Skill★ 093% same
Wrote their own version · 38
- fleetdm/fleet★ 7.2ksame name
- samchon/typia★ 6ksame name
- samchon/nestia★ 2.2ksame name
- cwinvestments/memstack★ 425same name
- AlpacaLabsLLC/skills-for-architects★ 390same name
- Achuan-2/siyuan-plugin-task-note-management★ 227same name
- HurricaHjz/SecondSelf★ 156same name
- HurricaHjz/second-yourself★ 105same name
- cybaea/obsidian-vault-intelligence★ 79same name
- saksham10arora-dotcom/everything-claude-codex★ 74same name
28 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- about-oracleSkill
- awakenSkill
- bampenpienSkill
- budSkill
- create-shortcutSkill
- digSkill
- feelSkill
- forwardSkill
- goSkill
- incubateSkill
- learnSkill
- oracle-cheatsheetSkill
- oracle-family-scanSkill
- oracle-prismSkill
- philosophySkill
- psiSkill
- recapSkill
- resonanceSkill
- round-tableSkill
- rrrSkill
- soulSkill
- traceSkill
- where-we-areSkill
- who-are-youSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 32 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Never copy. Always symlink.
- Distinctive: line 78
Search for project across all locations:
- Distinctive: line 144
When listing, verify symlinks are valid:
- Very specific: line 151
If broken: ghq get -u [url] to restore source.
“Common” is measured: kept by at least 6 in 10 of the 32 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
project-manager
Track and manage external repos: Learn (study) | Incubate (develop)
Golden Rule
ghq owns the clone → ψ/ owns the symlink
Never copy. Always symlink. One source of truth.
When to Use
Invoke this skill when:
- User shares a GitHub URL and wants to study/clone it
- User mentions wanting to learn from a codebase
- User wants to start developing on an external repo
- Need to find where a previously cloned project lives
Step 0 — Anchor (date-stamp + root)
date "+🕐 %H:%M %Z (%A %d %B %Y)"
# Find oracle root — git toplevel that has CLAUDE.md + ψ/
ORACLE_ROOT=$(git rev-parse --show-toplevel 2>/dev/null)
if [ -n "$ORACLE_ROOT" ] && [ -f "$ORACLE_ROOT/CLAUDE.md" ] && { [ -d "$ORACLE_ROOT/ψ" ] || [ -L "$ORACLE_ROOT/ψ" ]; }; then
PSI="$ORACLE_ROOT/ψ"
elif [ -f "$(pwd)/CLAUDE.md" ] && { [ -d "$(pwd)/ψ" ] || [ -L "$(pwd)/ψ" ]; }; then
ORACLE_ROOT="$(pwd)"
PSI="$ORACLE_ROOT/ψ"
else
echo "⚠️ Not in oracle repo (no CLAUDE.md + ψ/ at git root). Writing to pwd."
ORACLE_ROOT="$(pwd)"
PSI="$ORACLE_ROOT/ψ"
fiActions
learn [url|slug]
Clone repo for study (read-only reference).
# 1. Clone via ghq
ghq get -u https://github.com/owner/repo
# 2. Create org/repo symlink structure
GHQ_ROOT=$(ghq root)
mkdir -p "$PSI/learn/owner"
ln -sf "$GHQ_ROOT/github.com/owner/repo" "$PSI/learn/owner/repo"Output (announce-mode — absolute path):
announce-mode → absolute path (no ψ/, no ~/, no $VAR, no ...).
Use: echo "marker: $RESOLVED_PATH" — bash substitutes. See CONVENTIONS.md.
LINK="$PSI/learn/owner/repo"
echo "✅ Linked: $LINK"incubate — REDIRECTS TO /incubate
/project incubateis now/incubate. If the user says/project incubate [args], run/incubate [args]instead. Do NOT execute incubate logic here — invoke the standalone/incubateskill with the same arguments.
find [query]
Search for project across all locations:
# Search ghq repos
ghq list | grep -i "query"
# Search learn/incubate symlinks (org/repo structure)
find "$PSI/learn" "$PSI/incubate" -type l 2>/dev/null | grep -i "query"Output: List matches with their ghq paths
list
Show all tracked projects with rich metadata (#227):
echo "📦 Projects"
echo ""
# Collect all tracked repos (learn + incubate symlinks)
REPOS=()
for link in $(find "$PSI/learn" "$PSI/incubate" -name "origin" -type l 2>/dev/null | sort); do
dir=$(dirname "$link")
owner=$(basename "$(dirname "$dir")")
repo=$(basename "$dir")
type="learn"
echo "$link" | grep -q "incubate" && type="incubate"
REPOS+=("$owner/$repo:$type")
done
if [ ${#REPOS[@]} -eq 0 ]; then
echo " No tracked projects. Use /learn or /incubate to add."
else
printf " %-35s %-6s %-8s %-8s %s\n" "Repo" "Stars" "License" "Type" "Description"
printf " %-35s %-6s %-8s %-8s %s\n" "───────────────────────────────────" "──────" "────────" "────────" "──────────────────────"
for entry in "${REPOS[@]}"; do
slug="${entry%%:*}"
type="${entry##*:}"
# Fetch metadata from GitHub (cached per session)
meta=$(gh api "repos/$slug" --jq '"\(.stargazers_count)\t\(.license.spdx_id // "none")\t\(.description // "-" | .[0:40])"' 2>/dev/null || echo "?\tnone\t-")
stars=$(echo "$meta" | cut -f1)
license=$(echo "$meta" | cut -f2)
desc=$(echo "$meta" | cut -f3)
printf " %-35s %-6s %-8s %-8s %s\n" "$slug" "⭐$stars" "$license" "$type" "$desc"
done
fi
echo ""
echo " Total: ${#REPOS[@]} tracked repos"Directory Structure
ψ/
├── learn/owner/repo → ~/Code/github.com/owner/repo (symlink)
└── incubate/owner/repo → ~/Code/github.com/owner/repo (symlink)
~/Code/ ← ghq root (source of truth)
└── github.com/owner/repo/ (actual clone)Health Check
When listing, verify symlinks are valid:
# Check for broken symlinks
find "$PSI/learn" "$PSI/incubate" -type l ! -exec test -e {} \; -print 2>/dev/nullIf broken: ghq get -u [url] to restore source.
Examples
# User shares URL to study
User: "I want to learn from https://github.com/SawyerHood/dev-browser"
→ ghq get -u https://github.com/SawyerHood/dev-browser
→ mkdir -p ψ/learn/SawyerHood
→ ln -sf ~/Code/github.com/SawyerHood/dev-browser ψ/learn/SawyerHood/dev-browser
# User wants to develop → redirect to /incubate
User: "I want to work on claude-mem"
→ /incubate https://github.com/thedotmack/claude-mem
# User says "/project incubate" → redirect to /incubate
User: "/project incubate https://github.com/Soul-Brews-Studio/arra-oracle-v3 --contribute"
→ /incubate https://github.com/Soul-Brews-Studio/arra-oracle-v3 --contributeAnti-Patterns
| ❌ Wrong | ✅ Right |
git clone directly to ψ/ | ghq get then symlink |
Flat: ψ/learn/repo-name | Org structure: ψ/learn/owner/repo |
| Copy files | Symlink always |
| Manual clone outside ghq | Everything through ghq |
Quick Reference
# Add to learn
ghq get -u URL && mkdir -p "$PSI/learn/owner" && ln -sf "$(ghq root)/github.com/owner/repo" "$PSI/learn/owner/repo"
# Incubate (use standalone /incubate skill)
/incubate URL [--flash | --contribute | --status | --offload]
# Update source
ghq get -u URL
# Find repo
ghq list | grep nameDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

