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.
Plan and run task-based usability sessions, observe participant behavior without coaching, and turn evidence into prioritized design findings. Use when a prototype or product journey needs validation, a team disagrees about ease of use, or analytics show…
Evaluate and select a supplier through a consistent, conflict-aware evidence process. Use when multiple vendors or sourcing options must be compared against approved requirements.
Run an academic peer review through conflict checks, claim and method assessment, constructive evidence-based comments, confidentiality, and recommendation boundaries. Use when evaluating a manuscript, proposal, or scholarly artifact.
Run several coding agents in parallel on one repository from a shared work queue, with per-agent isolation, serialized builds, disk limits, and a supervision loop that reclaims stalled work. Use when someone asks to run a coding swarm, work through open beads…
Coordinate live event decisions, incidents, resources, communication, and recovery through one operating structure. Use when a large, distributed, high-profile, or high-consequence event needs real-time cross-team control.
Test event people, content, cues, systems, access, and recovery before participants arrive. Use when a program has live dependencies that cannot be trusted from documents alone.
Learn from a career conversation through preparation, listening, bounded questions, and reciprocal follow-up. Use when someone has agreed to share experience outside a formal hiring interview.
Sample a dataset with a documented frame, method, seed, strata, privacy controls, and representativeness checks. Use when a full dataset is too large or sensitive for inspection, testing, labeling, or analysis.
Turn a savings wish into a number, a date, and weekly math. Tracked somewhere the person will keep seeing it. Use when they say "I'm saving for a car", "how long until I can afford X", or "I can never save money".
Find scholarships the person can win. Big databases plus the local awards most people miss, in a deadline tracker. Use when they say "find me scholarships", "how do I pay for college", or "are there scholarships for someone like me".
Turn a freelance inquiry into a clear project scope with outcomes, deliverables, responsibilities, assumptions, change rules, payment milestones, and acceptance checks. Use when a client request is vague, someone needs a statement of work, or a freelancer…
Make a screen-recorded tutorial on something they know. OBS set up, beats scripted, recorded, edited, published. Use when they say "I want to make a tutorial", "record my screen", or just solved something worth showing.
Secure file downloads with per-request authorization, safe storage indirection, bounded delivery, and revocation evidence. Use when private, tenant-scoped, generated, or untrusted files are served through a web application.
Secure an internal API with workload identity, authorization, transport protection, input limits, audit, segmentation, and abuse resistance. Use when a service boundary is private but still consequential.
Secure file uploads through strict acceptance rules, isolated storage, content inspection, and authorized delivery. Use when users or integrations can place files into an application.
Select B-roll that clarifies place, action, evidence, transition, or emotion without misleading viewers. Use when supporting footage must strengthen an edit while preserving factual context.
List one real item for sale, properly. Photos, honest description, checked price, shipping, and the common scams named first. Use when they say "help me sell my X", "how do I list this", or "is this buyer message a scam".
Make a small site findable by name. Titles, descriptions, headings, sitemap, and Search Console, with expectations set honestly. Use when they ask "how do I get on Google", "why doesn't my site show up", or after a site ships.
Set a project milestone with a measurable outcome, acceptance evidence, owner, date, dependencies, and decision consequence. Use when a plan needs a verifiable checkpoint rather than a vague phase label.
Implement a webhook receiver with signature verification, idempotency, retries, replay tools, and observable delivery. Use when one service must react to events from another, an integration sends callbacks, or webhook deliveries are unreliable or duplicated.
Ship a repeatable data pipeline that survives retries, late records, schema changes, and backfills without corrupting downstream results. Define contracts, checkpoints, quality checks, and recovery. Use when a recurring data flow becomes production…
Get the person shipping on GitHub. Account, git on their machine, a first repo, and Pages serving a URL. Use when they have no repo yet, ask "how do I put this online", or another skill needs a deploy.
Build a small dashboard over their real data. The three numbers that matter, updating when the data does. Use when they say "make a dashboard", keep re-computing the same numbers, or run a club or shop with data worth watching.
Turn their presentation into a deck that doesn't look templated. Restructured, restyled, presenter notes, exported. Use when they say "help with my slides", "my presentation looks bad", or a talk is coming up.
Announce something the person made in their own words. Covers one suitable platform, a truthful draft, checked media and link, publication, and follow-up. Use when they say "how do I announce this", "help me post about my project", or they shipped something…
Build spreadsheet fluency on data they already track. Structure, formulas, lookups, and summaries on their own sheet. Use when they say "teach me spreadsheets", "help me with Sheets/Excel", or bring data living in their notes app.
Start a real club, this month. Pitch written, first three members recruited, first meeting on the calendar. Use when they say "I want to start a club", "there's no club for X at my school", or want leadership experience that is true.
Start a newsletter the person can sustain. Niche chosen, platform set up, issue one written and sent. Use when they say "I want to start a newsletter" or want a writing habit that shows up on a resume.
Pick one project and start it today. Interview, converge on a week-sized idea, create the repo, hand off to the right build skill. Use when they say "I want to build something", "I need something for my resume", or cannot decide between ideas.
Figure out what site to make, then kick it off. Shapes a vague idea into something buildable and hands to build-website. Use when they say "I want a website" but do not yet know what it is for.
Start a channel around something the person knows. Channel created, first video planned to the shot level, effort stated honestly. Use when they say "I want to start a YouTube channel", "should I make videos", or want to turn a hobby into content.
Choose the first app to build and kick it off. One small app solving a problem they have, repo created, handed to build-web-app. Use when they say "I want to make an app", "I have an app idea", or their idea is too big to start.
Start selling one thing, honestly. Something they can make or resell, one channel, first listing live. Use when they say "I want to make money", "can I sell my art", or want small-business experience for a resume.
Store user preferences with minimal data, clear ownership, versioned schemas, and reliable synchronization. Use when an application must remember settings across sessions or devices.
Stress-test a cash-flow model with combined operational, financing, timing, and liquidity shocks plus actionable thresholds. Use when evaluating runway, resilience, covenants, or contingency funding.
Build a study system around their actual courses. Capture, spaced review, and a weekly plan that survives a real week. Use when they say "help me study", "I keep cramming", or "I can't keep up with my classes".
Summarize a journal article by preserving its question, method, sample, findings, uncertainty, limitations, and contribution. Use when a reader needs an accurate compact account of a study.
Convert a long support thread into a concise, traceable case summary with customer goal, chronology, evidence, actions, and open decisions. Use when a ticket needs escalation, handoff, review, or a reliable status update.
Turn research records into traceable, bounded design insights and decisions. Use when multiple sessions, methods, participants, or sources must be analyzed without erasing contradiction, minority needs, or uncertainty.
Combine diverse research into a claim-by-claim synthesis that preserves disagreement, quality differences, and uncertainty. Use when moving from collected sources to findings.