Menu
Skills in this repository
SkillsMP has collected 1,021 skills from protosphinx/sphinxstack. Open a skill to review its source and details.
protosphinx/sphinxstackShowing 40 of 1,021 collected skills.
Restore a production service while preserving the evidence needed to understand the failure. Establish impact, contain harm, test the recovery, and record follow-up work. Use when real users are affected or a production signal requires coordinated…
Build an honest comparison for one real decision. Criteria the person chose, weights, data per option, and what the numbers cannot settle. Use when they are stuck between options or ask "help me decide".
Decline an interview clearly and professionally while protecting privacy and closing outstanding logistics. Use when a candidate no longer wants or cannot continue in a hiring process.
Decode a JWT without confusing readable claims with verified identity or authorization. Use when inspecting token structure, metadata, timing, audience, or signature requirements.
Decompose a production monolith through measured domain boundaries, dependency and data ownership, compatible extraction waves, parity tests, and rollback. Use when independent evolution is needed without sacrificing operating control.
Define a project assumption with its basis, uncertainty, dependency, impact, test, owner, and decision deadline. Use when a plan relies on something not yet proven.
Turn a broad topic into a bounded, answerable question with explicit concepts, scope, evidence needs, and decision relevance. Use when starting research, an essay, a report, or an evidence review.
Define alert severity from user impact, urgency, scope, reversibility, and required authority. Use when operational notifications need consistent routing and response expectations.
Define a specific audience from evidence, context, needs, and constraints. Use when a message, product, service, event, or campaign lacks a clear primary audience or relies on vague demographic labels.
Turn an event idea into a bounded brief with outcomes, audience, constraints, and evidence. Use when organizers need an agreed basis for planning before choosing format, venue, or suppliers.
Define the smallest product or service that delivers one real user outcome and tests the riskiest product assumption with explicit exclusions and evidence. Use when a product idea has grown into too many features, a team cannot agree what version one…
Turn product values and user evidence into testable design choices. Use when a team needs shared guidance for recurring tradeoffs that rules, components, or brand adjectives do not resolve.
Turn a purchasing need into testable outcome, service, security, and operating requirements. Use when a team must brief suppliers without prescribing an unexamined solution.
Define product metrics from user outcomes, specify exact events and populations, add guardrails, and produce a measurement plan that supports decisions. Use when a team asks what to measure, has conflicting dashboard numbers, or needs success criteria before…
Define service indicators and reliability objectives from user outcomes and evidence. Use when teams need measurable availability, latency, correctness, durability, or freshness commitments and defensible alerting.
Define measurable and operationally credible support response, update, and resolution objectives in a service-level document. Use when establishing or revising service levels across customer tiers, channels, hours, severities, or vendors.
Transfer ownership of a connected workstream with outcomes, authority, context, resources, and accountability. Use when someone should lead ongoing work rather than execute a single task.
Put an existing project online with a free host. GitHub Pages, Cloudflare Pages, or Netlify, verified live. Use when they have files but no URL, say "how do I put this online", or want a site off localhost.
Deprecate an API operation or version with consumer evidence, replacement parity, notice, migration support, telemetry, and controlled removal. Use when evolving a public or internal API without surprising active consumers.
Design a durable background job with explicit payload, ownership, idempotency, retries, deadlines, progress, cancellation, and recovery. Use when work must continue outside an interactive request.
Design a background task runner with durable identity, idempotency, scheduling, retries, leases, cancellation, observability, and recovery. Use when work must continue safely outside a request.
Design a bulk-action flow with explicit selection scope, previews, authorization, progress, partial-result reconciliation, and recovery. Use when one command can change many records or objects.
Design cache invalidation from data authority, key identity, dependency, freshness, event ordering, failure, and repair requirements. Use when cached values can become stale across processes or regions.
Design a change-control process for scope, impact, evidence, authority, scheduling, implementation, rollback, communication, and post-change verification. Use when modifications can affect shared services, contracts, schedules, budgets, safety, compliance, or…
Design a trustworthy checkout flow that preserves price, inventory, payment, accessibility, and recovery invariants. Use when customers must complete a purchase across cart, identity, delivery, tax, discounts, and payment decisions.
Design a command-line interface with coherent commands, arguments, output, errors, configuration, and compatibility for both people and scripts. Use when creating a new CLI, reshaping an existing command, or defining a stable shell-facing contract before…
Design a command palette with discoverable search, scoped actions, keyboard access, permissions, confirmation, and recovery. Use when frequent users need fast access to a large set of navigation and product commands.
Design community-based research with shared questions, authority, benefit, consent, data governance, compensation, interpretation, and exit. Use when research concerns a community that should shape how knowledge is produced and used.
Design a comparison interface with normalized attributes, transparent missingness, user-relevant differences, and accessible scanning. Use when people must evaluate products, plans, records, candidates, or scenarios side by side.
Design configuration distribution with source authority, schema, versioning, signing, targeting, staged propagation, rollback, caching, and audit. Use when many runtimes depend on changing operational settings.
Model structured content around meaning, relationships, reuse, and lifecycle. Use when content must serve multiple channels, locales, permissions, workflows, or migrations without becoming ungoverned fields.
Design a secure content-preview workflow with draft identity, access, production parity, expiry, collaboration, robots exclusion, and publish reconciliation. Use when editors or reviewers need to inspect unpublished web content safely.
Design contract testing across schemas, examples, provider behavior, consumer assumptions, compatibility, versions, and deployment gates. Use when independently released systems must integrate safely.
Design a cookie consent interface with genuine purpose-level choice, equal refusal, evidence, and withdrawal. Use when nonessential browser storage or tracking requires user control.
Design a crisis decision log that preserves facts, uncertainty, options, authority, rationale, dissent, actions, communications, review, and supersession. Use when fast decisions must remain accountable under changing evidence.
Design a cross-border executive search through mandate, governance, evidence-based sourcing, lawful data, fair assessment, conflicts, mobility, disclosure, appointment, and transition. Use when a consequential leadership role spans jurisdictions and…
Design a dashboard around user decisions, trustworthy metrics, comparison context, accessibility, and drill-down paths. Use when several measures must support recurring monitoring or action.
Design a recurring data-access review that verifies identity, purpose, scope, sensitivity, privilege, activity, ownership, and removal. Use when governing who can query, export, administer, or share datasets and platforms.
Design a data contract registry with ownership, schema and semantic versions, compatibility, quality, policy, lineage, consumer evidence, and deprecation. Use when independently changing producers and consumers share data.
Design a data deletion workflow with verified subject scope, authority, dependency tracing, holds, backups, processors, proof, and restoration controls. Use when data must be erased without deleting the wrong records or leaving active copies.