ingest
/ingest
Create or update a single OKF concept file from raw input. Use when the user wants to document a specific table, metric, API, service, or concept in the knowledge base — even if they say "add this to the okf", "documenta essa tabela", "cria um conceito pra isso", "adiciona no knowledge base", "register this API", or pastes a schema/description and says to save it. If no OKF files exist yet, suggest /mega-brain:init first.
- Author
- guhcostan ↗
- Repository
- claude-mega-brain ↗
- Licence
- MIT
- Last repository change
- 22.07.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 22.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Create or update a single OKF concept file from raw input. Use when the user wants to document a specific table, metric, API, service, or concept in the knowledge base — even if they say "add this to the okf", "documenta essa tabela", "cria um conceito pra isso", "adiciona no knowledge base", "register this API", or pastes a schema/description and says to save it. If no OKF files exist yet, suggest /mega-brain:init first.
Triggers from the description
Original author description
Create or update a single OKF concept file from raw input. Use when the user wants to document a specific table, metric, API, service, or concept in the knowledge base — even if they say "add this to the okf", "documenta essa tabela", "cria um conceito pra isso", "adiciona no knowledge base", "register this API", or pastes a schema/description and says to save it. If no OKF files exist yet, suggest /mega-brain:init first.
How it works
- Before writing
- Output format
- Common types
- Process
- Updating an existing entry
SKILL.md preview
--- name: ingest description: Create or update a single OKF concept file from raw input. Use when the user wants to document a specific table, metric, API, service, or concept in the knowledge base — even if they say "add this to the okf", "documenta essa tabela", "cria um conceito pra isso", "adiciona no knowledge base", "register this API", or pastes a schema/description and says to save it. If no OKF files exist yet, suggest /mega-brain:init first. --- # ingest — OKF Concept Writer Turns raw input (schema dump, API doc, user description, table definition) into one OKF-formatted `.md` file committed to the knowledge base. ## Before writing Look for existing OKF files: any `.md` with `type:` frontmatter, or `index.md` / `log.md` in the project. If none exist, stop and tell the user to run `/mega-brain:init` first. If `.mega-brain.json` defines `dir`, save new concepts under that directory. Otherwise, choose a sensible location (`docs/`, project root, etc.) consistent with existing OKF files. Check if a concept with the same name already exists. If so, ask whether to update it or create a new one. ## Output format One `.md` file per concept. Only `type` is required: ```markdown --- type: <concept type> title: <display name> description: <one sentence, plain language, no jargon> resource: <URL to the actual resource, if any> tags: [<tag1>, <tag2>] timestamp: <ISO 8601 date> --- <body: exact schema, formula, join patterns, examples, caveats> ``` ## Common types | Type | Use for | |------|---------| | `BigQuery Table` | BQ tables with schema | | `BigQuery Dataset` | BQ datasets | | `Table` | Non-BQ database tables | | `Metric` | KPI or business metric with formula | | `API` | REST/GraphQL endpoints | | `Runbook` | Operational procedures | | `Concept` | Business or domain terminology | | `Service` | Internal microservices | | `Pipeline` | ETL or data pipelines | Types are freeform — add your own. ## Process 1. Read the source material 2. Identify the concept type and canonical name 3. Write `description`: one sentence, plain language 4. Add `resource` URL if there's a live resource (BQ console URL, API endpoint, dashboard) 5. Write the body with exact values — preserve field names, types, and formulas as-is; do not generalize 6. Link to related concepts with `[Name](relative-path.md)` — this builds the knowledge graph 7. Save next to related OKF files (e.g. `docs/tables/<slug>.md` or `<config-dir>/tables/<slug>.md`) 8. Add one line to `index.md`: `- [Title](path) — description` 9. Append to `log.md`: `<date> — added <title>` ## Updating an existing entry - Update `timestamp` - Preserve existing wikilinks unless explicitly removing them - Keep `description` to one sentence — push additional detail into the body
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · guhcostan/claude-mega-brain | 100 | MIT |
| abatyuk/okf | 100 | MIT |
| kriscard/Skills | 100 | MIT |
| wellwelwel/blue-spec | 100 | Apache-2.0 |
| zimoliao/scholaraio | 100 | MIT |
| erayozenn/BigHead-2ndBrain | 100 | MIT |
| zanderadam/engy | 100 | MIT |
| ARCASSystems/FounderOS | 100 | MIT |
| coreyhaines31/makerskills | 100 | MIT |
Database snapshot: 13.11.2026 · package version 3297f6170dfa (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100init
Initialize OKF knowledge base files in the current project. Use when the user wants to start documenting their project for claude-mega-brain, or when the user says "init mega brain", "setup the knowledge base", "cria o okf", "inicializa o mega brain", "quero usar o mega brain",… - 100migrate
Scan the project and migrate existing documentation into OKF format. Use when the user wants to populate the knowledge base from existing docs, README, schemas, API specs, runbooks, or any structured project knowledge. Trigger on "migrate to okf", "populate the knowledge base",… - 95okf-authoring
Author Open Knowledge Format (OKF) bundles — knowledge represented as a directory of markdown files with YAML frontmatter. Use when asked to create, write, generate, enrich, or validate an OKF bundle or OKF concept docs; to turn a data source (Glue database, API, database,… - 95okf-skill
Use the Open Knowledge Format (OKF) when storing, retrieving, or documenting knowledge. Produces and reads OKF bundles, portable markdown with YAML frontmatter. Use when the user asks to "document this in OKF", "create an OKF bundle", "read the knowledge base", or when working… - 90okf
Use this skill for Open Knowledge Format (OKF) rules, compliance, frontmatter requirements, and validation of any OKF bundle. Triggers on okf, Open Knowledge Format, OKF compliance, OKF frontmatter, validate OKF, OKF rules, and pure format questions. This is the pure format… - 100okf-maintain-knowledge
OKF — Author, maintain, and consume Open Knowledge Format (OKF) knowledge bundles. Use when capturing project knowledge (services, APIs, schemas, decisions) into an OKF bundle, when updating one after code or docs change, or when a repository's OKF bundle should inform the task.…