# Ingest

Fetch requested source material and prepare sourced engagement updates.

- Repository: https://github.com/suboss87/FDEOps (946 stars)
- Category: Writing
- License: MIT
- Last updated: 2026-10-21
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add suboss87/FDEOps --skill ingest -g -a claude-code -y`
Codex: `npx skills add suboss87/FDEOps --skill ingest -g -a codex -y`
Cursor: `npx skills add suboss87/FDEOps --skill ingest -g -a cursor -y`
Gemini CLI: `npx skills add suboss87/FDEOps --skill ingest -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add suboss87/FDEOps`

## Description

Fetch requested source material and prepare sourced engagement updates. Use to catch up from external notes or messages; applying updates requires a bound record and confirmation.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# ingest

<!-- Generated by bin/generate-skills.js; edit the canonical references and catalog. -->

## Purpose

Sourced proposed updates, with confirmed record application when bound.

Before investigating or acting:
1. Read [the task context contract](references/task-context.md).
2. Read [the method](references/ingest.md).

Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required.

## Principles

- Use permitted supplied material or available source tools to prepare a sourced proposal without requiring an engagement record. CLI staging and reconciliation use a bound engagement; applying updates requires the bound record and confirmation. Do not claim an unbound draft has been saved to engagement memory.
- If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered.
- The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance.
- Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.