intelligence-investigator

Generate intelligence briefings for the planning dashboard. Use this skill whenever a request file appears in `.planning/console/inbox/pending/` whose `type` field starts with `intelligence.` (refresh_briefing, triage_finding, snapshot_diff, investigate_section, dismiss_finding). The skill reads the per-project KB at `.gsd/intelligence/intelligence.db`, synthesizes a briefing with a causal hypothesis + acknowledged uncertainty + confidence label and ranked moves, then writes the result back to the KB. Always trigger this skill for these request types — do not generate briefings manually.

Ir a la instalación

Repositorio: Tibsfox/gsd-skill-creator
Última actividad en el origen: 6 de junio de 2026 a las 02:15
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 intelligence-investigator

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.

Explorador de archivos

8 archivos

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	intelligence-investigator
description	Generate intelligence briefings for the planning dashboard. Use this skill whenever a request file appears in `.planning/console/inbox/pending/` whose `type` field starts with `intelligence.` (refresh_briefing, triage_finding, snapshot_diff, investigate_section, dismiss_finding). The skill reads the per-project KB at `.gsd/intelligence/intelligence.db`, synthesizes a briefing with a causal hypothesis + acknowledged uncertainty + confidence label and ranked moves, then writes the result back to the KB. Always trigger this skill for these request types — do not generate briefings manually.
version	1.0.0
format	"2025-10-02T00:00:00.000Z"
triggers	["console-inbox request type starts with intelligence.* (refresh_briefing, triage_finding, snapshot_diff, investigate_section, dismiss_finding)"]
updated	"2026-05-02T00:00:00.000Z"
status	ACTIVE
allowed-tools	Read, Glob, Bash(sqlite3:), Bash(git:), Bash(node:), Bash(bun:), Write

Intelligence Investigator

You are responsible for generating planning briefings for the GSD intelligence dashboard. The dashboard surfaces these briefings to the developer at the start of every planning meeting. You run inside a gsd-skill-creator session that is already watching .planning/console/inbox/pending/.

When to activate

Activate when you find a file matching req_*.json in .planning/console/inbox/pending/ whose type field starts with intelligence.:

intelligence.refresh_briefing — full project briefing refresh
intelligence.triage_finding — single finding deep-dive
intelligence.snapshot_diff — explain what changed between two snapshots
intelligence.investigate_section — investigate a specific section of code
intelligence.dismiss_finding — record a dismissal with rationale

Process

1. Parse the request

Read the request file. Extract id, type, project, branch, payload, respond_to, timeout_hint_ms. The request fields define the scope:

payload.since_snapshot — for diff-based requests
payload.scope — list of section/file globs to focus on
payload.conversation_text — recent dashboard discussion (already redacted)
payload.finding_id — for triage requests

2. Load KB context

Run bash scripts/load-kb-context.sh <project> to extract a redacted JSON context summary. The script:

Reads top 30 findings by severity × confidence from the per-project DB
Reads in-flight bundles + decisions
Reads recent meeting record paths (last 3)
Reads recent snapshot diffs (last 3)
Redacts secrets (API keys, tokens, password fragments, SSH keys) before emitting context (S14, D-25-31)
NEVER emits raw source-file content (D-25-30)

The output is structured JSON; parse it before reasoning.

3. Synthesize briefing

Following references/briefing-format.md, write a briefing of 2-3 paragraphs that:

intelligence-investigator

Opciones de instalación

Revisa los archivos de origen

Intelligence Investigator

When to activate

Process

1. Parse the request

2. Load KB context

3. Synthesize briefing

Intelligence Investigator

When to activate

Process

1. Parse the request

2. Load KB context

3. Synthesize briefing

4. Rank suggested moves

5. Self-check the briefing

6. Write briefing to KB

7. Write status to outbox

Failure paths

Critical constraints

Reference files

intelligence-investigator

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

Más de este repositorio

Intelligence Investigator

When to activate

Process

1. Parse the request

2. Load KB context

3. Synthesize briefing

Intelligence Investigator

When to activate

Process

1. Parse the request

2. Load KB context

3. Synthesize briefing

4. Rank suggested moves

5. Self-check the briefing

6. Write briefing to KB

7. Write status to outbox

Failure paths

Critical constraints

Reference files