[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMKWJS4F5S98PZQ2P8K8J9":3,"skill-same:01M7EMKWJS4F5S98PZQ2P8K8J9":47},{"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":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EMKWJS4F5S98PZQ2P8K8J9","cognitive-task-analysis",null,"Designing and analyzing cognitive tasks — Stroop, n-back, task-switching, and process-pure measurement.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-cognitive-task-analysis\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cognitive-task-analysis\ndescription: Designing and analyzing cognitive tasks — Stroop, n-back, task-switching, and process-pure measurement.\ncategory: scientific\n---\n\n## Overview\n\ncognitive-task-analysis covers the classic experimental paradigms of cognitive psychology — Stroop,\nflanker, n-back, task-switching, stop-signal, attentional blink — and how to analyze them so the\nnumbers reflect the intended process. The central problem: no task is process-pure, so every\n\"cognitive measure\" is contaminated by general speed, strategy, and task-specific demands. This\nskill is about designing tasks and analyses that isolate processes anyway.\n\n## When to use\n\n- Choosing a paradigm for a construct: inhibition, working memory, shifting, sustained attention.\n- Task design: trial counts, congruency ratios, timing, practice blocks.\n- Computing standard indices: Stroop interference, switch costs, stop-signal reaction time (SSRT).\n- Difference scores: when they're justified and why they're often unreliable.\n- Modeling: drift-diffusion and process models as alternatives to raw RT\u002Faccuracy.\n- Individual-differences use: reliability of task indices for correlational research.\n\n## Core concepts\n\n- **The task-impurity problem.** Every cognitive task measures the target process plus perception,\n  motor speed, motivation, and strategy. A \"worse Stroop score\" could be slower color naming, not\n  worse inhibition. Control conditions (congruent\u002Fneutral baselines) exist to subtract the\n  impurity — but subtraction assumes pure insertion, which is itself questionable.\n- **Difference scores and their reliability.** Interference = incongruent − congruent. Difference\n  scores amplify measurement error: reliability of a difference is lower than its components\n  (often much lower). For individual-differences research, this is frequently fatal — check the\n  reliability of the difference score itself, not just the raw conditions.\n- **Stroop\u002Fflanker.** Interference effects (incongruent slower\u002Fless accurate). Design: enough\n  trials per condition (≥50 for stable means), congruent\u002Fneutral\u002Fincongruent proportions that\n  don't let participants strategize, manual vs vocal responses documented. Analyze: interference\n  and facilitation separately; check for speed-accuracy trade-offs.\n- **N-back.** Working-memory updating: 1-, 2-, 3-back loads; lures (n+1 matches) to prevent\n  familiarity strategies. Dependent measures: hits\u002Ffalse alarms (d′), not just accuracy — response\n  bias varies wildly. Note: n-back reliability for individual differences is modest; it's a\n  within-subjects manipulation tool first.\n- **Task-switching.** Switch cost = switch − repeat RT. Design: predictable (AABB) vs unpredictable\n  (cued) switching, preparation intervals (CTI) to separate preparation from residual cost.\n  Distinguish switch costs (transient control) from mixing costs (repeat trials in mixed vs pure\n  blocks — sustained control).\n- **Stop-signal task and SSRT.** The race model: go process vs stop process. SSRT estimated via\n  the integration method with staircase-adjusted stop-signal delays (targeting ~50% inhibition).\n  Critical assumption: the staircase must actually track 50% — verify, and exclude participants\n  where it fails. SSRT is not directly observed; it's model-derived.\n- **Drift-diffusion modeling.** Decomposes RT\u002Faccuracy into drift rate (evidence quality),\n  boundary separation (caution), and non-decision time (encoding\u002Fmotor). Often resolves\n  ambiguities raw RTs can't (is the group slower because of worse processing or more caution?).\n  Needs sufficient trials (≥100+ per condition ideally); fit with hierarchical Bayesian tools\n  (HDDM) for typical sample sizes.\n- **Reliability for individual differences.** Most cognitive tasks were built for within-subjects\n  experimental effects, where reliability demands are low. Repurposing them as individual-\n  difference measures requires demonstrating test-retest reliability of the specific index —\n  many classic \"effects\" have difference-score reliabilities near zero.\n\n## Practical workflow\n\n1. **Pick the paradigm for the process**, not the fashion. List the process, its confounds, and\n   the control conditions that isolate it.\n2. **Design trials.** Enough per condition for stable estimates; proportions that prevent\n   strategy; practice blocks with feedback; documented timing and response modality.\n3. **Pilot.** Check effect presence (manipulation works?), RT distributions, error rates (5-15%\n   is the sweet spot — floor\u002Fceiling kills sensitivity), and participant comprehension.\n4. **Preprocess.** Preregistered exclusions; analyze RT and accuracy jointly; compute d′ where\n   relevant.\n5. **Model.** Start with condition means and preregistered contrasts; use DDM\u002FHDDM when the\n   question is about processing vs caution; mixed-effects models for trial-level data.\n6. **Reliability check (if individual differences).** Test-retest or split-half of the actual\n   index; disattenuate correlations; abandon indices with near-zero reliability.\n7. **Report.** Trial counts, exclusions, full descriptive statistics per condition, and the exact\n   computation of every derived index.\n\n## Common pitfalls\n\n- Difference scores with unreported (terrible) reliability used in correlations.\n- Interpreting slower RT as worse cognition without checking accuracy (caution shifts).\n- N-back accuracy without d′ (response bias masquerading as memory).\n- SSRT from a failed staircase (not ~50% inhibition).\n- Too few trials for DDM fitting, or fitting DDM to group means instead of hierarchically.\n- Strategy shifts across conditions mistaken for process differences.\n- Ceiling\u002Ffloor effects from poorly calibrated difficulty.\n","## Overview\n\ncognitive-task-analysis covers the classic experimental paradigms of cognitive psychology — Stroop,\nflanker, n-back, task-switching, stop-signal, attentional blink — and how to analyze them so the\nnumbers reflect the intended process. The central problem: no task is process-pure, so every\n\"cognitive measure\" is contaminated by general speed, strategy, and task-specific demands. This\nskill is about designing tasks and analyses that isolate processes anyway.\n\n## When to use\n\n- Choosing a paradigm for a construct: inhibition, working memory, shifting, sustained attention.\n- Task design: trial counts, congruency ratios, timing, practice blocks.\n- Computing standard indices: Stroop interference, switch costs, stop-signal reaction time (SSRT).\n- Difference scores: when they're justified and why they're often unreliable.\n- Modeling: drift-diffusion and process models as alternatives to raw RT\u002Faccuracy.\n- Individual-differences use: reliability of task indices for correlational research.\n\n## Core concepts\n\n- **The task-impurity problem.** Every cognitive task measures the target process plus perception,\n  motor speed, motivation, and strategy. A \"worse Stroop score\" could be slower color naming, not\n  worse inhibition. Control conditions (congruent\u002Fneutral baselines) exist to subtract the\n  impurity — but subtraction assumes pure insertion, which is itself questionable.\n- **Difference scores and their reliability.** Interference = incongruent − congruent. Difference\n  scores amplify measurement error: reliability of a difference is lower than its components\n  (often much lower). For individual-differences research, this is frequently fatal — check the\n  reliability of the difference score itself, not just the raw conditions.\n- **Stroop\u002Fflanker.** Interference effects (incongruent slower\u002Fless accurate). Design: enough\n  trials per condition (≥50 for stable means), congruent\u002Fneutral\u002Fincongruent proportions that\n  don't let participants strategize, manual vs vocal responses documented. Analyze: interference\n  and facilitation separately; check for speed-accuracy trade-offs.\n- **N-back.** Working-memory updating: 1-, 2-, 3-back loads; lures (n+1 matches) to prevent\n  familiarity strategies. Dependent measures: hits\u002Ffalse alarms (d′), not just accuracy — response\n  bias varies wildly. Note: n-back reliability for individual differences is modest; it's a\n  within-subjects manipulation tool first.\n- **Task-switching.** Switch cost = switch − repeat RT. Design: predictable (AABB) vs unpredictable\n  (cued) switching, preparation intervals (CTI) to separate preparation from residual cost.\n  Distinguish switch costs (transient control) from mixing costs (repeat trials in mixed vs pure\n  blocks — sustained control).\n- **Stop-signal task and SSRT.** The race model: go process vs stop process. SSRT estimated via\n  the integration method with staircase-adjusted stop-signal delays (targeting ~50% inhibition).\n  Critical assumption: the staircase must actually track 50% — verify, and exclude participants\n  where it fails. SSRT is not directly observed; it's model-derived.\n- **Drift-diffusion modeling.** Decomposes RT\u002Faccuracy into drift rate (evidence quality),\n  boundary separation (caution), and non-decision time (encoding\u002Fmotor). Often resolves\n  ambiguities raw RTs can't (is the group slower because of worse processing or more caution?).\n  Needs sufficient trials (≥100+ per condition ideally); fit with hierarchical Bayesian tools\n  (HDDM) for typical sample sizes.\n- **Reliability for individual differences.** Most cognitive tasks were built for within-subjects\n  experimental effects, where reliability demands are low. Repurposing them as individual-\n  difference measures requires demonstrating test-retest reliability of the specific index —\n  many classic \"effects\" have difference-score reliabilities near zero.\n\n## Practical workflow\n\n1. **Pick the paradigm for the process**, not the fashion. List the process, its confounds, and\n   the control conditions that isolate it.\n2. **Design trials.** Enough per condition for stable estimates; proportions that prevent\n   strategy; practice blocks with feedback; documented timing and response modality.\n3. **Pilot.** Check effect presence (manipulation works?), RT distributions, error rates (5-15%\n   is the sweet spot — floor\u002Fceiling kills sensitivity), and participant comprehension.\n4. **Preprocess.** Preregistered exclusions; analyze RT and accuracy jointly; compute d′ where\n   relevant.\n5. **Model.** Start with condition means and preregistered contrasts; use DDM\u002FHDDM when the\n   question is about processing vs caution; mixed-effects models for trial-level data.\n6. **Reliability check (if individual differences).** Test-retest or split-half of the actual\n   index; disattenuate correlations; abandon indices with near-zero reliability.\n7. **Report.** Trial counts, exclusions, full descriptive statistics per condition, and the exact\n   computation of every derived index.\n\n## Common pitfalls\n\n- Difference scores with unreported (terrible) reliability used in correlations.\n- Interpreting slower RT as worse cognition without checking accuracy (caution shifts).\n- N-back accuracy without d′ (response bias masquerading as memory).\n- SSRT from a failed staircase (not ~50% inhibition).\n- Too few trials for DDM fitting, or fitting DDM to group means instead of hierarchically.\n- Strategy shifts across conditions mistaken for process differences.\n- Ceiling\u002Ffloor effects from poorly calibrated difficulty.\n",{"name":5,"category":24,"description":7},"scientific","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-cognitive-task-analysis",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill cognitive-task-analysis",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill cognitive-task-analysis",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill cognitive-task-analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-cognitive-task-analysis\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\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":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]