Project initialization inventory and cache generation (one-time intake). Use when first onboarding a project or after major structural changes.
Scanned 2/12/2026
Install via CLI
openskills install sd0xdev/sd0x-dev-flow---
name: repo-intake
description: Project initialization inventory and cache generation (one-time intake). Use when first onboarding a project or after major structural changes.
allowed-tools: Read, Grep, Glob, Bash(git:*), Bash(node:*)
context: fork
agent: Explore
disable-model-invocation: true
---
# Repo Intake
## When to Use
- First time onboarding a project
- Rebuilding cache after major project structural changes
- Cache expired, needs updating
## When NOT to Use
- Already familiar with project structure (read cache directly)
- Only need to find specific files (use Glob/Grep)
- Day-to-day development (cache already exists)
## Workflow
```
Docs -> Entrypoints -> Tests Map -> Next Steps
```
## Usage
```bash
node skills/repo-intake/scripts/intake_cached.js --mode auto --top 10
```
## Cache Location
Cache stored at: `~/.claude/cache/repo-intake/<repoKey>/`
| File | Description |
| ------------- | ----------------------- |
| `latest.md` | Latest scan results |
| `latest.json` | Latest scan results (JSON) |
| `LATEST.json` | Cache metadata |
## Verification
- Output includes Overview, Entrypoints, Test Map, Next Steps
- Entrypoints correctly identify `{CONFIG_FILE}`, `{BOOTSTRAP_FILE}`
- Test Map covers Unit/Integration/E2E layers
## Output Format
```markdown
## Overview
<summary>
## Entrypoints
- {CONFIG_FILE}
- {BOOTSTRAP_FILE}
## Test Map
| Type | Pattern |
| ----------- | ----------------- |
| Unit | test/unit/ |
| Integration | test/integration/ |
| E2E | test/e2e/ |
## Next Steps
- <questions>
```
## Examples
```
Input: /midway-intake
Action: Execute intake script -> Output project map
```
```
Input: /midway-intake save
Action: Execute intake script -> Output and write to docs/ai/intake/
```
No comments yet. Be the first to comment!
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.