skill-seekers-reference/CREATE_COMMAND_COVERAGE_ANALYSIS.md

Create Command vs Individual Scrapers - Coverage Analysis

Analysis Date: 2026-02-16
Question: Can create command replace all individual scrapers?

---

✅ VERDICT: YES - Create Command Has Full Coverage

After comprehensive analysis, skill-seekers create CAN replace all individual scrapers with equivalent functionality.

---

Source Type Coverage

Source Type	Individual Command	Create Command	Status
Documentation	scrape	create https://...	✅ Full parity
GitHub	github	create owner/repo	✅ Full parity
Local Code	analyze	create ./path	✅ Full parity
PDF	pdf	create file.pdf	✅ Full parity
Multi-Source	unified	create config.json	✅ Full parity

---

Feature Parity by Source Type

1. Documentation Scraping (scrape → create)

Feature	scrape	create	Status
URL scraping	✅	✅	Full
Config file (--config)	✅	✅	Full
Max pages (--max-pages)	✅	✅	Full
Skip scrape (--skip-scrape)	✅	✅	Full
Resume (--resume)	✅	✅	Full
Fresh start (--fresh)	✅	✅	Full
Rate limit (-r)	✅	✅	Full
Workers (-w)	✅	✅	Full
Async mode (--async)	✅	✅	Full
Enhancement workflows	✅	✅	Full
RAG chunking	✅	✅	Full

Gap Analysis:

• scrape has --interactive mode (interactive config builder)
• create does NOT expose --interactive directly
• Workaround: Users can use --config with pre-built config

Verdict: 95% parity - only missing interactive wizard

---

2. GitHub Scraping (github → create)

Feature	github	create	Status
Repo scraping (--repo)	✅	✅ (auto)	Full
GitHub token (--token)	✅	✅	Full
Profile (--profile)	✅	✅	Full
Non-interactive (--non-interactive)	✅	✅	Full
Skip issues (--no-issues)	✅	✅	Full
Skip changelog (--no-changelog)	✅	✅	Full
Skip releases (--no-releases)	✅	✅	Full
Max issues (--max-issues)	✅	✅	Full
Scrape only (--scrape-only)	✅	✅	Full
Local repo path (--local-repo-path)	✅	✅	Full
Enhancement workflows	✅	✅	Full

Gap Analysis:

• github has --config to load from JSON file
• create also has --config for additional settings
• github shows repo in help; create auto-detects

Verdict: 100% parity

---

3. Local Code Analysis (analyze → create)

Feature	analyze	create	Status
Directory analysis (--directory)	✅	✅ (auto)	Full
Preset (--preset)	✅	✅	Full
Languages (--languages)	✅	✅	Full
File patterns (--file-patterns)	✅	✅	Full
Skip patterns (--skip-patterns)	✅	✅	Full
Skip test examples (--skip-test-examples)	✅	✅	Full
Skip how-to guides (--skip-how-to-guides)	✅	✅	Full
Skip config (--skip-config)	✅	✅	Full
Skip docs (--skip-docs)	✅	✅	Full
Enhancement workflows	✅	✅	Full

Gap Analysis:

• analyze has --preset-list (show available presets)
• create does NOT have --preset-list
• analyze has deprecated flags (--quick, --comprehensive, --depth)
• create uses clean --preset approach

Verdict: 95% parity - only missing preset list

---

4. PDF Extraction (pdf → create)

Feature	pdf	create	Status
PDF file (--pdf)	✅	✅ (auto)	Full
OCR (--ocr)	✅	✅	Full
Page range (--pages)	✅	✅	Full
Enhancement workflows	✅	✅	Full

Verdict: 100% parity

---

5. Multi-Source (unified → create)

Feature	unified	create	Status
Config file (--config)	✅	✅	Full
Merge mode (--merge-mode)	✅	✅	Full
Fresh start (--fresh)	✅	✅	Full
Dry run (--dry-run)	✅	✅	Full

Verdict: 100% parity

---

Arguments NOT in Create Command (Intentional)

These are intentionally excluded or handled differently:

Argument	Reason
--interactive (scrape)	Use --config instead
--preset-list (analyze)	Use workflows list instead
--url (scrape)	Auto-detected from source
--repo (github)	Auto-detected from source
--directory (analyze)	Auto-detected from source
--quick/--comprehensive/--depth	Deprecated, use --preset

---

Create Command Advantages

Feature	Create	Individual
Auto-detection	✅ Source type auto-detected	❌ Must specify command
Unified interface	✅ One command for all	❌ Different commands
Progressive help	✅ --help-web, --help-github, etc.	❌ Single help output
Argument validation	✅ Warns about incompatible args	❌ Silent failures
Future-proof	✅ New sources automatic	❌ Need new commands

---

Minor Gaps (Non-Critical)

1. Interactive Config Builder

# Individual scraper only
skill-seekers scrape --interactive

# Create workaround
skill-seekers create https://example.com/ --config my-config.json
# (Build config separately or use defaults)

2. Preset List

# Individual scraper only  
skill-seekers analyze --preset-list

# Create workaround
skill-seekers workflows list
# (Shows workflow presets, similar concept)

---

Migration Path

Users can migrate from individual commands to create:

# Before
skill-seekers scrape --config configs/react.json
skill-seekers github --repo facebook/react --name react
skill-seekers analyze --directory ./my-project --preset comprehensive
skill-seekers pdf --pdf manual.pdf --name docs

# After (equivalent)
skill-seekers create --config configs/react.json
skill-seekers create facebook/react --name react
skill-seekers create ./my-project --preset comprehensive
skill-seekers create manual.pdf --name docs

---

Recommendation

You are correct - there is NO critical gap with the create command.

What works:

• ✅ All 5 source types covered
• ✅ All major features supported
• ✅ Enhancement workflows work
• ✅ RAG chunking works
• ✅ All platform packaging works

What's missing (minor):

• Interactive config builder (can use --config instead)
• Preset list (can use workflows list instead)

Verdict:

create command can fully replace individual scrapers. The minor gaps are UX conveniences, not functional limitations.

---

Suggested Actions

1. Promote create as primary command in documentation
2. Deprecate individual commands slowly (add warnings)
3. Add --interactive to create if needed for parity
4. Keep individual commands for backward compatibility

---

Analysis confirms: create command has no critical gaps.