ak-research

name	ak:research
description	Research technical solutions, analyze architectures, gather requirements thoroughly. Use for technology evaluation, best practices research, solution design, scalability/security/maintainability analysis.
user-invocable	true
when_to_use	Invoke for deep technical research before implementation.
category	utilities
keywords	["research","evaluation","analysis","solutions"]
license	MIT
argument-hint	[topic]
metadata	{"author":"agentkit","version":"1.0.0"}

Research

Research Methodology

Always honoring YAGNI, KISS, and DRY principles. Be honest, be brutal, straight to the point, and be concise.

Phase 1: Scope Definition

First, you will clearly define the research scope by:

• Identifying key terms and concepts to investigate
• Determining the recency requirements (how current must information be)
• Establishing evaluation criteria for sources
• Setting boundaries for the research depth

Phase 2: Systematic Information Gathering

You will employ a multi-source research strategy:

1. Search Strategy:

   • Use the runtime's native web_search capability for current external research.
   • Treat legacy .claude/.ck.json keys skills.research.useGemini and gemini.model as compatibility input only; they do not enable retired CLI dispatch.
   • Run multiple independent web_search capability queries in parallel when the runtime supports parallel tool calls.
   • Craft precise search queries with relevant keywords
   • Include terms like "best practices", "2024", "latest", "security", "performance"
   • Search for official documentation, GitHub repositories, and authoritative blogs
   • Prioritize results from recognized authorities (official docs, major tech companies, respected developers)
   • IMPORTANT: You are allowed to perform at most 5 researches (max 5 tool calls), user might request less than this amount, strictly respect it, think carefully based on the task before performing each related research topic.

2. Deep Content Analysis:

   • When you found a potential Github repository URL, use ak:docs-seeker skill to find read it.
   • Focus on official documentation, API references, and technical specifications
   • Analyze README files from popular GitHub repositories
   • Review changelog and release notes for version-specific information

3. Video Content Research:

   • Prioritize content from official channels, recognized experts, and major conferences
   • Focus on practical demonstrations and real-world implementations

4. Cross-Reference Validation: