seis-ai-agent

Orchestrates SEIS repository work across governance, cloud, code, design, and data lanes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working across the SEIS ecosystem means choosing between many specialist lanes (governance, cloud, code, design, data) without duplicating plugins or creating parallel structures. This Skill provides a single versioned orchestration surface that routes every request to the smallest useful lane while keeping all work inside the canonical SEIS repository. ## Core Features & Use Cases - Unified Lane Routing: Classifies incoming requests into SEIS, SEIS-Cloud, SEIS-Code, SEIS-Design, or SEIS-Data lanes and applies the matching workflow rules. - Repository Safety Gates: Inspects git status, branch, and remotes first, and keeps destructive operations such as deletions, cloud deploys, and secret-bearing changes behind explicit confirmation. - Consolidation Governance: Treats specialist plugin packages as repo-contained source mirrors behind one canonical install id (seis-ai-agent@seis-repo), preventing duplicate public installs. - Use Case: A maintainer asks to prepare a cloud deployment and update docs; the Skill checks repo safety, routes the deployment work to SEIS-Cloud and the documentation work to the SEIS lane, then validates with the scoped npm check scripts. ## Quick Start Ask the agent to handle a SEIS repository task, for example: review the current git state and route my cloud deployment readiness request through the unified SEIS-Agent workflow.

Frequently Asked Questions about seis-ai-agent

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

FAQPage Schema
How do I route a task to the right SEIS lane?▼

Classify the request into the smallest useful lane: SEIS for governance and architecture, SEIS-Cloud for deployment readiness, SEIS-Code for implementation and CI, SEIS-Design for UI and design systems, and SEIS-Data for analytics and registries. The unified workflow defines these boundaries explicitly.

How do I validate changes made through the SEIS-Agent workflow?▼

Run the scoped checks first: npm run check:seis-ai-agent, check:seis-unified-plugin-suite, check:seis-specialist-plugins, and check:seis-operating-identities. Scale to npm run quality only when the change touches shared governance, generated reports, plugin contracts, or public repo readiness.

Can I install the specialist SEIS lane plugins separately?▼

No. The consolidation rules require seis-ai-agent@seis-repo as the single canonical install, with specialist packages treated as embedded source mirrors inside the repo. Their skills, MCP servers, and validation contracts stay testable but are not separate public installs.

What safety checks happen before destructive repository operations?▼

The workflow inspects git status, current branch, and remotes before acting. Repository deletion, cloud apply or deploy commands, secret-bearing operations, and destructive plugin changes all require explicit human confirmation before proceeding.

What are the limitations of the unified SEIS-Agent approach?▼

It is bound to the canonical emirhankudun-ux/SEIS repository and main branch, so it does not operate as a general-purpose agent outside that context. The legacy personal plugin family also cannot be removed or rewritten without explicit human approval.