Explore skills
Showing 21901–21930 of 77079 skills
Prepare 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: 817Claude 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: 817Claude CodeCodexPlan how to earn customer trust and appropriate access. Use when credibility, permissions or AI policy constrain the engagement.
suboss87/FDEOps
Stars: 817Claude 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: 817Claude 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: 817Claude 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: 817Claude 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: 817Claude 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: 817Claude 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: 817Claude 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: 817Claude 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: 817Claude 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: 817Claude CodeCodexExercise the delivered customer journey using real runtime or browser evidence. Use for functional acceptance testing after implementation, including failure paths.
suboss87/FDEOps
Stars: 817Claude CodeCodexPrepare a sponsor update separating promised outcomes, measured results and customer acceptance. Use for progress readouts or defending a delivery claim.
suboss87/FDEOps
Stars: 817Claude 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: 817Claude 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: 817Claude 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: 817Claude 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: 817Claude 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: 817Claude 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: 817Claude CodeCodexCompare competing customer use cases by value, feasibility and evidence. Use when several problems compete for delivery capacity.
suboss87/FDEOps
Stars: 817Claude 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: 817Claude 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: 817Claude CodeCodexChallenge a proposed solution by identifying and testing consequential assumptions. Use when the brief feels too certain or discovery reveals contradictions.
suboss87/FDEOps
Stars: 817Claude CodeCodexAssess the impact of a proposed change on dependencies and shared infrastructure. Use before touching unfamiliar or consequential systems.
suboss87/FDEOps
Stars: 817Claude CodeCodexMap stakeholders, decision rights, influence and blockers from supplied evidence. Use when ownership is unclear or the stakeholder landscape changes.
suboss87/FDEOps
Stars: 817Claude CodeCodexA small community registry starter plugin used to verify OpenDesign marketplace install flows.
nexu-io/open-design
Stars: 108kClaude CodeCodexYour brand designer. Names the business (with the trademark, domain and handle checks to run before falling in love with a name), writes the voice, a one-line promise and a tagline, and briefs the look: colours, type, logo and the first things a customer sees, so they match the positioning the marketing director chose. Use when the user says "name my business", "brand this", "logo", "brand identity", "what should it look like", "tagline", or "brand voice".
Jakeschincariol/founder-skill
Stars: 4kClaude CodeCodexMaps every competitor and the gap they leave. Finds the direct competitors, indirect ones and the substitutes a buyer would use instead, from public sources only, and records what each sells, at what price, how they position themselves and what their customers complain about in public reviews, every fact with a link. Ends with a positioning map and the gap the new business can own. Use when the user says "who are my competitors", "is this market crowded", "what else is out there", "competitor analysis", "find the gap", or "who am I up against".
Jakeschincariol/founder-skill
Stars: 4kClaude CodeCodexYour launch lead. Builds a dated, step-by-step launch plan: a cheap real-world test first (a waitlist, a pre-sale or a pop-up with a real price, so real buyers confirm what the simulated panel said), then the countdown to opening day with owners and deadlines, the launch-day run sheet, and the first 30 days of what to measure and what to change. Use when the user says "how do I launch", "launch plan", "when can I open", "launch checklist", "go live", or "soft open".
Jakeschincariol/founder-skill
Stars: 4kClaude CodeCodex