Menu
Research technical options with source-backed recommendations. Use for technology evaluation, architecture trade-offs, library/framework choices, best practices, scalability, security, maintainability, or when current external facts matter.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Build and maintain an internal technical LLM wiki when the user requests wiki work or a verified major or architectural change qualifies for automatic wiki review. Use for project memory, architecture notes, contracts, runbooks, decisions, glossary, incremental ingest, delta status, and wiki health. Do not use merely because a routine task or plan completed.
Explore ambiguous ideas and solution directions before evidence-backed research or implementation planning. Use for ideation, framing, assumption checks, option generation, product or architecture trade-offs, and deciding whether research or a plan is needed.
Create implementation plans, architecture decisions, and phased roadmaps. Use for Standard or Complex changes, new pipelines, schema changes, migrations, multi-file features, technology choices, or when acceptance criteria and verification strategy are unclear.
Review code and data pipeline changes for correctness, security, performance, maintainability, contract breaks, and missing verification. Use before merge, after implementation, for PRs, commits, pending diffs, or codebase risk scans.
Design data ingestion into landing/bronze layers. Use for source onboarding, transfer pattern selection, full/incremental/CDC scope, change detection, landing zones, schema drift, idempotent file or batch processing, and ingestion quality gates.
Design warehouse and semantic data models. Use for grain definition, fact/dimension design, star schema, Kimball, Data Vault, SCD, bridge tables, surrogate keys, semantic metrics, and model review.
| name | research |
| description | Research technical options with source-backed recommendations. Use for technology evaluation, architecture trade-offs, library/framework choices, best practices, scalability, security, maintainability, or when current external facts matter. |
Use this skill to answer technical questions with evidence and a ranked recommendation.
Research is convergent and source-backed. It is not for open-ended ideation.
research when the answer depends on current facts, external sources, standards, benchmarks, vendor behavior, or source-backed recommendations.brainstorm first when the user is still exploring ideas, framing the problem, or comparing unsourced solution directions.plan after a recommendation is selected and the implementation is Standard or Complex.scout, wiki, or the relevant implementation skill before external research.Compare options on criteria relevant to the task:
When giving suggestions or proposals, present 2-3 viable options unless there is only one safe or practical choice. Mark one option as recommended and explain why it is the best default for the user's context.
Recommendation: <recommended option and reason>
Why:
- ...
Options considered:
| Option | Pros | Cons | Risk |
Evidence:
- <source/link/date>
Implementation notes:
- ...
Open questions:
- ...
Do not produce a long reading list without a decision.