env-setup

Environment configuration and secrets management. Use when setting up .env files, managing secrets, or configuring environments.

Ir a la instalación

Repositorio: Tibsfox/gsd-skill-creator
Última actividad en el origen: 7 de julio de 2026 a las 04:19
Idioma detectado de SKILL.md: inglés
Estrellas: 69
Forks: 9

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/Tibsfox/gsd-skill-creator --skill env-setup

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

goal-ambiguity-gate

Use the moment a request is underspecified and you are about to act on an ASSUMED goal. Enumerate the candidate goals the request could mean, project the action or artifact each one implies, and check whether they diverge: if two or more plausible goals lead to materially different actions or artifacts, ask exactly ONE targeted clarifying question; otherwise proceed on the most-likely goal and state the assumption in one line. Clarification is an evidence-producing action, not a delay — but one question, never an interrogation. Distinct from gsd-spec-phase (GSD-phase-bound, emits a heavy SPEC.md) and intent-router (fetch strategy, not goal disambiguation). Backed by agent goal-state inference (arxiv 2606.16813v1). Triggers on acting under an assumed goal when the request admits more than one materially different reading.

2026-07-19

memory-hubness-gate

Use at write time to vector/embedding memory — Grove content-addressed insertion, chroma/pgvector upserts, memory-consolidation promoting session traces to MEMORY.md, or embedding externally-ingested content. Scores each candidate record against a fixed panel of sentinel queries and quarantines any record that would become the nearest neighbor of too many unrelated queries — a hub — whether from adversarial poisoning or accidental over-generality. This is the memory-record-side sibling of skill-injection-guardian (file-side) and the write-side complement of memory-use-warrant (read-side). Quarantine, never silently drop; a human reviews. Backed by the admission-time hubness gate (arxiv 2606.19692v1). Triggers on inserting into vector memory, consolidating memory, and embedding stranger content.

2026-07-19

memory-use-warrant

Run this appropriateness check the moment you are about to integrate a retrieved long-term memory — a Grove content-addressed hit, a chroma/pgvector neighbour, a memory-consolidation digest, or a MEMORY.md line — into a response, especially anything touching private origins, Fox Companies IP, credentials, or Center Camp / consent-governed content. It answers a question intent-router never asks: not WHAT to fetch or HOW, but WHETHER a correctly-retrieved item should reach output. Relevance is not appropriateness — a perfect similarity match can still be a boundary violation. Default is FAIL-CLOSED: if in-context authorization is uncertain, the memory may inform behaviour but must not be surfaced. Backed by RBI-Eval (arxiv 2606.06055v1). Triggers on surfacing recalled sensitive memory into a response.

2026-07-19

Ver todos los de este repositorio

name	env-setup
description	Environment configuration and secrets management. Use when setting up .env files, managing secrets, or configuring environments.
version	1.0.0
format	"2025-10-02T00:00:00.000Z"
triggers	["setting up environment variables"]
updated	"2026-04-25T00:00:00.000Z"
status	ACTIVE

Environment Configuration

Non-Negotiable Rules

Rule	Why
NEVER commit .env to git	Secrets persist in history forever
NEVER log secret values	Logs stored in plain text, forwarded
NEVER hardcode secrets	Source code is widely shared
ALWAYS use .env.example	Documents vars without exposing values
ALWAYS add .env* to .gitignore FIRST	Prevents accidental commit
ALWAYS validate config at startup	Fail fast, not hours into production

.gitignore (add before creating .env)

.env
.env.*
!.env.example
*.pem
*.key
credentials.json

Naming Conventions

UPPER_SNAKE_CASE: DATABASE_URL, JWT_SECRET
Prefix by service: DB_, REDIS_, AWS_
Booleans: ENABLE_CACHE=true (not 1/yes)
Feature flags: FEATURE_*

Key Patterns

No defaults for secrets — force explicit configuration
Validate at startup with Zod/Joi/Pydantic, not at first use
Unique secrets per environment — one leak shouldn't compromise all
Rotate leaked secrets immediately — check git history, audit access logs
Process env always wins — CI/CD overrides file-based config

env-setup

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

Environment Configuration

Non-Negotiable Rules

.gitignore (add before creating .env)

Naming Conventions

Key Patterns

Más de este repositorio

Environment Configuration

Non-Negotiable Rules

.gitignore (add before creating .env)

Naming Conventions

Key Patterns