image-to-mission

Extract creative intent from images into executable build specs. Activates on images + build intent, "image to mission", "i2m", or capturing visual energy in code/design.

Ir para a instalação

Repositório: Tibsfox/gsd-skill-creator
Última atividade na origem: 10 de junho de 2026 às 22:32
Idioma detectado do SKILL.md: inglês
Estrelas: 69
Forks: 9

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/Tibsfox/gsd-skill-creator --skill image-to-mission

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

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 todas deste repositório

name	image-to-mission
description	Extract creative intent from images into executable build specs. Activates on images + build intent, "image to mission", "i2m", or capturing visual energy in code/design.
domain	creative-translation
context	fork
activation	domain
dependencies	{"optional":["vision-to-mission"]}
format	"2025-10-02T00:00:00.000Z"
version	1.0.0
status	ACTIVE
updated	"2026-04-15T00:00:00.000Z"
triggers	["user provides an image and wants it turned into a build spec or mission","\"image to mission\" or \"i2m\" is requested","capturing visual or design energy from an image into code or a mission package"]

Image to Mission

Takes one or more images plus optional creator context and produces:

Structured 4-layer visual analysis (literal, spatial, relational, mood)
Extracted technical parameters (color, geometry, material, feel)
Executable build instructions with philosophy annotations
Self-contained transmission package for cross-context handoff

When to Activate

Activate when the user provides images AND expresses intent to:

Build, create, or make something based on the images
Translate visual reference into code, design, or specifications
Capture the "feel" or "energy" of images in another medium
Create a mission package from visual reference
Direct keywords: "image to mission", "i2m"
Target medium: "translate this to [canvas/react/three.js/SVG/CSS]"

DO NOT activate when the user:

Simply asks "what's in this image?" (use standard image analysis)
Wants image editing or manipulation
Needs OCR or text extraction from images
Is asking about image file formats or metadata
Asks to describe colors or content without build intent

Observation Protocol

Before building anything, enter observation mode:

Phase 1: Observe (mandatory — do not skip)

Process each image through four layers:

Literal: Inventory all visible objects, materials, colors
Spatial: Map relationships, arrangements, density
Relational: Find patterns across images, note changes vs. constants
Mood: Quantify atmosphere (energy, intimacy, order, handmade, ceremony)

Phase 2: Listen (if creator provides context)

Structure context into: process, intent, constraints, accidents, multipurpose. Extract the process insight — the key understanding about HOW it was made.

Phase 3: Connect

Synthesize observations + context into unified understanding. Find what neither source reveals alone.

Phase 4: Extract

Convert understanding to numerical parameters:

Colors (palette, temperature, contrast, relationships)
Geometry (shape, arrangement, symmetry, constants)
Materials (surfaces, light interaction, blend modes)
Feel (energy, intimacy, order, handmade, ceremony — all 0-1)

Phase 5: Build

Translate parameters to target medium. Generate step-by-step instructions with philosophy notes.

Format	When	Content
Direct build	Simple, single-medium output	Code/SVG + philosophy notes
Build spec	Medium complexity	Step-by-step instructions
Mission package	Complex, multi-component	Full vision_to_mission handoff
Transmission package	Cross-context work	JSON/Markdown bundle

image-to-mission

Opções de instalação

Revise os arquivos de origem

Image to Mission

When to Activate

Observation Protocol

Phase 1: Observe (mandatory — do not skip)

Phase 2: Listen (if creator provides context)

Phase 3: Connect

Phase 4: Extract

Phase 5: Build

Phase 6: Document

Image to Mission

When to Activate

Observation Protocol

Phase 1: Observe (mandatory — do not skip)

Phase 2: Listen (if creator provides context)

Phase 3: Connect

Phase 4: Extract

Phase 5: Build

Phase 6: Document

Output Formats

Implementation

Key Principles

Safety

image-to-mission

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Image to Mission

When to Activate

Observation Protocol

Phase 1: Observe (mandatory — do not skip)

Phase 2: Listen (if creator provides context)

Phase 3: Connect

Phase 4: Extract

Phase 5: Build

Phase 6: Document

Mais deste repositório

Image to Mission

When to Activate

Observation Protocol

Phase 1: Observe (mandatory — do not skip)

Phase 2: Listen (if creator provides context)

Phase 3: Connect

Phase 4: Extract

Phase 5: Build

Phase 6: Document

Output Formats

Implementation

Key Principles

Safety