From majestic-engineer
Researches technical problems across GitHub issues, Stack Overflow, Reddit, and documentation. Gathers structured solutions from multiple sources with executive summaries, options, and references. Useful for debugging and finding examples.
How this skill is triggered — by the user, by Claude, or both
Slash command
/majestic-engineer:web-researchThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Audience:** Developers debugging issues or researching solutions who need comprehensive findings from multiple sources.
Audience: Developers debugging issues or researching solutions who need comprehensive findings from multiple sources.
Goal: Search GitHub issues, Stack Overflow, Reddit, and docs to find relevant solutions and patterns.
| Source | What to Look For |
|---|---|
| GitHub Issues | Open and closed issues with matching symptoms |
| Stack Overflow | Accepted answers and high-vote alternatives |
| r/programming, r/webdev, topic-specific subreddits | |
| Official docs | Changelogs, migration guides, known issues |
| Blog posts | Tutorials, deep dives, experience reports |
| Hacker News | Technical discussions and alternative perspectives |
site: operator for targeted source searchinginurl:, intitle:, filetype: for precise results### Executive Summary
[Key findings in 2-3 sentences]
### Detailed Findings
#### Option 1: [Solution/Approach Name]
- Description
- Implementation details
- Pros and cons
- Source credibility
#### Option 2: [Alternative Solution]
[Continue as needed]
### Sources and References
[Direct links with brief descriptions]
### Recommendations
[Best approach based on research with trade-offs noted]
npx claudepluginhub majesticlabs-dev/majestic-marketplace --plugin majestic-engineerScans HN, Lobsters, Reddit, and tech blogs for community opinions and experience reports on technologies or approaches. Use for gathering perspectives.
Searches GitHub repos, issues, PRs, and code for proven solutions to concrete engineering problems, errors, integration failures, and implementation blockers.
Collects and ranks multi-source technical information (docs, GitHub, Stack Overflow, papers, blogs) before writing PRDs, ADRs, docs, or articles. Outputs a ranked source dossier to memory/research/.