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.
Write focused landing-page copy around one audience decision and credible value. Use when a campaign, product, service, event, or resource needs a clear page with evidence, boundaries, and a useful next action.
Write a localization brief that defines audience, market, purpose, source version, terminology, context, constraints, formats, review, and delivery evidence. Use when translators and localizers need enough information to produce accurate usable content.
Write and verify a lower-third name and role caption for accuracy, consent, readability, timing, and safe display. Use when identifying a speaker or source on screen.
Write a media file manifest with stable identity, filename, checksum, format, duration, tracks, rights, language, accessibility, source, and delivery state. Use when media assets must be transferred or archived reliably.
Write a meeting decision with its question, outcome, authority, rationale, conditions, dissent, owner, effective date, and follow-up. Use when a group has made a choice that others must understand and execute.
Write a concise networking introduction grounded in real context, shared relevance, and a bounded request. Use when introducing yourself to a professional contact.
Write a policy summary that preserves scope, duties, rights, exceptions, dates, contacts, and authoritative links in plain language. Use when readers need a shorter guide to an approved policy.
Write and test a positioning statement grounded in audience evidence and credible difference. Use when a product, service, project, or program needs a clear category, value, alternative, and proof.
Write a factual press release around a defensible news event and useful source material. Use when an organization has an approved announcement that journalists or public stakeholders may reasonably need.
Write an accurate announcement for a verified product change. Use when customers, users, partners, or internal teams need to understand what changed, why it matters, what they should do, and what remains limited.
Write a production safety brief with task hazards, controls, roles, welfare, emergency actions, and stop authority. Use when a media crew works in a location or activity with meaningful risk.
Write a truthful professional biography fitted to a specific audience, length, and use. Use when preparing a website, speaker, publication, team, or application bio.
Write a resume project description that explains the problem, individual contribution, decisions, technology or method, and verified result. Use when projects provide relevant evidence beyond formal job titles.
Write a public consultation response that answers the official questions with evidence, affected perspectives, alternatives, impacts, and transparent interests. Use when an organization or group comments on a proposed rule, policy, standard, or plan.
Write a public FAQ answer that directly resolves a real question with accurate scope, plain language, examples, limitations, and next steps. Use when readers repeatedly need the same trustworthy explanation.
Write a concise recruiter follow-up that adds context, asks for a clear next step, and respects the stated timeline. Use when a job-search conversation needs a professional nudge without pressure or repetition.
Write a regulatory response that answers each request with verified facts, evidence, authority, uncertainty, remediation, commitments, and controlled attachments. Use when responding formally to a regulator, inspector, authority, or supervisory body.
Write a release announcement with verified availability, audience value, changes, limitations, actions, support, and evidence links. Use when a product, feature, service, report, or version is ready to communicate.
Draft a fair request for proposal with comparable responses and explicit evaluation rules. Use when an organization is inviting suppliers to propose a consequential product or service.
Write a research CV that documents methods, contributions, outputs, data, software, funding, collaboration, and impact accurately. Use when applying to research roles inside or outside academia.
Write a research proposal that connects a bounded gap to a justified method, ethics, data plan, schedule, resources, risks, and feasible contribution. Use when seeking approval, supervision, funding, or project direction.
Write a focused research question with a defined population, phenomenon, setting, scope, and evidence need. Use when a broad topic must become an answerable inquiry.
Write a resume after a career break with truthful chronology, privacy-respecting context, current evidence, relevant prior work, and return readiness. Use when time away from paid employment must be presented clearly.
Write a resume for a regulated profession with verified licenses, jurisdictions, scope, supervised practice, credentials, compliance, and role evidence. Use when applying in healthcare, law, finance, aviation, engineering, education, safety, or another…
Write a resume for an academic role by selecting verified research, teaching, service, methods, and impact for the stated position. Use when a concise role-specific resume is needed instead of a complete academic CV.
Write a resume for a public-sector role by matching verified evidence to stated criteria, accountability, service, accessibility, and required format. Use when applying through a structured government or public-institution process.
Write a concise resume headline that identifies relevant role, specialization, and credible value without unsupported superlatives. Use when the top of a resume needs immediate positioning.
Write a concise resume summary from verified experience, role direction, distinctive strengths, scope, and evidence. Use when a resume needs a truthful opening tailored to a specific opportunity.
Turn one operational action into a safe, verifiable runbook step with prerequisites, expected observations, failure handling, and recovery. Use when documenting a repeated diagnostic, mitigation, deployment, or maintenance action.
Write a concise post-call sales message that records verified needs, decisions, commitments, and the next mutual action. Use when following a discovery call, demo, proposal review, or commercial conversation.
Write a sales resume that verifies quota, attainment, revenue, territory, cycle, customer, pipeline, and individual contribution. Use when applying for revenue, account, business-development, or sales-leadership roles.
Develop a truthful scholarship essay from the applicant's experiences, evidence, and goals while answering the exact prompt. Use when drafting or revising a competitive application essay.
Write a sensitive research summary that communicates findings, uncertainty, methods, limitations, and implications while protecting participants, communities, confidential sources, and restricted data. Use when research involves vulnerable populations,…
Write a short executive summary that presents the decision, evidence, implications, options, recommendation, risk, and next action. Use when leaders need to understand a longer document quickly.
Write a skills-based resume that groups verified capabilities while preserving employers, roles, dates, context, and evidence. Use when relevant experience is non-linear or distributed across work, study, care, service, and projects.
Draft an accurate, useful customer-support response with a clear answer, safe next step, and honest limits. Use when replying to one support email, chat, ticket, review, or community question from verified case context.
Write a systematic review protocol with preregistered questions, eligibility, searches, screening, extraction, bias assessment, synthesis, and amendment control. Use when a review must minimize selection and analysis discretion.
Define a team's purpose, outcomes, boundaries, decision rights, interfaces, and working agreements. Use when forming a team or repairing persistent operating ambiguity.
Write a technical case study from verified architecture, constraints, decisions, implementation, measurements, failures, outcomes, and lessons. Use when documenting how a system or engineering project actually worked.
Write a technical resume that connects systems, decisions, individual scope, constraints, and verified outcomes to a target role. Use when applying for engineering, data, security, infrastructure, or other technical work.