Explore skills
Showing 14701–14730 of 19740 skills
Review the portfolio across existing engagement records. Use for status across customers; requires accessible permitted records and does not create missing client histories.
suboss87/FDEOps
Stars: 818Claude CodeCodexTurn meeting notes or a transcript into sourced decisions, changes and next actions. Use after a customer conversation; review consequential record updates before saving.
suboss87/FDEOps
Stars: 818Claude CodeCodexInvestigate 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.
suboss87/FDEOps
Stars: 818Claude CodeCodexPrepare a customer demo or executive walkthrough around an evidenced outcome. Use before show-and-tell to rehearse the journey and prepare a fallback.
suboss87/FDEOps
Stars: 818Claude CodeCodexTrace a customer workflow and identify the problem, baseline and evidence gaps. Use for discovery or an unclear customer brief, before choosing a solution.
suboss87/FDEOps
Stars: 818Claude CodeCodexPlan how to earn customer trust and appropriate access. Use when credibility, permissions or AI policy constrain the engagement.
suboss87/FDEOps
Stars: 818Claude CodeCodexEvaluate an AI workflow against representative cases and its permitted actions. Use for model, retrieval or agent evaluation; tests do not grant release authority.
suboss87/FDEOps
Stars: 818Claude CodeCodexKeeps 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 (or npx --yes fdeops). Never ask them to type commands. Not for ordinary code edits in an unbound repo.
suboss87/FDEOps
Stars: 818Claude CodeCodexAssess a field lesson for reuse or product feedback without exposing customer context. Use for recurring deployment lessons; distinguish a hypothesis from a validated pattern.
suboss87/FDEOps
Stars: 818Claude CodeCodexTransfer operation of a customer deployment with ownership, evidence and a tested support path. Use for handoff or an engineer rotation, not merely code delivery.
suboss87/FDEOps
Stars: 818Claude CodeCodexFetch 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.
suboss87/FDEOps
Stars: 818Claude CodeCodexBuild or change a customer-system integration with explicit data mapping, permissions, retries and reconciliation. Use for connectors, imports, write-back and upstream APIs.
suboss87/FDEOps
Stars: 818Claude CodeCodexCompare feasible approaches to a customer problem and recommend a path with costs, constraints and evidence. Use for an architecture or delivery decision, not implementation.
suboss87/FDEOps
Stars: 818Claude CodeCodexSequence an understood outcome into verifiable delivery slices with dependencies, ownership and acceptance checks. Use for delivery planning, estimation or migration strategy.
suboss87/FDEOps
Stars: 818Claude CodeCodexRun 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.
suboss87/FDEOps
Stars: 818Claude CodeCodexChoose up to three immediate priorities from competing initiatives. Use when everything is urgent and the customer needs a defensible order with explicit deferrals.
suboss87/FDEOps
Stars: 818Claude CodeCodexExercise the delivered customer journey using real runtime or browser evidence. Use for functional acceptance testing after implementation, including failure paths.
suboss87/FDEOps
Stars: 818Claude CodeCodexPrepare a sponsor update separating promised outcomes, measured results and customer acceptance. Use for progress readouts or defending a delivery claim.
suboss87/FDEOps
Stars: 818Claude CodeCodexStress-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.
suboss87/FDEOps
Stars: 818Claude CodeCodexTriage an outage, loss of stakeholder trust or a failing engagement direction. Use for urgent recovery; distinguish diagnosis from authorized production mitigation.
suboss87/FDEOps
Stars: 818Claude CodeCodexReview a proposed customer code change against its intended outcome and operational risks. Use for a diff or PR review; report evidence and actionable findings.
suboss87/FDEOps
Stars: 818Claude CodeCodexPrepare 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.
suboss87/FDEOps
Stars: 818Claude CodeCodexWrite 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.
suboss87/FDEOps
Stars: 818Claude CodeCodexAssess a new customer request against agreed scope, trade-offs and ownership. Use when an engagement expands or a custom feature needs a commitment decision.
suboss87/FDEOps
Stars: 818Claude CodeCodexCompare competing customer use cases by value, feasibility and evidence. Use when several problems compete for delivery capacity.
suboss87/FDEOps
Stars: 818Claude CodeCodexPrepare or execute an authorized controlled release with verified checks, recovery and an operating owner. Use when a customer increment is ready for deployment.
suboss87/FDEOps
Stars: 818Claude CodeCodexSwitch between existing customer engagements and triage competing needs. Use when context switching causes confusion; requires engagement records and preserves one client per write.
suboss87/FDEOps
Stars: 818Claude CodeCodexChallenge a proposed solution by identifying and testing consequential assumptions. Use when the brief feels too certain or discovery reveals contradictions.
suboss87/FDEOps
Stars: 818Claude CodeCodexAssess the impact of a proposed change on dependencies and shared infrastructure. Use before touching unfamiliar or consequential systems.
suboss87/FDEOps
Stars: 818Claude CodeCodexMap stakeholders, decision rights, influence and blockers from supplied evidence. Use when ownership is unclear or the stakeholder landscape changes.
suboss87/FDEOps
Stars: 818Claude CodeCodex