phase-research
SolidRun Phase 1 Research only — keyword research, SERP analysis, competitor analysis, content gap analysis, surface targeting. Use when user wants research-only output without writing an article. Triggered by /seo-blog research, "research this keyword", "what's the SERP for X", "competitor analysis for".
Install
Quality Score: 86/100
Skill Content
Details
- Author
- XuanRanL
- Repository
- XuanRanL/loamwright-SEO-Skill
- Created
- 2 weeks ago
- Last Updated
- 3 days ago
- Language
- Python
- License
- Apache-2.0
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
research
Deep research with PRD methodology: Proposal → Baseline → Parallel Sub-Agent Team → Auto-Stitch → Lead Synthesis. Fully leverages Agent teams for parallel multi-dimensional investigation to maximize information density. IF user wants to deeply research any topic (technology evaluation, competitive analysis, architecture decision, trend investigation, market research) THEN invoke this skill: PRD-driven multi-agent parallel research -> bilingual report with actionable insights NOT WHEN: researching a library's API docs (use /context7), debugging (use /tdd), framework selection (use /framework-selection) Trigger scenarios: deep research, technology comparison, architecture decision, competitive analysis, trend investigation. Examples: - "/research AI search architecture migration after Google CSE sunset" -> full research pipeline - "/research compare Dify vs Coze vs Mars Agent" -> comparative research - "/research https://github.com/karpathy/autoresearch" -> GitHub project research - "/research livestream moneti
research
Deep online research on any topic. Produces structured reports with citations and confidence scores. Three depth modes — quick scan, standard investigation, or deep dive.
research
Starts Phase 1 (Research) for a topic: reads every relevant file, optionally runs a panel of Explore teammates, and saves a research artifact to .claude/state/research/. Use when the user says 'research <topic>' or '/research', or before planning work in unfamiliar code. Research only - proposes no solutions.