record-finding

Estrellas6

Forks0

Actualizado4 de julio de 2026 a las 14:33

Dump a single empirical Finding into the OKF knowledge base after an investigation or debugging session. Fast and non-interactive. Records what you truthfully observed and believed at this moment, with confidence and context, as an immutable dated note under knowledge/findings/. Use after diagnosing a bug, verifying behavior, or discovering something non-trivial worth remembering.

Instalación

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.

Fuente

gsemet

gsemet/okf-schema

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

Más de este repositorio

mismo repositorio

okfkb-gardening

gsemet/okf-schema

Autonomously refresh and consolidate an OKFKB knowledge base in one zero-prompt run: repair graph maintenance issues, reconcile Finding contradictions and supersession, update or promote semantic knowledge, create open investigations and operational/planning documents when justified, detect stale knowledge, and validate using project-prescribed checks. Use only when the user explicitly asks to garden, refresh, consolidate, or maintain an OKFKB knowledge base.

2026-07-136

okfkb

gsemet/okf-schema

Understand, use, and maintain an opinionated OKFKB knowledge base: capture immutable empirical Findings, choose the correct knowledge layer, consolidate converged evidence into Concepts and Structures, preserve contradictions, navigate from stable knowledge to raw evidence, and route recurring maintenance to okfkb-gardening. Use when the user mentions OKFKB, knowledge lifecycle, recording durable findings, consolidating a knowledge base, promoting findings, choosing a KB document type, or maintaining an agent knowledge base.

2026-07-136

okf-schema

gsemet/okf-schema

Validate, lint, and manage OKF (Open Knowledge Format) bundles using the okf-schema CLI and Python API. Use when the user mentions OKF validation, validate a knowledge bundle, check OKF conformance, lint frontmatter, OKF schema validation, bundle integrity, broken links in OKF, or wants to initialize or manage an OKF bundle structure. Also use for okf-schema CLI commands, JSONSchema validation of OKF concepts, or formatting OKF frontmatter.

2026-07-096

consolidate-knowledge-base

gsemet/okf-schema

Interactively review the OKF knowledge base to detect contradictions between Findings, mark contradicted/superseded Findings, propose Experiments to resolve open questions, and propose promotions of converged Findings into stable Concept/Structure/Principle documents. Every mutation is confirmed by a human before it is written. Use periodically or after a batch of recorded Findings.

2026-07-046

name	record-finding
description	Dump a single empirical Finding into the OKF knowledge base after an investigation or debugging session. Fast and non-interactive. Records what you truthfully observed and believed at this moment, with confidence and context, as an immutable dated note under knowledge/findings/. Use after diagnosing a bug, verifying behavior, or discovering something non-trivial worth remembering.

record-finding

Record ONE Finding: a dated, empirical, falsifiable note of what you observed and believed right now. Findings can later be wrong — that is fine. Be truthful about the moment, not about eternal truth.

When to use

You just finished an investigation, debugging session, or verification.
You learned something non-trivial about how the external world (VS Code, Copilot, pricing, logs) behaves.
You want to hand off "what I found and believed" for later consolidation.

Do NOT use this to record standards/conventions (that is a Principle), how an object is composed (Structure), or a stable idea (Concept). Those are promoted deliberately by consolidate-knowledge-base, not dumped.

Procedure

Write exactly one file to knowledge/findings/<slug>.md where <slug> is a short hyphenated summary of the claim.

Use this frontmatter (all listed fields are required):

---
type: Finding
title: Short claim as a title
description: One-sentence summary of the finding.
tags: [relevant, keywords]
timestamp: <ISO-8601 UTC, e.g. 2026-07-02T14:30:00Z>
confidence: low | medium | high
context: >-
  What you believed and the situation at the time — including assumptions
  that may later prove wrong, and the scope you actually tested.
---

In the body, state plainly: what was observed, why it matters, and the caveats / limits of what you verified.
If this finding contradicts or replaces an earlier one, add contradicts: [<finding-id>] or supersedes: [<finding-id>]. Do NOT edit the older finding — the consolidate-knowledge-base skill handles backlinks.
If a run of an Experiment produced this finding, add derived_from: <experiment-id>.

Immutability

Once written, never reword or delete a finding's body. This is enforced by the Findings Are Immutable principle. Corrections happen by writing a NEW finding.

Validate

just knowledge-lint
just knowledge-validate

Both must pass. Do not run consolidate-knowledge-base here — dumping stays fast.