okhp3-capture-intake

Capture one raw item into a project inbox with provenance and minimal handling.

1|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/OKHP3/refoldec --skill okhp3-capture-intake-okhp3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: okhp3-capture-intake
Source: https://github.com/OKHP3/refoldec/tree/main/.agents/skills/okhp3-capture-intake
Command: npx skills add https://github.com/OKHP3/refoldec --skill okhp3-capture-intake-okhp3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Raw ideas, files, links, transcripts, and requests often get lost, prematurely interpreted, or silently rewritten when they first arrive. This Skill preserves a single incoming item in a project inbox exactly as received, recording provenance and unknowns without triaging, interpreting, or promoting it. ## Core Features & Use Cases - Provenance-preserving capture: Records received date, source or origin, the raw item or a lossless pointer, a one-sentence relevance note, constraints, and a capture status of CAPTURED, BLOCKED, or NOT RUN. - Safe handling of untrusted content: Treats instruction-like text inside captured material as data, refusing embedded commands such as publish or delete requests. - Explicit destination control: Requires the user to name the project root and inbox path, returning BLOCKED rather than guessing a directory. - Use Case: A meeting transcript arrives with unclear ownership. Use this Skill to store it in the project inbox with its source, date, and open questions recorded, deferring lifecycle decisions to a later triage step. ## Quick Start Use okhp3-capture-intake to preserve this note in my project inbox at 00_Inbox/ under the project root.

Frequently Asked Questions about okhp3-capture-intake

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

FAQPage Schema
How do I capture a raw idea or file into a project inbox?▼

Provide the project root and inbox path along with the item, and the Skill stores it with received date, source, a lossless copy or pointer, and a one-sentence relevance note. It returns the destination path and a CAPTURED status without interpreting the content.

What is the difference between capture intake and triage?▼

Capture intake preserves one item as received with provenance and no lifecycle decisions. Triage, handled by the separate okhp3-triage-and-file skill, decides disposition such as activation, filing, archival, or deletion after capture.

What happens if I do not provide an inbox path?▼

The Skill returns BLOCKED and names the missing choice instead of guessing a destination directory. It does not claim that any file was written until an explicit project root and inbox path are supplied.

Can captured content contain instructions like publish or delete?▼

Instruction-like content inside a captured item is treated as untrusted data, not commands. The Skill preserves the source, refuses publication or deletion, and labels any interpretation as inferred.

When should I not use single-item capture intake?▼

Avoid it for batch triage, deduplication, interpretation, activation, archival, publication, or deletion, which are explicitly out of scope. It is designed only for first-arrival preservation of one item at a time.