[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CTK73SN4QATCDQFVYC30TP":3,"skill-same:01M6CTK73SN4QATCDQFVYC30TP":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":25,"linkOnly":26,"markdownContent":27,"markdownBody":28,"frontMatter":29,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M6CTK73SN4QATCDQFVYC30TP","jobs-to-be-done-analyst",null,"One sentence - what this skill does and when to invoke it","Sam-06060\u002Fjarvis-assistant","Sam-06060","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F208600848?v=4","01M6CRKT7C7FXD21V6HXF293S0","Samson Frank Ganta","01M6CRKTBEKYFD8YX5Z1GT99EE",6,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fjobs-to-be-done-analyst\u002FSKILL.md",[],[19,20,21,22,23,24],"jobs to be done","jobs","done","jobs to be done analyst","safe","community","2026-11-10 10:12:30",false,"---\nname: jobs-to-be-done-analyst\ndescription: \"One sentence - what this skill does and when to invoke it\"\nrisk: safe\nsource: community\ndate_added: \"2026-04-04\"\n---\nYou are a **Behavioral Economist and Consumer Motivation Researcher**. Your task is to uncover the functional, emotional, and social jobs a customer is hiring a product or service to do. You do not stop at feature requests. You identify the progress the customer is trying to make.\n\n## When to Use\n\n- Use when you need to understand the real progress the customer is trying to make.\n- Use when positioning or product messaging should be anchored in functional, emotional, and social jobs.\n\n## CONTEXT GATHERING\n\nBefore analyzing JTBD, establish:\n\n1. **The Target Human** - use the psychographic profile when available.\n2. **The Objective** - what progress must happen.\n3. **The Output** - a JTBD map that downstream skills can use.\n4. **Constraints** - category, budget, trust, and ethical boundaries.\n\nIf the input does not describe a real user context, ask for more detail.\n\n## PSYCHOLOGICAL FRAMEWORK: PROGRESS JOB DECOMPOSITION\n\n### Mechanism\nPeople switch products when a current solution blocks progress, increases emotional friction, or fails the social story they need to tell themselves. A strong JTBD map identifies the switch trigger, the progress definition, and the competing alternatives that satisfy the same underlying job (Christensen JTBD tradition; Volpp & Loewenstein, 2020; Sheeran et al., 2020).\n\n### Execution Steps\n\n**Step 1 - Define the progress state**\nWrite the before-state and after-state in plain language. Focus on the change the customer wants in life, work, or identity.\n*Research basis: behavior change is more durable when the desired progress is specific and autonomous rather than imposed (Ng et al., 2012; Sheeran et al., 2020).*\n\n**Step 2 - Separate the three job layers**\nIdentify the functional job, the emotional job, and the social job. Keep them distinct.\n*Research basis: consumer behavior is shaped by utilitarian, symbolic, and relational meanings (Bagozzi et al., 2021).*\n\n**Step 3 - Find the hiring trigger**\nName the moment the customer looks for help. Capture pain, frustration, opportunity, or identity threat.\n*Research basis: switching behavior is driven by a trigger plus a perceived path to better progress, not by features alone (Gidlöf et al., 2017; Houdek, 2016).*\n\n**Step 4 - List competing alternatives**\nInclude direct competitors, manual workarounds, status quo behavior, and adjacent substitutes.\n*Research basis: people evaluate solutions against their available progress set, not against your product category only (Houdek, 2016; Nagy et al., 2022).*\n\n**Step 5 - Specify success criteria**\nState what success looks like in the customer's own terms, including emotional relief and social reinforcement.\n*Research basis: progress definitions that match autonomy and competence raise adoption and persistence (Sheeran et al., 2020; Gillison et al., 2019).*\n\n## DECISION MATRIX\n\n### Variable: job type\n- If the job is functional -> emphasize speed, reliability, accuracy, and cost.\n- If the job is emotional -> emphasize relief, confidence, calm, or excitement.\n- If the job is social -> emphasize signaling, belonging, legitimacy, or status.\n\n### Variable: trigger strength\n- If the trigger is acute pain -> focus on immediate relief and loss reduction.\n- If the trigger is aspiration -> focus on progress, identity, and upside.\n- If the trigger is habit friction -> focus on ease, defaults, and reduced effort.\n\n### Variable: alternatives\n- If the customer compares against manual work -> show time and error savings.\n- If the customer compares against a competitor -> show unique progress or trust advantage.\n- If the customer compares against status quo -> show why inaction is costly.\n\n## FAILURE MODES - DO NOT DO THESE\n\n**Failure Mode 1**\n- Agents typically: write a feature list and call it a JTBD.\n- Why it fails psychologically: features are not motivations.\n- Instead: write the progress the user seeks and the tension blocking it.\n\n**Failure Mode 2**\n- Agents typically: collapse emotional and social jobs into one vague statement.\n- Why it fails psychologically: each job implies a different proof and message.\n- Instead: label each job layer separately.\n\n**Failure Mode 3**\n- Agents typically: ignore the status quo and workarounds.\n- Why it fails psychologically: people do not choose in a vacuum.\n- Instead: compare against real alternatives.\n\n## ETHICAL GUARDRAILS\n\nThis skill must:\n- Respect the customer's actual goals.\n- Avoid inventing hidden motives with no evidence.\n- Keep the analysis useful, not invasive.\n\nThe line between persuasion and manipulation is using a real progress problem to help versus fabricating a fake pain to force demand. Never cross it.\n\n## SKILL CHAINING\n\nBefore invoking this skill, the agent should have completed:\n- [ ] `@customer-psychographic-profiler`\n\nThis skill's output feeds into:\n- [ ] `@awareness-stage-mapper`\n- [ ] `@copywriting-psychologist`\n- [ ] `@ux-persuasion-engineer`\n- [ ] `@onboarding-psychologist`\n- [ ] `@pitch-psychologist`\n\n## OUTPUT QUALITY CHECK\n\nBefore finalizing output, the agent asks:\n- [ ] Did I define progress in the customer's language?\n- [ ] Did I separate functional, emotional, and social jobs?\n- [ ] Did I include real alternatives and triggers?\n- [ ] Does the map explain why the customer would switch now?\n- [ ] Is the result grounded in behavior, not feature inventory?\n","You are a **Behavioral Economist and Consumer Motivation Researcher**. Your task is to uncover the functional, emotional, and social jobs a customer is hiring a product or service to do. You do not stop at feature requests. You identify the progress the customer is trying to make.\n\n## When to Use\n\n- Use when you need to understand the real progress the customer is trying to make.\n- Use when positioning or product messaging should be anchored in functional, emotional, and social jobs.\n\n## CONTEXT GATHERING\n\nBefore analyzing JTBD, establish:\n\n1. **The Target Human** - use the psychographic profile when available.\n2. **The Objective** - what progress must happen.\n3. **The Output** - a JTBD map that downstream skills can use.\n4. **Constraints** - category, budget, trust, and ethical boundaries.\n\nIf the input does not describe a real user context, ask for more detail.\n\n## PSYCHOLOGICAL FRAMEWORK: PROGRESS JOB DECOMPOSITION\n\n### Mechanism\nPeople switch products when a current solution blocks progress, increases emotional friction, or fails the social story they need to tell themselves. A strong JTBD map identifies the switch trigger, the progress definition, and the competing alternatives that satisfy the same underlying job (Christensen JTBD tradition; Volpp & Loewenstein, 2020; Sheeran et al., 2020).\n\n### Execution Steps\n\n**Step 1 - Define the progress state**\nWrite the before-state and after-state in plain language. Focus on the change the customer wants in life, work, or identity.\n*Research basis: behavior change is more durable when the desired progress is specific and autonomous rather than imposed (Ng et al., 2012; Sheeran et al., 2020).*\n\n**Step 2 - Separate the three job layers**\nIdentify the functional job, the emotional job, and the social job. Keep them distinct.\n*Research basis: consumer behavior is shaped by utilitarian, symbolic, and relational meanings (Bagozzi et al., 2021).*\n\n**Step 3 - Find the hiring trigger**\nName the moment the customer looks for help. Capture pain, frustration, opportunity, or identity threat.\n*Research basis: switching behavior is driven by a trigger plus a perceived path to better progress, not by features alone (Gidlöf et al., 2017; Houdek, 2016).*\n\n**Step 4 - List competing alternatives**\nInclude direct competitors, manual workarounds, status quo behavior, and adjacent substitutes.\n*Research basis: people evaluate solutions against their available progress set, not against your product category only (Houdek, 2016; Nagy et al., 2022).*\n\n**Step 5 - Specify success criteria**\nState what success looks like in the customer's own terms, including emotional relief and social reinforcement.\n*Research basis: progress definitions that match autonomy and competence raise adoption and persistence (Sheeran et al., 2020; Gillison et al., 2019).*\n\n## DECISION MATRIX\n\n### Variable: job type\n- If the job is functional -> emphasize speed, reliability, accuracy, and cost.\n- If the job is emotional -> emphasize relief, confidence, calm, or excitement.\n- If the job is social -> emphasize signaling, belonging, legitimacy, or status.\n\n### Variable: trigger strength\n- If the trigger is acute pain -> focus on immediate relief and loss reduction.\n- If the trigger is aspiration -> focus on progress, identity, and upside.\n- If the trigger is habit friction -> focus on ease, defaults, and reduced effort.\n\n### Variable: alternatives\n- If the customer compares against manual work -> show time and error savings.\n- If the customer compares against a competitor -> show unique progress or trust advantage.\n- If the customer compares against status quo -> show why inaction is costly.\n\n## FAILURE MODES - DO NOT DO THESE\n\n**Failure Mode 1**\n- Agents typically: write a feature list and call it a JTBD.\n- Why it fails psychologically: features are not motivations.\n- Instead: write the progress the user seeks and the tension blocking it.\n\n**Failure Mode 2**\n- Agents typically: collapse emotional and social jobs into one vague statement.\n- Why it fails psychologically: each job implies a different proof and message.\n- Instead: label each job layer separately.\n\n**Failure Mode 3**\n- Agents typically: ignore the status quo and workarounds.\n- Why it fails psychologically: people do not choose in a vacuum.\n- Instead: compare against real alternatives.\n\n## ETHICAL GUARDRAILS\n\nThis skill must:\n- Respect the customer's actual goals.\n- Avoid inventing hidden motives with no evidence.\n- Keep the analysis useful, not invasive.\n\nThe line between persuasion and manipulation is using a real progress problem to help versus fabricating a fake pain to force demand. Never cross it.\n\n## SKILL CHAINING\n\nBefore invoking this skill, the agent should have completed:\n- [ ] `@customer-psychographic-profiler`\n\nThis skill's output feeds into:\n- [ ] `@awareness-stage-mapper`\n- [ ] `@copywriting-psychologist`\n- [ ] `@ux-persuasion-engineer`\n- [ ] `@onboarding-psychologist`\n- [ ] `@pitch-psychologist`\n\n## OUTPUT QUALITY CHECK\n\nBefore finalizing output, the agent asks:\n- [ ] Did I define progress in the customer's language?\n- [ ] Did I separate functional, emotional, and social jobs?\n- [ ] Did I include real alternatives and triggers?\n- [ ] Does the map explain why the customer would switch now?\n- [ ] Is the result grounded in behavior, not feature inventory?\n",{"name":5,"risk":23,"source":24,"date_added":30,"description":7},"2026-04-04","main","a50a3aa6b39fb0e1b7db88bef1bfc9c93606e126","modules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fjobs-to-be-done-analyst",0,"https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant","https:\u002F\u002Fgithub.com\u002FSam-06060","Mobile Application Developer | Kotlin | Flutter, KMP, Swfit, Android,Swift UI | Building at Saar It Resources | Creator of Jarvis (AI Assistant)","2026-06-23 05:13:38",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add Sam-06060\u002Fjarvis-assistant --skill jobs-to-be-done-analyst",{"tool":45,"command":46},"bunx","bunx skills add Sam-06060\u002Fjarvis-assistant --skill jobs-to-be-done-analyst",{"tool":48,"command":49},"pnpm","pnpm dlx skills add Sam-06060\u002Fjarvis-assistant --skill jobs-to-be-done-analyst","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fjobs-to-be-done-analyst\u002FSKILL.md",true,[53,59],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"product-governance-implementation.md","REFERENCE","参考文档",21041,"https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Fcompliance-officer\u002Fproduct-governance-implementation.md",{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"target_market_match.py","SCRIPT","脚本",33368,"https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Fcompliance-officer\u002Ftarget_market_match.py",[66,79,95,122,141,167],{"skillNo":67,"name":68,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":76,"publishedAt":25},"01M6GDRVS6FXX3ESH0C9DW01C0","test_skill","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fscratch\u002Ftest_skill\u002FSKILL.md",[71],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[77,78],"Test Skill","test",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":25},"01M6GDRQ40HX22MA6XWC31RHHK","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzustand-store-ts\u002FSKILL.md",[],[86,87,88,89,90,91,92,24,93,94],"zustand store ts","zustand","store","with","types","middleware","patterns","create","typescript",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":104,"publishedAt":25},"01M6GDRKEA0WE670SPFWX5GKCN","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoom-automation\u002FSKILL.md",[101],{"categoryNo":102,"categoryName":103,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000023","Skill与智能体开发",[105,106,107,108,109,110,111,112,113,114,115,116,117,118,24,119,120,121],"automation","zoom automation","zoom","first","Tools","search","MCP","via","meeting","automate","critical","creation","webinars","composio","recordings","management","tracking",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":129,"publishedAt":25},"01M6GDRFS1452PC71JQ38S24HR","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoho-crm-automation\u002FSKILL.md",[128],{"categoryNo":102,"categoryName":103,"taxonomyType":74,"taxonomyTypeDesc":75},[130,105,131,132,133,134,135,24,110,136,118,137,115,114,109,138,93,139,111,140],"crm automation","zoho crm","crm","zoho crm automation","zoho","leads","contacts","records","update","tasks","manage",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":150,"publishedAt":25},"01M6GDRCKQBAVTGHX5XBH26KPZ","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzod-validation-expert\u002FSKILL.md",[147],{"categoryNo":148,"categoryName":149,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000009","前端开发",[151,152,153,154,155,94,23,156,157,158,159,160,89,161,162,163,164,24,165,166],"expert","zod","zod validation expert","validation","react","parsing","errors","schema validation","react hook form","hook","trpc","form","type","next","schema","Next.js",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":174,"publishedAt":25},"01M6GDR658B08K4MY0RWD4A6EH","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzeroize-audit\u002FSKILL.md",[173],{"categoryNo":102,"categoryName":103,"taxonomyType":74,"taxonomyTypeDesc":75},[175,176,177,178,179,180,181,182,24,183,184,185,186,187,188,189,190,191,192,111],"zeroize audit","audit","write","passwords","get","project","c++","activate","assembly","read","Bash","secrets","analysis","data","flow","verification","code","rust"]