Design multitenant authorization with explicit isolation invariants, centralized decisions, adversarial testing, and recoverable administration. Use when one application serves organizations whose identities, data, and authority must never cross.
Skills in this repository
protosphinx/sphinxstack - Page 10
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.
Design the signals needed to tell whether users are succeeding and to explain failures quickly. Connect service indicators, structured events, traces, alerts, and runbooks to real journeys. Use when a live system is hard to operate or before a new production…
Design role-based access control from explicit resources, actions, constraints, and ownership. Use when permissions have outgrown scattered conditionals or informal administrator conventions.
Design a compact service metric set for demand, errors, duration, saturation, dependencies, and completed outcomes. Use when teams need actionable measurement without uncontrolled telemetry growth.
Design session issuance, rotation, expiration, revocation, and device visibility around authentication risk. Use when a web or native application must preserve signed-in state safely.
Detect and triage financial-data anomalies using reconciled controls, documented expectations, reproducible tests, and evidence-preserving investigation. Use when transactions, balances, reports, or integrations appear unusual.
Detect and contain metric cardinality growth by tracing series creation to unstable label dimensions. Use when telemetry cost, memory, query latency, or ingestion limits rise unexpectedly.
Direct a safe, consistent voice-recording session with performance context, technical checks, consent, and usable coverage. Use when recording narration, dialogue, prompts, or voiceover.
Build an evidence-backed billing dispute, submit it through the right channel, and track the account through resolution. Use when a charge, invoice, credit, or balance appears wrong.
Document a data field's business meaning, source, type, units, allowed values, lifecycle, quality rules, sensitivity, and consumers. Use when creating or correcting a data dictionary or schema reference.
Document a decision owner with scope, authority, inputs, consulted parties, deadline, escalation, conflicts, record, and review. Use when accountability is unclear across several stakeholders.
Record a design choice with context, evidence, alternatives, tradeoffs, and review triggers. Use when a consequential or recurring decision should remain understandable after people, constraints, or implementation change.
Document a reusable design value by semantic purpose, not appearance alone. Use when color, spacing, type, motion, elevation, radius, size, or other decisions must remain consistent across themes and platforms.
Create a maintainable known-issue record with verified symptoms, affected scope, safe workarounds, status, and update ownership. Use when support, customers, or operators need a reliable reference for an unresolved defect.
Document a laboratory or computational experiment with timestamped purpose, materials, procedure, deviations, raw evidence, observations, and next steps. Use when creating a reproducible contemporaneous research record.
Document a process exception with scope, reason, authority, risk, compensating controls, duration, review, and closure. Use when an approved rule cannot be followed for a bounded case.
Record a purchasing decision with alternatives, evidence, authority, and follow-up conditions. Use when a team needs a durable rationale for an award, renewal, exception, or no-buy decision.
Document a refund from request and authority through calculation, processor action, customer notice, ledger posting, and settlement. Use when money is returned or credited after a sale.
Document a time-bounded departure from a security requirement with accountable risk ownership. Use when a control cannot be met immediately and a formal exception or compensating-control decision is required.
Document a service dependency's contract, ownership, limits, failure behavior, observability, and recovery path. Use when a production capability relies on another internal or external system.
Document a software system's boundaries, components, data, decisions, runtime, security, failure modes, and change paths. Use when maintainers or reviewers need a current architecture guide grounded in the real implementation.
Document a UI component's purpose, anatomy, behavior, states, content, accessibility, and implementation contract. Use when designers and engineers need one practical source for correct reuse.
Capture a repeatable work process with inputs, roles, controls, exceptions, and evidence of completion. Use when a workflow must be taught, audited, improved, or handed over.
Publish a tested API request and response example with prerequisites, safe placeholders, errors, and version context. Use when developers need a copyable example for one API operation or integration path.
Document an environment variable as a configuration contract with purpose, type, default, scope, secrecy, validation, and failure behavior. Use when software behavior depends on deploy-time configuration.
Document an interface icon's meaning, variants, accessible name behavior, visual construction, and prohibited uses. Use when an icon enters or changes within a shared product or design system.
Document confidential or restricted work at a safe abstraction level while preserving truthful scope, contribution, and outcome. Use when relevant experience is covered by agreements, security duties, client privacy, or trade-secret controls.
Document financial assumptions with ownership, evidence, units, scenarios, dependencies, and review triggers. Use when a budget, forecast, valuation, pricing case, or investment decision depends on uncertain inputs.
Document professional certifications and licenses with exact name, issuer, status, date, identifier policy, and verification evidence. Use when credentials are relevant to a resume, CV, profile, or application.
Document transferable skills by tracing each capability to real context, action, constraint, outcome, and evidence. Use when experience from another role, study, care, service, or project must support a career move.
Capture credible work accomplishments with context, contribution, outcome, and source evidence. Use when someone needs a durable record for a resume, review, interview, promotion, or portfolio.
Edit a documentary scene with source traceability, truthful chronology, participant protection, narrative clarity, and rights-aware media choices. Use when shaping real events or testimony into a coherent sequence.
Edit a multiauthor report into one coherent, evidence-traceable document while preserving specialist meaning, attribution, dissent, and review history. Use when several contributors have drafted overlapping or inconsistent sections.
Edit a podcast interview for clarity, pace, accuracy, consent, and listening continuity without changing meaning. Use when a recorded conversation must become a publishable episode.
Cut a watchable 30-60 second vertical video from their footage. Hook in the first two seconds, tight cuts, captions on. Use when they say "make this a short", "edit this into a reel", or have raw phone footage worth posting.
Teach the edit pass on a draft the person already has. Cut, reorder, sharpen, read aloud; before and after preserved. Use when they say "can you edit this", "make this better", "is this too long", or paste any draft of their own.
Get an email to a professor written and sent. Short, specific, in the person's own words. Use when they say "how do I email my professor", "can you check this email", or they keep putting the ask off.
Evaluate a business loan offer by modeling proceeds, fees, repayment cash flows, collateral, covenants, guarantees, and downside cases. Use when comparing financing terms or preparing a borrowing decision.
Assess a long-lived asset using lifecycle economics, capacity, safety, and delivery evidence. Use when equipment, property, or infrastructure requires a consequential investment decision.
Evaluate a global mobility offer across role, immigration, tax, pay, benefits, family, housing, safety, healthcare, return rights, and failure scenarios. Use when employment requires relocation or cross-border work.