research-external

Solid

External research workflow for docs, web, APIs - NOT codebase exploration

AI & Automation 501 stars 42 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
90
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# External Research Workflow Research external sources (documentation, web, APIs) for libraries, best practices, and general topics. > **Note:** The current year is 2025. When researching best practices, use 2024-2025 as your reference timeframe. ## Invocation ``` /research-external <focus> [options] ``` ## Question Flow (No Arguments) If the user types just `/research-external` with no or partial arguments, guide them through this question flow. Use AskUserQuestion for each phase. ### Phase 1: Research Type ```yaml question: "What kind of information do you need?" header: "Type" options: - label: "How to use a library/package" description: "API docs, examples, patterns" - label: "Best practices for a task" description: "Recommended approaches, comparisons" - label: "General topic research" description: "Comprehensive multi-source search" - label: "Compare options/alternatives" description: "Which tool/library/approach is best" ``` **Mapping:** - "How to use library" → library focus - "Best practices" → best-practices focus - "General topic" → general focus - "Compare options" → best-practices with comparison framing ### Phase 2: Specific Topic ```yaml question: "What specifically do you want to research?" header: "Topic" options: [] # Free text input ``` Examples of good answers: - "How to use Prisma ORM with TypeScript" - "Best practices for error handling in Python" - "React vs Vue vs Sve...

Details

Author
vibeeval
Repository
vibeeval/vibecosystem
Created
2 months ago
Last Updated
yesterday
Language
C#
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category