seis-integration-guardian

Enforces safe, documented practices for MCP, plugin, and provider integration work.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Integration work on MCP servers, plugins, skills, and AI providers often leads to leaked credentials, false claims about live provider access, and undocumented configuration changes. This Skill keeps that work safe, honest, and recorded. ## Core Features & Use Cases - Credential Protection: Prevents printing, storing, or committing API keys, tokens, SSH keys, and service accounts during integration work. - Honest Status Tracking: Keeps Missing Key, Disabled, Planned, Error, Mock, and Connected provider states distinct, and forbids claiming live access without verified tool calls. - Approval Gates: Requires explicit approval before cloud writes, GitHub writes, deployments, SSH, database mutations, or billing-impacting actions. - Use Case: When adding a new MCP server to the SEIS repository, the Skill guides inspection of existing configuration, secrets-free setup, and recording outcomes in inventory files like docs/platform/big-tech-mcp-skill-inventory.md. ## Quick Start Ask the assistant to review the current MCP and provider configuration in the SEIS repository and record the verified status of each integration in the inventory files.

Frequently Asked Questions about seis-integration-guardian

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

FAQPage Schema
How do I safely add a new MCP server to a repository?▼

Inspect the existing repository and tool state first, then prefer project-local, secrets-free configuration such as `.mcp.json`. Record the outcome in structured inventory files and never commit API keys or tokens.

How should AI provider connection status be tracked?▼

Keep Missing Key, Disabled, Planned, Error, Mock, and Connected states distinct in documentation. Only claim Connected status after a safe command or tool call verifies live access in the current session.

What actions require explicit approval during integration work?▼

Cloud writes, GitHub writes, deployments, SSH operations, database mutations, billing-impacting actions, and credential setup all require explicit user approval before execution.

Can integration credentials be stored in repository config files?▼

No. API keys, tokens, cookies, SSH keys, service accounts, and private profile data must never be printed, stored, or committed. Use secrets-free, project-local configuration instead.

Where should integration outcomes be documented?▼

Record durable outcomes in SEIS docs or structured inventory files such as `docs/platform/big-tech-mcp-skill-inventory.md` and `content/development/seis-big-tech-mcp-skill-inventory.json`.