skills.rest
quanganh208
quanganh208COMMUNITY
Explore all skills by this author →
GitHub

ck:research

Research technical solutions and architecture trade-offs, then generate timestamped Markdown reports.

1|Updated Mar 6, 2026
Search Tags:#architecture#research#scalability#best-practices#security-analysis#report-generation#technology-evaluation
One-click install
npx skills add https://github.com/quanganh208/cookmate --skill ck-research-quanganh208
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:research
Source: https://github.com/quanganh208/cookmate/tree/main/.opencode/skills/research
Command: npx skills add https://github.com/quanganh208/cookmate --skill ck-research-quanganh208

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, repeatable process to research and evaluate technical solutions, analyze system architectures, and produce actionable, citation-backed reports so teams can make informed design and technology decisions quickly.

Core Features & Use Cases

  • Scope Definition: Guides clear scoping of research, recency requirements, and evaluation criteria to avoid scope creep.
  • Multi-Source Investigation: Orchestrates searches across web sources and optional Gemini model usage with fallbacks, prioritizing official docs, reputable repos, and expert content.
  • Deep Analysis & Validation: Performs cross-reference validation, repository and docs inspection, security/CVE checks, and assesses scalability, performance, and maintainability trade-offs.
  • Report Generation: Produces timestamped, structured Markdown reports with TOC, code examples, diagrams, and clear next steps tailored for architecture reviews, migration plans, and technology selection.
  • Use Cases: Tech stack evaluation, security and performance assessments, migration planning, and design decision justification.

Quick Start

Use ck:research to evaluate scalability, security, and cost trade-offs for migrating a monolithic Java backend to microservices and produce a timestamped decision report.

Frequently Asked Questions about ck:research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I research technical solutions and analyze architecture trade-offs for software systems?▼

To research technical solutions and analyze architecture trade-offs, define your scope and evaluation criteria, then apply multi-source validation against official documentation to generate a timestamped markdown report with actionable recommendations.

What is the best way to evaluate technology stack scalability and security before a migration?▼

Evaluating technology stack scalability and security requires cross-referencing official docs, inspecting repositories, and checking CVE databases to assess performance and maintainability trade-offs, culminating in a structured decision report.

How do I generate a technical decision report for migrating a monolithic backend to microservices?▼

Generating a technical decision report for migrating a backend to microservices involves orchestrating web searches, validating architecture trade-offs, and producing a timestamped markdown document with a table of contents, code examples, and next steps.

Can I use web search and Gemini models to validate infrastructure and API ecosystem design decisions?▼

Yes, you can validate infrastructure and API ecosystem design decisions by orchestrating up to five tool calls using optional Gemini or WebSearch fallbacks to cross-reference reputable repositories and expert content.

Does technology evaluation require official documentation citations to justify design decisions?▼

Yes, technology evaluation requires multi-source validation and citation of official documentation to justify design decisions, ensuring that architecture reviews and migration plans are backed by reputable, cross-referenced data.

What are the limitations of using automated research for security and scalability analyses?▼

Limitations of automated security and scalability analyses include dependency on web search depth, up to five tool call constraints, and the need to manually define recency requirements to prevent scope creep during technology evaluation.

Related Skills

Explore More Software Engineering Skills→
mortenbroesbymortenbroesby
1

spec-driven-development

Define a precise specification with objectives, constraints, and acceptance criteria before coding.

Community
Intermediate
tangzheng202202tangzheng202202
1

plan

Generate a structured Markdown plan saved to .hermes/plans/.

Community
Intermediate
doodledooddoodledood
4

research-web

Plan, execute, and synthesize multi-wave web research findings.

Community
Advanced
rysweetrysweet
1

engineer-analyst

Analyze technical systems using engineering frameworks and quantitative methods.

Community
Advanced