Results for “job-polling”

12 skills
More results
wondelai
jobs-to-be-done
Analyze customer needs by identifying the 'job' they hire a product to do, covering job statements, forces of progress, and competitive landscapes.
1.6k · bundle
deanpeters
jobs-to-be-done
Uncover customer jobs, pains, and gains in a structured JTBD format to clarify unmet needs, reposition products, or improve discovery and messaging.
5.6k · bundle
owl-listener
jobs-to-be-done
Map user Jobs-to-Be-Done with functional, emotional, and social dimensions plus outcome expectations to reframe product decisions around user motivations.
1.7k
pawbytes
paw-upwork-research
Live Upwork market research producing a ranked niche-opportunity dashboard. Use when the user wants to scan the Upwork market, find or validate a freelance niche, asks 'is there demand for X', wants competitor profile analysis, or needs rate observations for a niche. Triggers: 'research my niche', 'scan the Upwork market', 'is there demand', 'what should I specialize in', 'check the market', 'what do freelancers charge for X'.
85 · bundle
livelybug
research-ops
Evidence-first current-state research workflow for ECC. Use when the user wants fresh facts, comparisons, enrichment, or a recommendation built from current public evidence and any supplied local context.
0
subvisual
research-synthesis
research-synthesis
0 · bundle
mhassan0000
research-ops
Runs evidence-first research workflows, choosing the lightest useful path from search to deep synthesis, and labels facts, inference, and recommendations.
1
pwdev-solucoes
voc-research
Coleta a linguagem literal do público em avaliações, fóruns, redes sociais, tickets de suporte e transcrições de vendas para gerar um banco de frases verbatim que orienta a escrita de copy.
2
browser-act
indeed-job-search
Extract structured job listing data from Indeed search results, including job titles, companies, salaries, descriptions, benefits, and apply links.
3.7k · bundle
subvisual
jobs-to-be-done
Use to CREATE or REVIEW a Job to be Done (JTBD) in Alan Klement's demand-side, progress-based sense — a job is the progress a customer is trying to make, never a task or feature. Trigger whenever someone wants to write or draft a JTBD, job statement, or job story; figure out the real motivation, struggle, or progress behind a feature, request, or product; understand why customers switch, adopt, or churn; turn interview notes or research into jobs; or pressure-test, sharpen, or rewrite existing JTBDs into proper jobs. Also trigger on "grill my JTBD", "is this a real job or just a task/feature", "what's the actual job here", "why would they switch". In an A-Team target repo, jobs are durable artifacts — this skill writes docs/product/jtbd/NN-<slug>.md per CONTRACT.md and never deletes or silently rewrites a job. Do NOT use for writing PRDs, roadmaps, tickets, or acceptance criteria (those consume a finished JTBD), or for implementation user stories.
0 · bundle
azusagasaku
research-ops
以证据为先的ECC当前状态研究工作流程。当用户希望基于当前公开证据和提供的本地上下文获取最新事实、比较、丰富信息或建议时使用。
0