Updated 1w ago
by suboss87
FDEOps
Forward deployed engineering skills for AI coding agents.
965 GitHub stars (965)
+17 in 20 days
| Period | New stars |
|---|---|
| Sep 27 | 0 |
| Sep 28 | 0 |
| Sep 29 | +1 |
| Sep 30 | 0 |
| Oct 1 | 0 |
| Oct 2 | −3 |
| Oct 3 | +3 |
| Oct 4 | 0 |
| Oct 5 | +1 |
| Oct 6 | 0 |
| Oct 7 | +3 |
| Oct 8 | +1 |
| Oct 9 | +2 |
| Oct 10 | +2 |
| Oct 11 | 0 |
| Oct 12 | +1 |
| Oct 13 | +1 |
| Oct 14 | +1 |
| Oct 15 | +1 |
| Oct 16 | +3 |
- 30 skills (30 skills found in its SKILL.md files)
- 108 forks (108 forks)
- 1w ago last update (Last updated 1w ago)
Install
Skills CLI
npx skills add suboss87/FDEOps
Asks which skills and agents to install. Just one: npx skills add suboss87/FDEOps --skill audit — add -g for every project.
Claude Code
git clone https://github.com/suboss87/FDEOpscp -r "FDEOps/skills/audit" ~/.claude/skills/
Copies the audit skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add suboss87/FDEOps
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md — showing the first 30 of 36 files.
-
audit
Audit an inherited engagement or implementation against its evidence. Use when taking over work or joining mid-project; distinguish verified facts from inherited claims.
skills/audit/SKILL.md on GitHub (opens in a new tab) -
board-memo
Draft a board or executive summary of an engagement using outcomes, risks and investment decisions. Use when the sponsor needs to brief senior leadership.
skills/board-memo/SKILL.md on GitHub (opens in a new tab) -
brief
Clarify a new customer brief, desired outcome, constraints and evidence gaps. Use for kickoff or a first meeting; do not repeat discovery already supplied.
skills/brief/SKILL.md on GitHub (opens in a new tab) -
build
Implement a scoped software change for a customer and verify its behavior. Use for delivery work with an understood outcome, not incident response.
skills/build/SKILL.md on GitHub (opens in a new tab) -
business-case
Develop a business case for an initiative using costs, benefits, risks and evidence. Use when a sponsor needs budget or timeline justification.
skills/business-case/SKILL.md on GitHub (opens in a new tab) -
connect
Configure or diagnose access to a requested source using available host tools. Use for source MCP setup; source configuration needs no engagement record and credentials stay with the host.
skills/connect/SKILL.md on GitHub (opens in a new tab) -
dashboard
Review the portfolio across existing engagement records. Use for status across customers; requires accessible permitted records and does not create missing client histories.
skills/dashboard/SKILL.md on GitHub (opens in a new tab) -
debrief
Turn meeting notes or a transcript into sourced decisions, changes and next actions. Use after a customer conversation; review consequential record updates before saving.
skills/debrief/SKILL.md on GitHub (opens in a new tab) -
debug
Investigate a failure, regression or incorrect result in an integration or application, even before it can be reproduced. Use for diagnosis and repair; follow incident authority for live mitigation.
skills/debug/SKILL.md on GitHub (opens in a new tab) -
demo-prep
Prepare a customer demo or executive walkthrough around an evidenced outcome. Use before show-and-tell to rehearse the journey and prepare a fallback.
skills/demo-prep/SKILL.md on GitHub (opens in a new tab) -
discover
Trace a customer workflow and identify the problem, baseline and evidence gaps. Use for discovery or an unclear customer brief, before choosing a solution.
skills/discover/SKILL.md on GitHub (opens in a new tab) -
earn-trust
Plan how to earn customer trust and appropriate access. Use when credibility, permissions or AI policy constrain the engagement.
skills/earn-trust/SKILL.md on GitHub (opens in a new tab) -
evaluate
Evaluate an AI workflow against representative cases and its permitted actions. Use for model, retrieval or agent evaluation; tests do not grant release authority.
skills/evaluate/SKILL.md on GitHub (opens in a new tab) -
fde
Keeps the engagement record for client work. Use when they name a client or stakeholder. Use when they debrief a meeting or paste notes. Use when they ask what was agreed. Use when they run a POC, change the client's codebase, prove it on their staging, go live, or need evals before a model acts. Use when they prep a readout, when trust shifts, or they say @fde. Route and run the local fde CLI (o…
skills/fde/SKILL.md on GitHub (opens in a new tab) -
feedback
Assess a field lesson for reuse or product feedback without exposing customer context. Use for recurring deployment lessons; distinguish a hypothesis from a validated pattern.
skills/feedback/SKILL.md on GitHub (opens in a new tab) -
handoff
Transfer operation of a customer deployment with ownership, evidence and a tested support path. Use for handoff or an engineer rotation, not merely code delivery.
skills/handoff/SKILL.md on GitHub (opens in a new tab) -
ingest
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.
skills/ingest/SKILL.md on GitHub (opens in a new tab) -
integrate
Build or change a customer-system integration with explicit data mapping, permissions, retries and reconciliation. Use for connectors, imports, write-back and upstream APIs.
skills/integrate/SKILL.md on GitHub (opens in a new tab) -
options
Compare feasible approaches to a customer problem and recommend a path with costs, constraints and evidence. Use for an architecture or delivery decision, not implementation.
skills/options/SKILL.md on GitHub (opens in a new tab) -
plan
Sequence an understood outcome into verifiable delivery slices with dependencies, ownership and acceptance checks. Use for delivery planning, estimation or migration strategy.
skills/plan/SKILL.md on GitHub (opens in a new tab) -
poc
Run a bounded customer proof of concept to test a consequential uncertainty. Use for a spike or pilot with a question and decision deadline, not a full rollout.
skills/poc/SKILL.md on GitHub (opens in a new tab) -
prioritize
Choose up to three immediate priorities from competing initiatives. Use when everything is urgent and the customer needs a defensible order with explicit deferrals.
skills/prioritize/SKILL.md on GitHub (opens in a new tab) -
qa
Exercise the delivered customer journey using real runtime or browser evidence. Use for functional acceptance testing after implementation, including failure paths.
skills/qa/SKILL.md on GitHub (opens in a new tab) -
readout
Prepare a sponsor update separating promised outcomes, measured results and customer acceptance. Use for progress readouts or defending a delivery claim.
skills/readout/SKILL.md on GitHub (opens in a new tab) -
red-team
Stress-test a plan, brief or delivery claim against evidence and plausible failure modes. Use when the user asks for a red team or preparation for a consequential decision.
skills/red-team/SKILL.md on GitHub (opens in a new tab) -
rescue
Triage an outage, loss of stakeholder trust or a failing engagement direction. Use for urgent recovery; distinguish diagnosis from authorized production mitigation.
skills/rescue/SKILL.md on GitHub (opens in a new tab) -
review
Review a proposed customer code change against its intended outcome and operational risks. Use for a diff or PR review; report evidence and actionable findings.
skills/review/SKILL.md on GitHub (opens in a new tab) -
rollback
Prepare and rehearse a recovery path for an intended release. Use when rollback is assumed, untested or previously failed; follow the environment authority for any drill.
skills/rollback/SKILL.md on GitHub (opens in a new tab) -
runbook
Write an operating runbook from the delivered system and verified procedures. Use when the customer team or a successor needs to operate without the original engineer.
skills/runbook/SKILL.md on GitHub (opens in a new tab) -
scope
Assess a new customer request against agreed scope, trade-offs and ownership. Use when an engagement expands or a custom feature needs a commitment decision.
skills/scope/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.