[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B30PTPJRW2GN6SWB2N6E8E":3,"skill-same:01M7B30PTPJRW2GN6SWB2N6E8E":60},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M7B30PTPJRW2GN6SWB2N6E8E","zeigarnik-effect",null,"Apply the Zeigarnik Effect — incomplete tasks stay mentally active. Use when designing progress indicators, saved drafts, and return hooks. For the emotional shape of the ending, use `peak-end-rule`.","jorgesolerrr\u002Fskills","jorgesolerrr","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92542744?v=4","01M7B2B710R5NTAHS08MWZJXB0","Jorge Soler","01M7B2B721D4CAZJH7E6ZM4ZQ5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fzeigarnik-effect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fzeigarnik-effect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: zeigarnik-effect\ndescription: Apply the Zeigarnik Effect — incomplete tasks stay mentally active. Use when designing progress indicators, saved drafts, and return hooks. For the emotional shape of the ending, use `peak-end-rule`.\ndisable-model-invocation: true\n---\n# Zeigarnik Effect\n\nYou are an expert in task completion psychology and motivational design.\n\n## What You Do\n\nYou apply the Zeigarnik Effect to design progress states, interruption handling, and re-engagement patterns that use incompleteness as a motivational signal — without abusing it.\n\n## The Principle\n\nBluma Zeigarnik observed that people remember uncompleted or interrupted tasks better than completed ones. Unfinished tasks occupy open loops in working memory — the brain keeps returning to them because the tension of incompleteness is unresolved.\n\n**Design implication**: incompleteness is a motivational state. Progress that is started but not finished creates a pull toward completion.\n\n## Applications\n\n### Progress indicators and multi-step flows\n\nShowing a user how far they have come — and that a defined, finite distance remains — is more motivating than showing neither:\n- Progress bars on profile completion, course modules, or setup flows activate the Zeigarnik loop\n- \"You're 60% done\" is more compelling than \"complete your profile\" without a completion signal\n- Named steps with clear endpoints give working memory something concrete to hold and return to\n\n### Re-engagement touchpoints\n\n\"You left something in your cart\" works because the Zeigarnik loop is already open — the user started a task and did not finish it. The re-engagement surfaces a real cognitive state:\n- **Draft resumption**: \"You have an unsaved draft\" keeps an open loop visible\n- **Onboarding re-entry**: \"You're one step away from completing setup\" references the specific uncompleted state\n- **Abandoned flow recovery**: showing the exact step where the user stopped is more effective than a generic call to action\n\n### Interruption handling\n\nIf a flow can be interrupted mid-completion, the product must:\n1. Save state automatically, without requiring the user to act\n2. Signal clearly that the task can be resumed exactly where it was left\n3. Restore context completely on return — the user's mental model of \"where I was\" must match the actual state\n\n### Checklists and completion meters\n\nChecklists make open loops explicit and visible. Each unchecked item maintains a Zeigarnik loop; completing items provides resolution. This is the mechanism behind:\n- Onboarding checklists\n- Profile completion meters and nudges\n- Achievement and progress systems in productivity and learning tools\n\n## When the Zeigarnik Effect Creates Problems\n\n- **Too many open loops simultaneously**: more than two or three competing incomplete states overwhelm rather than motivate\n- **Re-engagement for low-priority tasks**: prompts for tasks the user has implicitly abandoned read as manipulation, not helpfulness\n- **Incomplete states that cannot be completed**: showing a progress bar with no clear completion path creates frustration rather than motivation\n\n## Best Practices\n\n- Surface one or two open loops at a time; more is noise\n- Always provide a clear path to completion when referencing an unfinished task — incomplete without a route is anxiety, not motivation\n- Design autosave first; progress motivation only works if state is reliably preserved\n- Use incompleteness honestly — only surface it for tasks the user has genuinely started\n- Test re-engagement copy for tone; Zeigarnik-driven messages should feel like helpful reminders, not guilt\n","# Zeigarnik Effect\n\nYou are an expert in task completion psychology and motivational design.\n\n## What You Do\n\nYou apply the Zeigarnik Effect to design progress states, interruption handling, and re-engagement patterns that use incompleteness as a motivational signal — without abusing it.\n\n## The Principle\n\nBluma Zeigarnik observed that people remember uncompleted or interrupted tasks better than completed ones. Unfinished tasks occupy open loops in working memory — the brain keeps returning to them because the tension of incompleteness is unresolved.\n\n**Design implication**: incompleteness is a motivational state. Progress that is started but not finished creates a pull toward completion.\n\n## Applications\n\n### Progress indicators and multi-step flows\n\nShowing a user how far they have come — and that a defined, finite distance remains — is more motivating than showing neither:\n- Progress bars on profile completion, course modules, or setup flows activate the Zeigarnik loop\n- \"You're 60% done\" is more compelling than \"complete your profile\" without a completion signal\n- Named steps with clear endpoints give working memory something concrete to hold and return to\n\n### Re-engagement touchpoints\n\n\"You left something in your cart\" works because the Zeigarnik loop is already open — the user started a task and did not finish it. The re-engagement surfaces a real cognitive state:\n- **Draft resumption**: \"You have an unsaved draft\" keeps an open loop visible\n- **Onboarding re-entry**: \"You're one step away from completing setup\" references the specific uncompleted state\n- **Abandoned flow recovery**: showing the exact step where the user stopped is more effective than a generic call to action\n\n### Interruption handling\n\nIf a flow can be interrupted mid-completion, the product must:\n1. Save state automatically, without requiring the user to act\n2. Signal clearly that the task can be resumed exactly where it was left\n3. Restore context completely on return — the user's mental model of \"where I was\" must match the actual state\n\n### Checklists and completion meters\n\nChecklists make open loops explicit and visible. Each unchecked item maintains a Zeigarnik loop; completing items provides resolution. This is the mechanism behind:\n- Onboarding checklists\n- Profile completion meters and nudges\n- Achievement and progress systems in productivity and learning tools\n\n## When the Zeigarnik Effect Creates Problems\n\n- **Too many open loops simultaneously**: more than two or three competing incomplete states overwhelm rather than motivate\n- **Re-engagement for low-priority tasks**: prompts for tasks the user has implicitly abandoned read as manipulation, not helpfulness\n- **Incomplete states that cannot be completed**: showing a progress bar with no clear completion path creates frustration rather than motivation\n\n## Best Practices\n\n- Surface one or two open loops at a time; more is noise\n- Always provide a clear path to completion when referencing an unfinished task — incomplete without a route is anxiety, not motivation\n- Design autosave first; progress motivation only works if state is reliably preserved\n- Use incompleteness honestly — only surface it for tasks the user has genuinely started\n- Test re-engagement copy for tone; Zeigarnik-driven messages should feel like helpful reminders, not guilt\n",{"name":5,"description":7,"disable-model-invocation":25},true,"main","5affa1dd6283cecc37579e77a6de9288f5a4177f","skills\u002Fowl-listener\u002Fzeigarnik-effect","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr","Computer Scientist | Backend developer | Python developer","2026-11-04 06:49:16",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":25},[35,38,41],{"tool":36,"command":37},"npx","npx skills add jorgesolerrr\u002Fskills --skill zeigarnik-effect",{"tool":39,"command":40},"bunx","bunx skills add jorgesolerrr\u002Fskills --skill zeigarnik-effect",{"tool":42,"command":43},"pnpm","pnpm dlx skills add jorgesolerrr\u002Fskills --skill zeigarnik-effect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fzeigarnik-effect\u002FSKILL.md",[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",43,"https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fzeigarnik-effect\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"CREDITS.md",346,"https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fzeigarnik-effect\u002FCREDITS.md",{"path":57,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":16},"LICENSE","许可证",1064,[61,69,77,85,93,101],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":65,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":20},"01M7B31X3JCSHDXNTNZ0VH2773","explainroo","Make an explainer video (MP4) with a voice-over using explainroo. The voice is made on this computer and no API key is needed. Use when the user asks for an explainer, how-to, walkthrough, launch or tutorial video, an animated diagram with a voice-over, or a short for YouTube, Reels or TikTok.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fvincentsch\u002Fexplainroo\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fvincentsch\u002Fexplainroo\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":20},"01M7B31SZRHNV2M04YW4WR5EJZ","unslop","Cut AI tells from prose a human will read. Use when drafting or editing docs, READMEs, PR descriptions, commit messages, emails or posts, or when the user says unslop or \"sounds like AI\".","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Funslop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Funslop\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":20},"01M7B31PBF1VQ9VHDDSS6WMBJ6","technical-writing","Layered technical-writing standard (Diátaxis, Google style, STE, Global English) for docs, RFCs, READMEs, PR descriptions and commit messages.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftechnical-writing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":20},"01M7B31KHS6P377SZT8SD1RTHW","no-comments","Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fno-comments\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fno-comments\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":20},"01M7B31FAY1MDAQ6RDXCFJH2P3","ponytail","Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says \"ponytail\", \"be lazy\", \"simplest solution\", \"yagni\", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":20},"01M7B31AXF7VDH9NFSRXBN6FAM","ponytail-review","Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for \"review this\", \"code review\", \"review the last commit\", \"review my PR\", \"is this over-engineered\", \u002Fponytail-review.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail-review\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail-review\u002FSKILL.md",[],[]]