seis-research

Conducts evidence-led technical research with source evaluation and decision synthesis for SEIS.

1|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/emirhankudun-ux/SEIS --skill seis-research-emirhankudun-ux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: seis-research
Source: https://github.com/emirhankudun-ux/SEIS/tree/main/plugins/seis-research/skills/seis-research
Command: npx skills add https://github.com/emirhankudun-ux/SEIS --skill seis-research-emirhankudun-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering and architecture decisions often depend on external facts like current documentation, standards, versions, and ecosystem behavior. This Skill structures that research so SEIS decisions rest on verified primary sources rather than assumptions or stale information. ## Core Features & Use Cases - Source Quality Control: Prioritizes official documentation, standards, release notes, and primary repositories over secondary sources. - Evidence Verification: Checks version, date, compatibility, licensing, and security implications before research becomes implementation guidance. - Decision-Ready Output: Produces structured findings with decision question, sources consulted, recommendations, risks, and next steps. - Use Case: Before adopting a new deployment platform for SEIS, use this Skill to review official docs, verify pricing and security posture, compare alternatives, and produce an ADR-ready recommendation with provenance. ## Quick Start Use the seis-research skill to investigate whether SEIS should adopt a specific platform or standard, citing official sources and flagging any security or licensing risks.

Frequently Asked Questions about seis-research

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

FAQPage Schema
How do I research a technical decision with verified sources?▼

Define the decision question and the artifact that will consume the answer, then consult primary sources such as official docs, standards, and release notes. Verify version, date, compatibility, and licensing before converting findings into implementation guidance.

What sources should I trust for platform and vendor research?▼

Use official documentation from providers like Apple, Google, Microsoft, OpenAI, GitHub, Cloudflare, Vercel, and Supabase first. Use primary repository docs and release notes for open-source packages, and treat secondary sources as context only.

How should research findings be documented for architecture decisions?▼

Return the decision question, sources consulted, findings, recommendation, security or licensing risk, and a validation next step. Preserve provenance in durable repo artifacts such as ADRs when research affects architecture, security, or public docs.

When should secondary sources not be used for decisions?▼

Secondary sources should never be the sole basis for high-impact decisions. They are acceptable only for context, while facts about versions, availability, and security must come from primary documentation.

How do I handle stale or unverified evidence in research?▼

Mark stale, partial, connector-gated, or unauthenticated evidence clearly in the output. Never invent dates, versions, product availability, or authentication status to fill gaps.