add-context

Classify user content as transcript, doc, note, or chat and route it to the matching ctx writer.

4|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/simonconway1979/os-intelligence --skill add-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-context
Source: https://github.com/simonconway1979/os-intelligence/tree/main/.claude/skills/add-context
Command: npx skills add https://github.com/simonconway1979/os-intelligence --skill add-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OS-Intelligence needs new meeting notes, documents, personal notes, or chat threads added to the active project, but users shouldn’t have to manually figure out which context “writer” pathway to use or how to route inputs.

Core Features & Use Cases

  • One entry point for all context types: routes your input to the correct existing /ctx-* writer by classifying it as transcript, doc, note, or chat.
  • Flexible input handling: supports adding context from a file path or from pasted content, with a short header read (first 60 lines) for classification.
  • Guardrails and routing confirmation: validates active project resolution, handles edge cases like empty/binary/malformed type overrides, and logs triage outcomes to logs/triage.log.

Quick Start

Run /add-context with the file path to your meeting transcript, document, note, or chat export, and it will classify and route it to the matching ctx writer.

Frequently Asked Questions about add-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically route meeting transcripts and project documents into the correct context?

Triage entry points classify inputs as transcripts, docs, notes, or chat by reading the first 60 lines, then route them to the matching context writer for project ingestion.

What is the best way to add chat threads and personal notes to an active project without manual routing?

A single entry point classifies input content and automatically invokes the corresponding context writer, resolving the active project from session files to ingest chat threads and personal notes.

Can I override the automatic classification when ingesting documents?

Yes, you can bypass automatic classification by providing an optional type override flag, forcing the triage mechanism to route the content to a specified context writer.

Does the context triage process work with pasted content or only file paths?

Context triage supports both pasted content and file paths, reading the first 60 lines of the provided input to classify and route it to the appropriate writer.

How are triage results and routing outcomes logged for telemetry?

Triage results are logged for telemetry by recording classification decisions, edge case handling, and routing outcomes to a dedicated logs file for tracking document ingestion.

What happens if the active project cannot be resolved during document ingestion?

If the active project cannot be resolved from session files, guardrails validate project resolution and halt the routing process to prevent misdirected document ingestion.