[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CPDACDPZNYESAEG1SV7HJ0":3,"skill-same:01M7CPDACDPZNYESAEG1SV7HJ0":53},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":46},"01M7CPDACDPZNYESAEG1SV7HJ0","to-questionnaire",null,"Turn a decision you can't fully answer into a questionnaire for someone else to fill in.","ThienHN0910\u002FTemplate-P","ThienHN0910","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F84314573?v=4","01M7CPATNRT0K5DSRBBHEQJJT3","HO NGOC THIEN","01M7CPATPDW689M0YJMGGJGFYZ",2,"MIT","https:\u002F\u002Fgithub.com\u002FThienHN0910\u002FTemplate-P\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fpocock\u002Fto-questionnaire\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: to-questionnaire\ndescription: Turn a decision you can't fully answer into a questionnaire for someone else to fill in.\ndisable-model-invocation: true\n---\n\nTurn something the user can't answer alone into a **questionnaire**: a Markdown document they hand to one person to fill in async, or fill out together over a meeting. The recipient holds knowledge the user lacks; the questionnaire pulls it out of them.\n\n**Grill the send, not the subject.** Interview the user only about the _send_, which they can always answer: who it goes to, and what they need back. The questions in the document then target the **gap** between what the recipient knows and what the user needs.\n\n\n1. **Who is it going to?** Ask, in one exchange, the recipient's role, expertise, and relationship to the user. This fixes the questionnaire's tone and how much context it must carry. Done when you know who the recipient is and what they know that the user doesn't.\n\n2. **What do you need back?** Ask, in one exchange, the specific decisions or facts the user can't resolve alone and needs from this person. Done when you have a concrete list of what the user must walk away able to do or decide.\n\n3. **Write the questionnaire.** Draft questions aimed at the gap from steps 1–2, following the Document structure below. Write it to `to-questionnaire-\u003Cslug>.md` in the current directory (slug from the topic) and report the path. Done when the file exists and every item the user named in step 2 is covered by a question.\n\n## Document structure\n\nFrame the document as a **discovery questionnaire**: the user lacks context, the recipient holds it. Order questions most-important-first, since async means you may only get one pass, and group them under `##` headings by theme once there are more than a handful. Write it using the template below.\n\n\u003Cquestionnaire-template>\n\n# \u003CQuestionnaire title>\n\n**Purpose:** why this questionnaire exists and the decision riding on it.\n\n**From:** \u003Cthe user>, **To:** \u003Cthe recipient>, **How your answers will be used:** \u003Cwhere they go>\n\n## Context\n\nOne paragraph orienting a recipient who wasn't in the user's head. Enough to answer well, not a page.\n\n## How to answer\n\nDeadline and rough effort. Partial answers and \"I don't know\" are useful: flag anything you're unsure of rather than skipping it.\n\n## \u003CTheme heading>\n\nOne `##` section per theme. Under each, its questions, most-important-first. Every question is one idea, never compound, with an answer stub directly beneath, and a one-line _why this matters_ only where the question could be misread or invite a throwaway answer.\n\n\u003Cquestion-example>\n### What load is the system expected to handle at launch?\n\n_Why this matters: it decides whether we provision for burst traffic now or defer it._\n\n>\n\u003C\u002Fquestion-example>\n\n## Anything else?\n\nA closing catch-all: anything we didn't ask that we should know?\n\n\u003C\u002Fquestionnaire-template>\n","Turn something the user can't answer alone into a **questionnaire**: a Markdown document they hand to one person to fill in async, or fill out together over a meeting. The recipient holds knowledge the user lacks; the questionnaire pulls it out of them.\n\n**Grill the send, not the subject.** Interview the user only about the _send_, which they can always answer: who it goes to, and what they need back. The questions in the document then target the **gap** between what the recipient knows and what the user needs.\n\n\n1. **Who is it going to?** Ask, in one exchange, the recipient's role, expertise, and relationship to the user. This fixes the questionnaire's tone and how much context it must carry. Done when you know who the recipient is and what they know that the user doesn't.\n\n2. **What do you need back?** Ask, in one exchange, the specific decisions or facts the user can't resolve alone and needs from this person. Done when you have a concrete list of what the user must walk away able to do or decide.\n\n3. **Write the questionnaire.** Draft questions aimed at the gap from steps 1–2, following the Document structure below. Write it to `to-questionnaire-\u003Cslug>.md` in the current directory (slug from the topic) and report the path. Done when the file exists and every item the user named in step 2 is covered by a question.\n\n## Document structure\n\nFrame the document as a **discovery questionnaire**: the user lacks context, the recipient holds it. Order questions most-important-first, since async means you may only get one pass, and group them under `##` headings by theme once there are more than a handful. Write it using the template below.\n\n\u003Cquestionnaire-template>\n\n# \u003CQuestionnaire title>\n\n**Purpose:** why this questionnaire exists and the decision riding on it.\n\n**From:** \u003Cthe user>, **To:** \u003Cthe recipient>, **How your answers will be used:** \u003Cwhere they go>\n\n## Context\n\nOne paragraph orienting a recipient who wasn't in the user's head. Enough to answer well, not a page.\n\n## How to answer\n\nDeadline and rough effort. Partial answers and \"I don't know\" are useful: flag anything you're unsure of rather than skipping it.\n\n## \u003CTheme heading>\n\nOne `##` section per theme. Under each, its questions, most-important-first. Every question is one idea, never compound, with an answer stub directly beneath, and a one-line _why this matters_ only where the question could be misread or invite a throwaway answer.\n\n\u003Cquestion-example>\n### What load is the system expected to handle at launch?\n\n_Why this matters: it decides whether we provision for burst traffic now or defer it._\n\n>\n\u003C\u002Fquestion-example>\n\n## Anything else?\n\nA closing catch-all: anything we didn't ask that we should know?\n\n\u003C\u002Fquestionnaire-template>\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","a1dd0de00a0db2613339b710e20f458f78439cbe","templates\u002Fskills\u002Fpocock\u002Fto-questionnaire",0,"https:\u002F\u002Fgithub.com\u002FThienHN0910\u002FTemplate-P","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@thienhn\u002Fcreate-template","https:\u002F\u002Fgithub.com\u002FThienHN0910","https:\u002F\u002Fthienhn.io.vn\u002Fabout","2026-11-09 15:21:02",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":24},[36,39,42],{"tool":37,"command":38},"npx","npx skills add ThienHN0910\u002FTemplate-P --skill to-questionnaire",{"tool":40,"command":41},"bunx","bunx skills add ThienHN0910\u002FTemplate-P --skill to-questionnaire",{"tool":43,"command":44},"pnpm","pnpm dlx skills add ThienHN0910\u002FTemplate-P --skill to-questionnaire","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FThienHN0910\u002FTemplate-P\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fpocock\u002Fto-questionnaire\u002FSKILL.md",[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",166,"https:\u002F\u002Fgithub.com\u002FThienHN0910\u002FTemplate-P\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fpocock\u002Fto-questionnaire\u002Fagents\u002Fopenai.yaml",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7CPGT91CB71D2H3Q8WB36P3","stitch-design-taste","Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.","https:\u002F\u002Fgithub.com\u002FThienHN0910\u002FTemplate-P\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Ftaste\u002Fstitch-design-taste\u002FSKILL.md",[],[],{"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":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7CPGP56DA29RQS9Z61T05MW","minimalist-ui","Clean editorial-style interfaces. Warm monochrome palette, typographic contrast, flat bento grids, muted pastels. No gradients, no heavy shadows.","https:\u002F\u002Fgithub.com\u002FThienHN0910\u002FTemplate-P\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Ftaste\u002Fminimalist-ui\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7CPGGFY7H5BY59NRZMSH3AG","industrial-brutalist-ui","Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics. Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects. For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints.","https:\u002F\u002Fgithub.com\u002FThienHN0910\u002FTemplate-P\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Ftaste\u002Findustrial-brutalist-ui\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7CPG61M01PSE6Y07ZA7Y1VG","imagegen-frontend-web","Elite frontend image-direction skill for generating premium, conversion-aware website design references. CRITICAL OUTPUT RULE — generate ONE separate horizontal image FOR EVERY section. A landing page with 8 sections produces 8 images. Never compress multiple sections into one image. Enforces composition variety (not always left-text \u002F right-image), background-image freedom, varied CTAs, varied hero scales (giant \u002F mid \u002F mini minimalist), narrative concept spine, second-read moments, and a single consistent palette across all images. Optimized for landing pages, marketing sites, and product comps that developers or coding models can accurately recreate.","https:\u002F\u002Fgithub.com\u002FThienHN0910\u002FTemplate-P\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Ftaste\u002Fimagegen-frontend-web\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7CPFVXKVQX1QZADQ84QENHJ","imagegen-frontend-mobile","Elite mobile app image-generation skill for creating premium, app-native screen concepts and flows. Designed for iOS, Android, and cross-platform mobile products. Prioritizes clean hierarchy, comfortably readable text, strong multi-screen consistency, controlled color palettes, non-generic creative direction, textured surfaces, image-led composition, tasteful custom iconography, and clean phone mockup framing. By default, screens should be shown inside a subtle premium iPhone or similar phone mockup with a visible frame, while the main focus stays on the app content itself. This skill generates images only. It does not write code.","https:\u002F\u002Fgithub.com\u002FThienHN0910\u002FTemplate-P\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Ftaste\u002Fimagegen-frontend-mobile\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7CPFHSD6HJ5MKGCWQZZZ439","image-to-code","Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards, generate fresh standalone images for sections or detail views instead of cropping old ones, avoid lazy under-generation, avoid cards-inside-cards-inside-cards UI, and keep the hero clean, spacious, readable, and visible on a small laptop.","https:\u002F\u002Fgithub.com\u002FThienHN0910\u002FTemplate-P\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Ftaste\u002Fimage-to-code\u002FSKILL.md",[],[]]