Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
 
← Back to list

FDE Engagement Fieldbook

A forward-deployed-engineer fieldbook that routes client work through lifecycle phases and turns every session into durable `.fde/` engagement memory.

AutomationAdvanced★ 236⑂ 30AI score 9/10Last updated: Aug 13, 2026

What it does

  • Triggers on @fde or plain language ("debrief these notes", "prep me for tomorrow's sponsor meeting", "when did we agree to drop that?") and routes to one of six domains: embed & trust, discover, plan, build, ship, operate & close.
  • The agent — not you — runs the local fde CLI (resume, scan, debrief, ingest, prep, receipts, status, dashboard, doctor, redact) and reports back in plain language for confirm/reject.
  • Every phase ends with a written artifact in .fde/ (context.md, decisions.md, risks.md, stakeholders.md, delivery.md), plus an end-of-session digest so the next session resumes mid-thought.
  • Hard guardrails: evidence tags on every claim, unknown - ask: instead of invented people or numbers, no transcript dumps into the product repo, and redaction of <private> data.
  • Domain overlays (AI/ML, healthcare, fintech, gov, artifacts) activate automatically on signal.

Who it's for

  • Forward deployed engineers, solutions architects, and technical consultants working inside customer environments.
  • Anyone juggling multiple client engagements and losing context between them.
  • Teams that must defend decisions and scope to skeptical sponsors with traceable receipts.

Examples

  1. Paste raw meeting notes → the agent runs fde debrief --smart, proposes decision/risk/delivery/contact routing, and only applies it after you confirm.
  2. Scope dispute → fde receipts <term> returns dated evidence; no hit is reported as a gap, not as proof.
  3. Pre-deploy check → intent-vs-diff (KEEP/JUSTIFY/SPLIT/DROP) and a pre-blast challenge are run and logged before anything irreversible ships.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/suboss87/FDEOps/HEAD/skills/fde/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the skills/fde folder from the GitHub repo suboss87/FDEOps into my ~/.claude/skills/fde/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/suboss87/FDEOps.git && mkdir -p ~/.claude/skills && cp -r FDEOps/skills/fde ~/.claude/skills/fde

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal.
  2. Clone the repository: git clone https://github.com/suboss87/FDEOps.git
  3. Install the skill: mkdir -p ~/.claude/skills && cp -r FDEOps/skills/fde ~/.claude/skills/fde
  4. Follow the repo README to install the local fde CLI (and optional session hooks); it typically lives at ~/.claude/fdeops/ — verify with node ~/.claude/fdeops/fde.js resume.
  5. Restart Claude Code and type @fde in chat.
  6. If it reports "NO ENGAGEMENT", just name the client; the agent runs fde resume --init <name> for you.
  7. From then on, speak naturally — never type fde commands yourself.
View source on GitHub ↗License: MIT