Research technical solutions by searching the web, examining GitHub repos, and gathering evidence. Use when exploring implementation options or evaluating technologies.
Installation
Details
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
skills listSkill Instructions
name: ark-research description: Research technical solutions by searching the web, examining GitHub repos, and gathering evidence. Use when exploring implementation options or evaluating technologies.
Ark Research
Research technical solutions and gather evidence before implementation.
Research Process
1. Web Search First
Always start with web search to find:
- Official documentation
- GitHub repositories
- Blog posts and tutorials
- Protocol specifications (PDFs, RFCs)
2. Examine GitHub Repositories
GitHub raw content is often blocked. Clone repos to examine them:
cd /tmp
git clone https://github.com/owner/repo.git
cat /tmp/repo/README.md
Look for:
- README documentation
- Code examples
- Architecture patterns
- Dependencies and requirements
3. Handle Blocked Content
If a website cannot be loaded:
- Ask the user to paste the relevant content
- Request PDFs or specification documents
- Ask for screenshots if visual content is needed
Example prompt:
"I found a relevant resource at [URL] but cannot access it. Could you paste the key content or provide the PDF?"
4. Local Research Workspace
Store findings in ./scratch/research/ for review:
mkdir -p ./scratch/research
Save:
- Cloned repo summaries
- Code snippets
- Architecture diagrams
- Comparison notes
5. Evidence Requirements
Minimum 2-3 datapoints required before recommending a solution:
- GitHub repo with active maintenance
- Documentation or specification
- Real-world usage examples
- Community feedback (issues, discussions)
If insufficient evidence, ask for guidance:
"I found only one reference to this approach. Can you point me to additional resources or clarify the requirements?"
Output Format
Always back up findings with sources:
## Research: [Topic]
### Option 1: [Solution Name]
- **Source**: [URL or repo link]
- **Pros**: ...
- **Cons**: ...
- **Evidence**: [What confirms this works]
### Option 2: [Solution Name]
...
### Recommendation
Based on [N] sources, I recommend [Option] because...
### Sources
- [Title](URL)
- [Repo](GitHub URL) - cloned and examined
- [Spec](URL) - user provided
Example Usage
User: "Research options for terminal recording in an MCP server"
- Web search: "terminal recording library node typescript"
- Find GitHub repos → clone to /tmp and examine
- Find asciinema, VHS, xterm.js
- Compare approaches in ./scratch/research/terminal-recording.md
- Present options with 2-3 sources each
More by mckinsey
View allRegenerate and debug types across the ARK stack (SDK, API, Dashboard). Use when fixing TypeScript type errors in ark-dashboard, updating types after CRD changes, regenerating types.ts from OpenAPI spec, debugging "Property does not exist on type" schema errors, or adding custom SDK functionality via overlays. Covers the full type pipeline from Kubernetes CRDs to TypeScript.
Analyze the Ark codebase by cloning the repository to a temporary location. Use this skill when the user asks questions about how Ark works, wants to understand Ark's implementation, or needs to examine Ark source code.
Guidance for developing the Ark Kubernetes operator. Use when modifying Go types, CRDs, controllers, or webhooks. Helps with CRD generation and Helm chart sync issues.
CVE research and security patch workflow for Ark. Provides CVE API integration, mitigation strategies, and security-focused PR templates. Works with research, analysis, and setup skills for comprehensive vulnerability fixing.
