All authors
Claude Skills by suboss87
github.com/suboss8736 skills3 installs89 views
- FdeKeeps 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.Votes: 0GitHub stars: 950
- AuditAudit an inherited engagement or implementation against its evidence. Use when taking over work or joining mid-project; distinguish verified facts from inherited claims.Votes: 0GitHub stars: 950
- Board MemoDraft a board or executive summary of an engagement using outcomes, risks and investment decisions. Use when the sponsor needs to brief senior leadership.Votes: 0GitHub stars: 950
- BriefClarify a new customer brief, desired outcome, constraints and evidence gaps. Use for kickoff or a first meeting; do not repeat discovery already supplied.Votes: 0GitHub stars: 950
- BuildImplement a scoped software change for a customer and verify its behavior. Use for delivery work with an understood outcome, not incident response.Votes: 0GitHub stars: 950
- Business CaseDevelop a business case for an initiative using costs, benefits, risks and evidence. Use when a sponsor needs budget or timeline justification.Votes: 0GitHub stars: 950
- ConnectConfigure 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.Votes: 0GitHub stars: 950
- DashboardReview the portfolio across existing engagement records. Use for status across customers; requires accessible permitted records and does not create missing client histories.Votes: 0GitHub stars: 950
- DebriefTurn meeting notes or a transcript into sourced decisions, changes and next actions. Use after a customer conversation; review consequential record updates before saving.Votes: 0GitHub stars: 950
- DebugInvestigate 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.Votes: 0GitHub stars: 950
- Demo PrepPrepare a customer demo or executive walkthrough around an evidenced outcome. Use before show-and-tell to rehearse the journey and prepare a fallback.Votes: 0GitHub stars: 950
- DiscoverTrace a customer workflow and identify the problem, baseline and evidence gaps. Use for discovery or an unclear customer brief, before choosing a solution.Votes: 0GitHub stars: 950
- Earn TrustPlan how to earn customer trust and appropriate access. Use when credibility, permissions or AI policy constrain the engagement.Votes: 0GitHub stars: 950
- EvaluateEvaluate an AI workflow against representative cases and its permitted actions. Use for model, retrieval or agent evaluation; tests do not grant release authority.Votes: 0GitHub stars: 950
- FeedbackAssess a field lesson for reuse or product feedback without exposing customer context. Use for recurring deployment lessons; distinguish a hypothesis from a validated pattern.Votes: 0GitHub stars: 950
- HandoffTransfer operation of a customer deployment with ownership, evidence and a tested support path. Use for handoff or an engineer rotation, not merely code delivery.Votes: 0GitHub stars: 950
- IngestFetch 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.Votes: 0GitHub stars: 950
- IntegrateBuild or change a customer-system integration with explicit data mapping, permissions, retries and reconciliation. Use for connectors, imports, write-back and upstream APIs.Votes: 0GitHub stars: 950
- OptionsCompare feasible approaches to a customer problem and recommend a path with costs, constraints and evidence. Use for an architecture or delivery decision, not implementation.Votes: 0GitHub stars: 950
- PlanSequence an understood outcome into verifiable delivery slices with dependencies, ownership and acceptance checks. Use for delivery planning, estimation or migration strategy.Votes: 0GitHub stars: 950
- PocRun 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.Votes: 0GitHub stars: 950
- PrioritizeChoose up to three immediate priorities from competing initiatives. Use when everything is urgent and the customer needs a defensible order with explicit deferrals.Votes: 0GitHub stars: 950
- QaExercise the delivered customer journey using real runtime or browser evidence. Use for functional acceptance testing after implementation, including failure paths.Votes: 0GitHub stars: 950
- ReadoutPrepare a sponsor update separating promised outcomes, measured results and customer acceptance. Use for progress readouts or defending a delivery claim.Votes: 0GitHub stars: 950
- Red TeamStress-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.Votes: 0GitHub stars: 950
- RescueTriage an outage, loss of stakeholder trust or a failing engagement direction. Use for urgent recovery; distinguish diagnosis from authorized production mitigation.Votes: 0GitHub stars: 950
- ReviewReview a proposed customer code change against its intended outcome and operational risks. Use for a diff or PR review; report evidence and actionable findings.Votes: 0GitHub stars: 950
- RollbackPrepare 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.Votes: 0GitHub stars: 950
- RunbookWrite 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.Votes: 0GitHub stars: 950
- ScopeAssess a new customer request against agreed scope, trade-offs and ownership. Use when an engagement expands or a custom feature needs a commitment decision.Votes: 0GitHub stars: 950
- Score Use CasesCompare competing customer use cases by value, feasibility and evidence. Use when several problems compete for delivery capacity.Votes: 0GitHub stars: 950
- ShipPrepare or execute an authorized controlled release with verified checks, recovery and an operating owner. Use when a customer increment is ready for deployment.Votes: 0GitHub stars: 950
- Switch ClientsSwitch between existing customer engagements and triage competing needs. Use when context switching causes confusion; requires engagement records and preserves one client per write.Votes: 0GitHub stars: 950
- Test AssumptionsChallenge a proposed solution by identifying and testing consequential assumptions. Use when the brief feels too certain or discovery reveals contradictions.Votes: 0GitHub stars: 950
- What BreaksAssess the impact of a proposed change on dependencies and shared infrastructure. Use before touching unfamiliar or consequential systems.Votes: 0GitHub stars: 950
- Who DecidesMap stakeholders, decision rights, influence and blockers from supplied evidence. Use when ownership is unclear or the stakeholder landscape changes.Votes: 0GitHub stars: 950