seis-hub

Coordinates SEIS repository consolidation, plugin iteration, and migration safety workflows on GitHub.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing a multi-repository ecosystem like SEIS involves risky operations: consolidating scattered repositories, migrating source repos safely, keeping plugin marketplaces in sync, and deciding when old repositories can be deleted. This Skill provides a governed operating lane so these tasks follow verified, auditable procedures instead of ad-hoc commands. ## Core Features & Use Cases - Repository Consolidation & Migration Safety: Consolidate repositories under the canonical emirhankudun-ux/SEIS repo, verify sources/<repo>/<branch> refs and snapshots, and gate source repository deletion behind authenticated import verification. - Plugin Development & Validation: Create and update SEIS-connected Codex plugins, validate manifests with validate_plugin.py, and use the cachebuster/reinstall flow for marketplace-backed updates. - Audit & Status Scripts: Run bundled shell scripts for status checks, zip audits, repo visibility audits, main-branch sync, and installed-plugin audits before making changes. - Use Case: You want to delete an old source repository after migrating it into SEIS. The Skill walks you through verifying branch refs and file snapshots first, then only permits deletion via the gated DRY_RUN=0 DELETE_SOURCE_REPOS=1 migration script. ## Quick Start Ask the assistant to check SEIS repository status and verify whether a migrated source repository is safe to delete.

Frequently Asked Questions about seis-hub

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

FAQPage Schema
How do I consolidate multiple repositories into SEIS?▼

Repository consolidation imports source repos under the canonical emirhankudun-ux/SEIS repository, preserving sources/<repo>/<branch> refs and repositories/<repo> snapshots. Run the status and visibility audit scripts first, then verify refs before considering any deletion.

When is it safe to delete an old source repository after migration?▼

Deletion is safe only after authenticated import succeeds and SEIS contains verified branch refs plus file snapshots. A marker file like MOVED_TO_SEIS.md is not sufficient proof. The final gated command is DRY_RUN=0 DELETE_SOURCE_REPOS=1 scripts/migrate-repositories-to-seis-depot.sh.

How do I validate a SEIS Codex plugin before publishing?▼

Validate the plugin manifest with plugin-creator/scripts/validate_plugin.py against the plugin directory, and check shell scripts with bash -n. For marketplace-backed updates, use the cachebuster/reinstall flow rather than hand-editing marketplace entries.

Can I commit a large workspace zip directly into SEIS?▼

No. Audit the zip first with seis-zip-audit.sh, then import only curated source snapshots or use Git LFS/object storage for binary archives. Zips containing .git, __MACOSX, virtual environments, SDKs, or build caches are treated as source archives, not normal repo source.

What should I do when old repositories seem missing on GitHub?▼

Run seis-repo-visibility-audit.sh to diagnose visibility, then use seis-main-branch-sync.sh to make main mirror the canonical branch so visitors land on the same content. Keep sources/<repo>/<branch> refs as recovery and index refs.