no-runtime-code

Enforce guardrails preventing handwritten runtime code in pipeline artifacts.

1|Updated Oct 1, 2025
One-click install
npx skills add https://github.com/GodSpeedAI/SEA --skill no-runtime-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: no-runtime-code
Source: https://github.com/GodSpeedAI/SEA/tree/main/.claude/skills/no-runtime-code
Command: npx skills add https://github.com/GodSpeedAI/SEA --skill no-runtime-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pipelines often risk running handwritten runtime code, which can bypass governance and introduce security and reliability issues. This Skill locks in strict guardrails to keep specs, SEA™ models, and generators as the sole sources of truth and execution logic.

Core Features & Use Cases

  • Guardrails enforcement: Prevents runtime code in CI/CD and deployment pipelines by validating artifacts and templates against approved models.
  • Policy alignment: Ensures specs, SEA™ definitions, and generator templates remain authoritative, versioned, and free of ad-hoc code.
  • Use Case: A team upgrades a template-driven workflow and wants to guarantee no custom runtime scripts are introduced; this Skill enforces the constraint across all pipeline artifacts.

Quick Start

Review your pipeline specification and generator templates to confirm that no handwritten runtime code is present and that only permitted artifacts are used.

Frequently Asked Questions about no-runtime-code

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

FAQPage Schema
How do I prevent handwritten runtime code in CI/CD pipelines?

To prevent handwritten runtime code in CI/CD pipelines, enforce strict guardrails that validate all deployment artifacts and templates against approved specs and SEA™ definitions. This ensures pure, deterministic execution by bypassing ad-hoc scripts.

What are pipeline guardrails for specs and generator workflows?

Pipeline guardrails for specs and generator workflows are constraints codified within SDS and SEA models. They enforce policy by validating artifacts against approved templates, guaranteeing that no custom runtime scripts are introduced during deployments.

How do I enforce deterministic execution in deployment pipelines?

You can enforce deterministic execution in deployment pipelines by applying guardrails that lock in specs, SEA™ definitions, and generator templates as the sole sources of execution logic. This prevents runtime code from altering the deployment flow.

Does this approach require modifying existing SDS or SEA mapping rules?

No, this approach does not require runtime changes. It codifies constraints directly within existing SDS and SEA mapping rules to enforce governance policies, ensuring the validation process remains purely structural and model-driven.

When should I not use runtime code guardrails in my pipeline?

You should avoid relying solely on runtime code guardrails if your workflow explicitly requires executing custom ad-hoc scripts outside of approved specs and SEA™ models, as these constraints are designed to block non-deterministic runtime modifications entirely.