[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M792DHNF3CRA99BV3HTS65NR":3,"skill-same:01M792DHNF3CRA99BV3HTS65NR":62},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M792DHNF3CRA99BV3HTS65NR","research",null,"Investigate properly: frame questions, build source ladders, triangulate, and report findings. Use when investigating complex questions with primary sources.","poorvith-mp\u002Fskills-education","poorvith-mp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F277478855?v=4","01M78Z5K0YH1Z3PX815PGQ96ND","Poorvith M P","01M792ATSH2NKESX1VP51ASDH0",3,"MIT","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-education\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: research\nlast_reviewed: 2026-09-06\ngroup: Research\ndescription: >-\n  Investigate properly: frame questions, build source ladders, triangulate, and report findings.\n  Use when investigating complex questions with primary sources.\n---\n\n# research\n\n## Core Philosophy\nResearch is not browsing search engines, skimming blog posts, and summarizing the first three links. Anyone can query an LLM or Google and produce a surface-level synthesis of conventional wisdom. Rigorous, high-trust research is an **investigative discipline**: it frames sharp, refutable hypotheses, climbs the \"Source Ladder\" to primary provenance, triangulates claims across independent conflicting vectors, audits funding and bias, and delivers structured intelligence with auditable citations.\n\n---\n\n## 4-Step Investigative Research Framework\n\n### Step 1: Question Framing & Scope Bounding\n1. **Refining the Research Perimeter**:\n   - Broad questions produce generic fluff. Narrow inquiries produce high-signal intelligence:\n     - *Fluffy*: \"How does WebAssembly perform?\"\n     - *Incisive*: \"What is the memory and cold-start latency overhead of Wasmtime versus Node.js v20 when executing identical JSON-parsing microservices under 1,000 QPS on AWS Lambda?\"\n2. **Defining the Falsification Criteria**:\n   - State what empirical evidence would refute your initial operating hypothesis.\n\n### Step 2: The Source Ladder Architecture\n1. **Climbing the Provenance Ladder**:\n   - **Tier 1 (Primary Provenance - Highest Trust)**: Source code, benchmark raw telemetry, official RFC specifications, SEC 10-K filings, court transcripts, peer-reviewed clinical trial datasets.\n   - **Tier 2 (Authoritative Secondary)**: Official technical documentation from system authors, seminal textbooks, peer-reviewed review articles.\n   - **Tier 3 (Practitioner Analysis)**: Production post-mortems, engineering blogs from scaled tech companies (e.g. Netflix, Cloudflare).\n   - **Tier 4 (Unverified \u002F Opinion - Zero Trust without Verification)**: Marketing whitepapers, Medium posts, corporate PR releases, Reddit comments.\n2. **The Golden Rule**: Never cite a Tier 4 claim without tracing it back to its Tier 1 origin.\n\n### Step 3: Triangulation & Cross-Vector Verification\n1. **The 3-Vector Rule**:\n   - A non-obvious empirical claim cannot be accepted as fact until verified across **three independent, non-affiliated sources**:\n     - Vector 1: Empirical benchmark or source code audit.\n     - Vector 2: Third-party independent academic replication or audit.\n     - Vector 3: Production post-mortem documenting real-world failure\u002Fsuccess.\n2. **Reconciling Conflicting Findings**:\n   - When Source A says X and Source B says Not-X, identify the hidden variable: Did they test different hardware? Different compiler flags? Different network conditions?\n\n### Step 4: Structuring the Research Dossier\n1. **Standardized Dossier Structure**:\n   - Executive Summary (BLUF: Bottom Line Up Front).\n   - Core Hypotheses & Findings Matrix.\n   - Deep Evidence & Methodology Dissection.\n   - Contradictions & Caveats.\n   - Primary Source Provenance References.\n\n---\n\n## Deliverable Format: High-Trust Research Dossier\n\n```markdown\n# Research Dossier: Edge Compute Cold Starts — Wasmtime vs V8 Isolates\n\n### 1. Executive Summary (BLUF)\nWasmtime delivers a 12x faster cold-start initialization compared to V8 isolates (0.45ms vs 5.6ms), but suffers a 1.8x throughput penalty on heavy numerical compute tasks due to the lack of dynamic JIT profiling and tier-2 optimization.\n\n### 2. Empirical Triangulation Matrix\n\n| Vector | Source \u002F Provenance | Methodology \u002F Scope | Verified Finding |\n|---|---|---|---|\n| **Vector 1: Primary Telemetry** | Bytecode Alliance Wasmtime Benchmarks (v18.0) | Memory footprint per instance | Baseline idle footprint is 180KB RAM vs 18MB for Node.js V8. |\n| **Vector 2: Academic Study** | ACM SIGPLAN 2024 (Müller et al.) | 100k synthetic microservice requests | Cold start latency: 0.42ms (p50), 0.98ms (p99) on Linux x86_64. |\n| **Vector 3: Production Audit** | Fastly Lucet\u002FWasm Architecture Report | Global edge POP telemetry | 99.8% of tenant requests execute in existing pre-warmed memory instances. |\n\n### 3. Critical Contradictions & Edge Cases\n- *Discrepancy*: Several commercial serverless benchmarks claimed Wasm cold starts were 50ms.\n- *Root Cause Analysis*: Tracing the setup revealed those benchmarks included container cold start times (Docker daemon initialization), not raw WebAssembly runtime compilation.\n\n### 4. Primary Source Citations\n1. Bytecode Alliance. (2024). *Wasmtime Performance Suite*. GitHub: https:\u002F\u002Fgithub.com\u002Fbytecodealliance\u002Fwasmtime\n2. Müller, K., et al. (2024). \"Sandboxing at the Edge.\" *ACM SIGPLAN*, 42(3), 112–126.\n```\n\n---\n\n## Worked Example: Investigating an Enterprise Vendor's \"Zero Overhead\" Database Claim\n\n- **Context**: A vendor claimed their distributed database layer introduced \"zero performance overhead\" over raw NVMe disk operations.\n- **Investigation**:\n  1. Cloned the vendor's open-source benchmark repository and reviewed the configuration.\n  2. Discovered the benchmark had disabled write-ahead logging (`fsync=off`) and kept the entire test database within the 64GB OS page cache.\n  3. Reran the benchmark with persistent disk flushing (`O_DIRECT` \u002F `fsync=on`) with working set sizes exceeding RAM.\n- **Outcome**: Uncovered a 42% write latency regression under durable transaction conditions, saving the enterprise from a flawed multi-million-dollar infrastructure migration.\n\n---\n\n## Verification Checklist\n\n- [ ] Specific, falsifiable research question formulated before gathering data.\n- [ ] Source Ladder climbed to primary source code, raw data, or official specs.\n- [ ] Key claims triangulated across at least 3 independent, non-affiliated vectors.\n- [ ] Benchmark conditions audited for hidden configuration biases (e.g. caching, compute parity).\n- [ ] Conflicting data and outlier results acknowledged and reconciled.\n\n---\n\n## Anti-Patterns\n\n- **Single-Source Paraphrasing**: Relying entirely on a single corporate whitepaper or sponsored blog post to make architectural decisions.\n- **Citing Secondary Aggregators**: Citing a news article that cites a blog post that misquotes a scientific paper. Always read the original paper.\n- **Confirmation Bias Hunting**: Searching only for queries that confirm your favorite technical bias (e.g. searching only *\"Why Rust is faster than Go\"*).\n","# research\n\n## Core Philosophy\nResearch is not browsing search engines, skimming blog posts, and summarizing the first three links. Anyone can query an LLM or Google and produce a surface-level synthesis of conventional wisdom. Rigorous, high-trust research is an **investigative discipline**: it frames sharp, refutable hypotheses, climbs the \"Source Ladder\" to primary provenance, triangulates claims across independent conflicting vectors, audits funding and bias, and delivers structured intelligence with auditable citations.\n\n---\n\n## 4-Step Investigative Research Framework\n\n### Step 1: Question Framing & Scope Bounding\n1. **Refining the Research Perimeter**:\n   - Broad questions produce generic fluff. Narrow inquiries produce high-signal intelligence:\n     - *Fluffy*: \"How does WebAssembly perform?\"\n     - *Incisive*: \"What is the memory and cold-start latency overhead of Wasmtime versus Node.js v20 when executing identical JSON-parsing microservices under 1,000 QPS on AWS Lambda?\"\n2. **Defining the Falsification Criteria**:\n   - State what empirical evidence would refute your initial operating hypothesis.\n\n### Step 2: The Source Ladder Architecture\n1. **Climbing the Provenance Ladder**:\n   - **Tier 1 (Primary Provenance - Highest Trust)**: Source code, benchmark raw telemetry, official RFC specifications, SEC 10-K filings, court transcripts, peer-reviewed clinical trial datasets.\n   - **Tier 2 (Authoritative Secondary)**: Official technical documentation from system authors, seminal textbooks, peer-reviewed review articles.\n   - **Tier 3 (Practitioner Analysis)**: Production post-mortems, engineering blogs from scaled tech companies (e.g. Netflix, Cloudflare).\n   - **Tier 4 (Unverified \u002F Opinion - Zero Trust without Verification)**: Marketing whitepapers, Medium posts, corporate PR releases, Reddit comments.\n2. **The Golden Rule**: Never cite a Tier 4 claim without tracing it back to its Tier 1 origin.\n\n### Step 3: Triangulation & Cross-Vector Verification\n1. **The 3-Vector Rule**:\n   - A non-obvious empirical claim cannot be accepted as fact until verified across **three independent, non-affiliated sources**:\n     - Vector 1: Empirical benchmark or source code audit.\n     - Vector 2: Third-party independent academic replication or audit.\n     - Vector 3: Production post-mortem documenting real-world failure\u002Fsuccess.\n2. **Reconciling Conflicting Findings**:\n   - When Source A says X and Source B says Not-X, identify the hidden variable: Did they test different hardware? Different compiler flags? Different network conditions?\n\n### Step 4: Structuring the Research Dossier\n1. **Standardized Dossier Structure**:\n   - Executive Summary (BLUF: Bottom Line Up Front).\n   - Core Hypotheses & Findings Matrix.\n   - Deep Evidence & Methodology Dissection.\n   - Contradictions & Caveats.\n   - Primary Source Provenance References.\n\n---\n\n## Deliverable Format: High-Trust Research Dossier\n\n```markdown\n# Research Dossier: Edge Compute Cold Starts — Wasmtime vs V8 Isolates\n\n### 1. Executive Summary (BLUF)\nWasmtime delivers a 12x faster cold-start initialization compared to V8 isolates (0.45ms vs 5.6ms), but suffers a 1.8x throughput penalty on heavy numerical compute tasks due to the lack of dynamic JIT profiling and tier-2 optimization.\n\n### 2. Empirical Triangulation Matrix\n\n| Vector | Source \u002F Provenance | Methodology \u002F Scope | Verified Finding |\n|---|---|---|---|\n| **Vector 1: Primary Telemetry** | Bytecode Alliance Wasmtime Benchmarks (v18.0) | Memory footprint per instance | Baseline idle footprint is 180KB RAM vs 18MB for Node.js V8. |\n| **Vector 2: Academic Study** | ACM SIGPLAN 2024 (Müller et al.) | 100k synthetic microservice requests | Cold start latency: 0.42ms (p50), 0.98ms (p99) on Linux x86_64. |\n| **Vector 3: Production Audit** | Fastly Lucet\u002FWasm Architecture Report | Global edge POP telemetry | 99.8% of tenant requests execute in existing pre-warmed memory instances. |\n\n### 3. Critical Contradictions & Edge Cases\n- *Discrepancy*: Several commercial serverless benchmarks claimed Wasm cold starts were 50ms.\n- *Root Cause Analysis*: Tracing the setup revealed those benchmarks included container cold start times (Docker daemon initialization), not raw WebAssembly runtime compilation.\n\n### 4. Primary Source Citations\n1. Bytecode Alliance. (2024). *Wasmtime Performance Suite*. GitHub: https:\u002F\u002Fgithub.com\u002Fbytecodealliance\u002Fwasmtime\n2. Müller, K., et al. (2024). \"Sandboxing at the Edge.\" *ACM SIGPLAN*, 42(3), 112–126.\n```\n\n---\n\n## Worked Example: Investigating an Enterprise Vendor's \"Zero Overhead\" Database Claim\n\n- **Context**: A vendor claimed their distributed database layer introduced \"zero performance overhead\" over raw NVMe disk operations.\n- **Investigation**:\n  1. Cloned the vendor's open-source benchmark repository and reviewed the configuration.\n  2. Discovered the benchmark had disabled write-ahead logging (`fsync=off`) and kept the entire test database within the 64GB OS page cache.\n  3. Reran the benchmark with persistent disk flushing (`O_DIRECT` \u002F `fsync=on`) with working set sizes exceeding RAM.\n- **Outcome**: Uncovered a 42% write latency regression under durable transaction conditions, saving the enterprise from a flawed multi-million-dollar infrastructure migration.\n\n---\n\n## Verification Checklist\n\n- [ ] Specific, falsifiable research question formulated before gathering data.\n- [ ] Source Ladder climbed to primary source code, raw data, or official specs.\n- [ ] Key claims triangulated across at least 3 independent, non-affiliated vectors.\n- [ ] Benchmark conditions audited for hidden configuration biases (e.g. caching, compute parity).\n- [ ] Conflicting data and outlier results acknowledged and reconciled.\n\n---\n\n## Anti-Patterns\n\n- **Single-Source Paraphrasing**: Relying entirely on a single corporate whitepaper or sponsored blog post to make architectural decisions.\n- **Citing Secondary Aggregators**: Citing a news article that cites a blog post that misquotes a scientific paper. Always read the original paper.\n- **Confirmation Bias Hunting**: Searching only for queries that confirm your favorite technical bias (e.g. searching only *\"Why Rust is faster than Go\"*).\n",{"name":5,"group":24,"description":7,"last_reviewed":25},"Research",1788652800000,"main","7ae884a84e46720ee4774a3d0e15b310064a9c4e","skills\u002Fresearch",0,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-education","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskillary","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp","poorvithmp.com","Shipping tools for problems people notice too late.","2026-10-02 21:32:26",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add poorvith-mp\u002Fskills-education --skill research",{"tool":42,"command":43},"bunx","bunx skills add poorvith-mp\u002Fskills-education --skill research",{"tool":45,"command":46},"pnpm","pnpm dlx skills add poorvith-mp\u002Fskills-education --skill research","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-education\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002FSKILL.md",true,[50,56],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"evals\u002Frouting.yaml","REFERENCE","参考文档",1085,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-education\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fevals\u002Frouting.yaml",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"research.skill","OTHER","其他",3957,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-education\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fresearch.skill",[63,70,77,83,90,96],{"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},"01M792EBE3X3WHX57AMJNNMGTN","training-design","Design enterprise training: needs analysis, curriculum structure, blended delivery and evaluation. Use when developing corporate workshops, course modules, or adult learning.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-education\u002Fblob\u002Fmain\u002Fskills\u002Ftraining-design\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},"01M792E6RWHNQV19CHD9WMMVSW","topic-selection","Turn a broad interest into a tractable research question or essay topic with defensible scope and available sources. Use when narrowing research questions, thesis scopes, or project ideas.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-education\u002Fblob\u002Fmain\u002Fskills\u002Ftopic-selection\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"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":80,"categories":81,"keywords":82,"publishedAt":19},"01M792E447NN2HJQAPWEKX2KNQ","study-plan","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-education\u002Fblob\u002Fmain\u002Fskills\u002Fstudy-plan\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M792E17ZWKR12JQ89MN7PK0D","study-plan-builder","Moved to modernized catalog in skillary. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-education\u002Fblob\u002Fmain\u002Fskills\u002Fstudy-plan-builder\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":86,"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},"01M792DZSR1NRRDRABT0XACRWA","study-abroad-advisor","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-education\u002Fblob\u002Fmain\u002Fskills\u002Fstudy-abroad-advisor\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M792DVAE1YB5T8DTS3B2V52J","source-evaluation","Judge whether sources carry claims: primary vs secondary, funding, method quality, and replication. Use when auditing source credibility or methodology.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-education\u002Fblob\u002Fmain\u002Fskills\u002Fsource-evaluation\u002FSKILL.md",[],[]]