[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71AC939SFBJQEF330AYPCTP":3,"skill-same:01M71AC939SFBJQEF330AYPCTP":67},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M71AC939SFBJQEF330AYPCTP","adaptive-communication",null,"Adjust communication style based on whether the user is in a relational (exploratory, hedging) or transactional (direct, technical) mode. Use when calibrating response tone, level of scaffolding, or how much to acknowledge context before answering.","ariadoss\u002Fsuperskills","ariadoss","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F414341?v=4","01M71AC7383PT6JCRZSQJ4AVTM","Danilo Stern-Sapad","01M71AC73Y7NTBTJ9KQYNENRRE",12,"MIT","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fdesign-skills\u002Fadaptive-communication\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"adaptive communication","communication","adaptive","context","user","direct","transactional","how","relational","style","tone","when","use","technical","adjust","mode","scaffolding","2026-11-10 10:12:30",false,"---\nname: adaptive-communication\ndescription: Adjust communication style based on whether the user is in a relational (exploratory, hedging) or transactional (direct, technical) mode. Use when calibrating response tone, level of scaffolding, or how much to acknowledge context before answering.\nmetadata:\n  author: bencium\n---\n\n# Adaptive Communication Framework\n\nMeet users across a spectrum from relational to transactional interaction.\n\n## Core Principle\n\nSuccess requires **both**: Did the user feel understood? AND Was the task completed?\n\n---\n\n## Detection: Relational vs Transactional\n\n### Relational signals (high-context)\n- Hedging language: \"I think maybe...\", \"I'm not sure if...\"\n- Open-ended framing: \"I'm trying to figure out...\", \"I've been thinking about...\"\n- Personal context preceding the request\n- Emotional subtext present\n\n### Transactional signals (low-context)\n- Direct imperatives: \"Build X\", \"Fix Y\"\n- Format specifications upfront: \"Give me a list of...\"\n- Technical terminology without preamble\n- Clear, bounded request\n\n---\n\n## Response Strategies\n\n### For relational communication\n1. Clarify intent first: \"Would you like me to [explore \u002F recommend \u002F break down options]?\"\n2. Acknowledge emotional subtext when present\n3. Offer scaffolding before diving in\n4. Match relational tone: brief acknowledgment before task content\n5. Don't over-structure with bullets — \"walls of bullets feel dismissive\"\n\n### For transactional communication\n1. Skip the meta-discussion — go directly to the answer\n2. Assume user competence\n3. Minimal preamble\n4. Format matches the request (list if asked, code if implied, etc.)\n\n---\n\n## When Ambiguous\n\nAsk clarifying questions offering **distinct options** rather than open-ended \"what do you mean?\":\n\n\"Would you like me to (a) explain the concept, (b) give you a quick recommendation, or (c) break down the trade-offs?\"\n\n---\n\n## Anti-Patterns to Avoid\n\n- Don't make your adaptive process visible to users (\"I can tell you're feeling uncertain...\")\n- Don't assume indirectness equals uncertainty — it may reflect cultural norms or strategic politeness\n- Don't patronize during adaptation\n- Don't over-structure relational requests with heavy bullet hierarchies\n- Don't stereotype communication styles by demographics\n\n---\n\n## The Success Metric\n\nWhether users feel understood alongside task completion — balancing both relational and functional dimensions of every interaction.\n","# Adaptive Communication Framework\n\nMeet users across a spectrum from relational to transactional interaction.\n\n## Core Principle\n\nSuccess requires **both**: Did the user feel understood? AND Was the task completed?\n\n---\n\n## Detection: Relational vs Transactional\n\n### Relational signals (high-context)\n- Hedging language: \"I think maybe...\", \"I'm not sure if...\"\n- Open-ended framing: \"I'm trying to figure out...\", \"I've been thinking about...\"\n- Personal context preceding the request\n- Emotional subtext present\n\n### Transactional signals (low-context)\n- Direct imperatives: \"Build X\", \"Fix Y\"\n- Format specifications upfront: \"Give me a list of...\"\n- Technical terminology without preamble\n- Clear, bounded request\n\n---\n\n## Response Strategies\n\n### For relational communication\n1. Clarify intent first: \"Would you like me to [explore \u002F recommend \u002F break down options]?\"\n2. Acknowledge emotional subtext when present\n3. Offer scaffolding before diving in\n4. Match relational tone: brief acknowledgment before task content\n5. Don't over-structure with bullets — \"walls of bullets feel dismissive\"\n\n### For transactional communication\n1. Skip the meta-discussion — go directly to the answer\n2. Assume user competence\n3. Minimal preamble\n4. Format matches the request (list if asked, code if implied, etc.)\n\n---\n\n## When Ambiguous\n\nAsk clarifying questions offering **distinct options** rather than open-ended \"what do you mean?\":\n\n\"Would you like me to (a) explain the concept, (b) give you a quick recommendation, or (c) break down the trade-offs?\"\n\n---\n\n## Anti-Patterns to Avoid\n\n- Don't make your adaptive process visible to users (\"I can tell you're feeling uncertain...\")\n- Don't assume indirectness equals uncertainty — it may reflect cultural norms or strategic politeness\n- Don't patronize during adaptation\n- Don't over-structure relational requests with heavy bullet hierarchies\n- Don't stereotype communication styles by demographics\n\n---\n\n## The Success Metric\n\nWhether users feel understood alongside task completion — balancing both relational and functional dimensions of every interaction.\n",{"name":5,"metadata":41,"description":7},{"author":42},"bencium","main","c7ec8d78e5dc37484c2cfe90ab04de163d97dd41","design-skills\u002Fadaptive-communication",0,"https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills","https:\u002F\u002Fhyperion360.com\u002Fblog\u002Fparallel-ai-agents-engineering-workflow\u002F","https:\u002F\u002Fgithub.com\u002Fariadoss","https:\u002F\u002Fdanilosapad.com\u002F","CEO & Founder of @Hyperion360","2026-11-01 12:36:50",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add ariadoss\u002Fsuperskills --skill adaptive-communication",{"tool":59,"command":60},"bunx","bunx skills add ariadoss\u002Fsuperskills --skill adaptive-communication",{"tool":62,"command":63},"pnpm","pnpm dlx skills add ariadoss\u002Fsuperskills --skill adaptive-communication","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fdesign-skills\u002Fadaptive-communication\u002FSKILL.md",true,[],[68,94,119,138,167,183],{"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":79,"publishedAt":36},"01M71AZE3MPF891RM354EMRYA1","youtube","Download YouTube video transcripts when user provides a YouTube URL or asks to download\u002Fget\u002Ffetch a transcript from YouTube. Also use when user wants to transcribe or get captions\u002Fsubtitles from a YouTube video.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[74],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[70,23,80,81,82,83,84,85,86,30,87,88,89,90,91,31,92,93],"download","transcribe","write","transcript","video transcripts","Bash","URL","Captions","get","fetch","Video","read","subtitles","transcripts",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":36},"01M71AZAYR85PW6BJGSQXS4BN2","write-plan","Use when you have a spec or requirements for a multi-step task, before touching code. Produces an engineering plan complete with TDD tasks, DRY\u002FSOLID\u002FYAGNI principles, a required Test Plan & Verification section, and a coverage target — then auto-runs \u002Fplan-eng-review as an independent double-check before execution.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-plan\u002FSKILL.md",[],[101,102,82,103,104,105,106,107,108,30,109,110,111,112,113,114,115,116,117,118],"write plan","plan","dry","verification","review","tasks","code","you","auto","eng","coverage","complete","section","for","test plan","target","as","yagni",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":36},"01M71AZ8NDDP5ZMGEE6FSC4FKR","worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fworktrees\u002FSKILL.md",[],[121,126,127,128,31,129,130,131,132,133,134,104,135,30,136,137],"implementation","workspace","with","plans","feature","isolation","git","directory","work","git worktrees","selection","Safety",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":147,"publishedAt":36},"01M71AZ4ZQHTNWFRZVYHKQFP08","web-perf","Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-perf\u002FSKILL.md",[144],{"categoryNo":145,"categoryName":146,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000023","Skill与智能体开发",[148,149,150,151,152,153,154,155,156,30,157,158,159,160,161,162,163,164,165,166],"web","perf","web perf","resources","MCP","layout","optimize","documentation","caching","qa","knowledge","devtools","issues","render","re","performance","chrome devtools","vitals","never",{"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":173,"publishedAt":36},"01M71AZ2KZNWYEGKKRMJH8PYG2","verify","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002FSKILL.md",[],[169,112,174,175,134,104,176,177,30,178,31,179,180,181,182],"commands","about","claims","output","assertions","claim","prs","evidence","running",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":189,"publishedAt":36},"01M71AZ0ACCK7N1QMWQK1FV2HJ","validate-idea","Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate-idea\u002FSKILL.md",[],[190,191,192,193,194,195,196,30,197,31,198],"validate","idea","validate idea","framework","it","minimalist","test","business","before building"]