[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DB5FDQ6AFWBS6VM67VPZAT":3,"skill-same:01M7DB5FDQ6AFWBS6VM67VPZAT":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7DB5FDQ6AFWBS6VM67VPZAT","research-rigor",null,"alicewe1\u002Falice_skill","alicewe1","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F102134151?v=4","01M7D9STCM8HAESM958JP0989K","Alice_we","01M7D9STDR22MTD9FTTWPAZNV8",64,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fresearch-rigor\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: game-security-research-rigor\ndescription: Guide for evidence-grounded game-security research, citation verification, uncertainty, reproducible analysis, and detector evaluation. Use when validating technical claims, synthesizing README or wiki resources, comparing security techniques, assessing telemetry or models, or deciding whether evidence supports an anti-cheat conclusion.\nx-alice-class: reverse\n---# Game Security Research Rigor\n\n## Purpose\n\nUse this skill with the relevant domain skill. Its job is to keep conclusions\nno stronger than the evidence and to make factual, empirical, and operational\nclaims independently checkable.\n\n## Separate the reasoning layers\n\nNever collapse these layers:\n\n1. **Observation** — the raw artifact or measurement.\n2. **Finding** — a rule, baseline, or invariant was violated.\n3. **Attribution** — a hypothesis about cause or actor intent.\n4. **Decision** — a risk-based response to the supported conclusion.\n\nAn anomaly, hash mismatch, or invariant violation establishes a finding only\nunder the stated measurement assumptions. It does not by itself prove cheating,\nmalicious intent, or the responsible actor.\n\n## Research workflow\n\n1. **Scope the question**\n   - Identify object, platform, game\u002Fbuild, mode, timeframe, trust boundaries,\n     available evidence, and the consequence of a wrong conclusion.\n   - State what is outside scope.\n2. **Acquire evidence**\n   - Prefer primary artifacts for version-specific behavior: source code,\n     specifications, raw telemetry, traces, binaries, and official changelogs.\n   - Use peer-reviewed or independently reproduced work for generalization.\n   - Treat vendor posts and community reports as claim-bearing sources, not\n     automatic proof.\n3. **Verify every citation**\n   - Confirm the URL or DOI resolves.\n   - Match title, authors, venue, and year to authoritative metadata.\n   - Read enough of the source to confirm it supports the exact claim.\n   - A venue name, search result, bibliography entry, or source count is not\n     evidence by itself.\n4. **Build a claim ledger**\n   - Record claim, supporting artifact, source\u002Fversion\u002Fdate, method, assumptions,\n     counterevidence, uncertainty, and remaining verification work.\n   - Label statements as observed, reproduced, sourced, inferred, or unknown.\n5. **Test alternatives**\n   - Look for benign explanations, measurement error, stale schemas, version\n     drift, selection bias, and contradictory evidence.\n6. **Reproduce and validate**\n   - Preserve inputs, transforms, tool\u002Fmodel versions, configuration, timestamps,\n     and commands needed to reproduce the result.\n   - Re-run against negative controls and changed conditions.\n7. **Conclude narrowly**\n   - Use one of: supported, suspicious, no signal observed within scope, or\n     inconclusive.\n   - Never turn missing data into a clean result.\n\n## Detector and telemetry evaluation\n\n- Do not copy universal thresholds across games or populations. Calibrate for\n  the title, build, mode, rank, input method, platform, region, and telemetry\n  pipeline where the detector will operate.\n- Split evaluation data by player\u002Fsession and, where appropriate, by time.\n  Prevent the same player or near-duplicate session from leaking across train,\n  calibration, and test sets.\n- Include representative legitimate users, top-skill players, accessibility\n  tools, unusual hardware, and controlled or independently adjudicated positive\n  cases.\n- Report prevalence and a confusion matrix with uncertainty: false-positive\n  rate, false-negative rate, precision\u002Fpositive predictive value, recall, and\n  calibration. Use PR-oriented metrics for rare events.\n- Evaluate the deployed decision volume, not only per-event error rates. A small\n  per-test false-positive rate can still create many false alerts when applied\n  repeatedly across large populations, time windows, features, or models.\n  Report expected alert and review counts; control repeated-testing and\n  false-discovery effects where applicable.\n- A score in `[0, 1]` is not a probability or calibrated confidence unless this\n  interpretation has been validated on held-out representative data.\n- Derive minimum sample requirements empirically. Round numbers such as 40 or 50\n  samples are not general stability guarantees.\n- Model signal dependence. Taking the maximum score or counting several\n  correlated signals does not guarantee corroboration or a lower joint\n  false-positive rate.\n- Revalidate after patches, balance changes, input changes, and population\n  drift. Version thresholds, features, models, and schemas.\n- Document label origin, adjudication criteria, reviewer disagreement, and\n  uncertainty. Separate controlled positives from suspected cases; check\n  training and evaluation data for contamination, duplication, and poisoning.\n\n## Invariant checks\n\nBefore treating an invariant violation as strong evidence:\n\n1. Confirm the invariant is actually guaranteed for that state and build.\n2. Confirm the observation came from an authoritative, correctly ordered source.\n3. Exclude replication delay, rollback, retries, reconnects, transitions,\n   administrator\u002Ftest paths, legitimate teleports or grants, schema errors,\n   stale baselines, and game bugs.\n4. Distinguish a state-integrity violation from attribution of exploitation.\n\nAn invariant can justify containment or investigation sooner than a soft\nbehavioral anomaly, but attribution and punitive action still require evidence\nappropriate to their impact.\n\n## Data and decision governance\n\n- Collect only telemetry needed for a declared detection purpose. Define field\n  ownership, access controls, retention, deletion, and incident-response rules.\n- Prefer pseudonymous identifiers in analysis data and keep re-identification\n  material separately protected. Do not place secrets or unnecessary personal\n  data in evidence logs.\n- Protect evidence integrity with immutable references, hashes where useful,\n  schema validation, ordering information, and an auditable access trail.\n- Evaluate performance for relevant populations and legitimate edge cases,\n  including accessibility tools and unusual hardware, without assuming that a\n  population difference implies abuse.\n- Keep detector output separate from enforcement policy. Record who or what made\n  the final decision, preserve counterevidence, and make consequential outcomes\n  reviewable and appealable.\n\n## Quality gates\n\n- **Scope:** versions, trust boundaries, and decision stakes are explicit.\n- **Identity:** citation metadata and source identity were verified.\n- **Support:** each material claim is supported by the cited content.\n- **Alternatives:** plausible benign causes and contradictory evidence were\n  considered.\n- **Validity:** empirical claims include representative evaluation and suitable\n  metrics.\n- **Reproducibility:** inputs, configuration, and transformations are traceable.\n- **Calibration:** conclusion wording matches evidence strength and scope.\n- **Action:** response is proportional, reviewable, and preserves an appeal path\n  for consequential enforcement.\n\nIf a gate fails, narrow the claim or return inconclusive. Never auto-fill a\nmissing source, fabricate a citation, or raise confidence to satisfy a template.\n\n## What tests establish\n\n- Unit and fixture tests establish implementation behavior.\n- Calibration tests establish an operating threshold on a defined population.\n- Held-out, temporal, and external tests assess generalization.\n- Shadow\u002Fcanary monitoring assesses production drift and operational impact.\n\nA green suite built from hand-authored threshold-triggering fixtures does not\nestablish detector validity, low false-positive rates, or production readiness.\n\n## Source roles\n\n| Source | Strongest appropriate use | Main limitation |\n|---|---|---|\n| Primary artifact or raw trace | What this exact version did | May be incomplete or untrusted |\n| Official specification\u002Fdocumentation | Intended behavior and interfaces | May omit implementation details |\n| Peer-reviewed study | Evidence under its study design | External validity may be limited |\n| Independent reproduction | Corroboration and failure discovery | Often version-specific |\n| Vendor\u002Fcommunity report | Leads and operational context | Bias and unverifiable details |\n\nDo not assign a universal quality tier solely from publication venue or source\ntype. Judge authority, directness, methodology, independence, recency, and\nclaim fit separately.\n","## Purpose\n\nUse this skill with the relevant domain skill. Its job is to keep conclusions\nno stronger than the evidence and to make factual, empirical, and operational\nclaims independently checkable.\n\n## Separate the reasoning layers\n\nNever collapse these layers:\n\n1. **Observation** — the raw artifact or measurement.\n2. **Finding** — a rule, baseline, or invariant was violated.\n3. **Attribution** — a hypothesis about cause or actor intent.\n4. **Decision** — a risk-based response to the supported conclusion.\n\nAn anomaly, hash mismatch, or invariant violation establishes a finding only\nunder the stated measurement assumptions. It does not by itself prove cheating,\nmalicious intent, or the responsible actor.\n\n## Research workflow\n\n1. **Scope the question**\n   - Identify object, platform, game\u002Fbuild, mode, timeframe, trust boundaries,\n     available evidence, and the consequence of a wrong conclusion.\n   - State what is outside scope.\n2. **Acquire evidence**\n   - Prefer primary artifacts for version-specific behavior: source code,\n     specifications, raw telemetry, traces, binaries, and official changelogs.\n   - Use peer-reviewed or independently reproduced work for generalization.\n   - Treat vendor posts and community reports as claim-bearing sources, not\n     automatic proof.\n3. **Verify every citation**\n   - Confirm the URL or DOI resolves.\n   - Match title, authors, venue, and year to authoritative metadata.\n   - Read enough of the source to confirm it supports the exact claim.\n   - A venue name, search result, bibliography entry, or source count is not\n     evidence by itself.\n4. **Build a claim ledger**\n   - Record claim, supporting artifact, source\u002Fversion\u002Fdate, method, assumptions,\n     counterevidence, uncertainty, and remaining verification work.\n   - Label statements as observed, reproduced, sourced, inferred, or unknown.\n5. **Test alternatives**\n   - Look for benign explanations, measurement error, stale schemas, version\n     drift, selection bias, and contradictory evidence.\n6. **Reproduce and validate**\n   - Preserve inputs, transforms, tool\u002Fmodel versions, configuration, timestamps,\n     and commands needed to reproduce the result.\n   - Re-run against negative controls and changed conditions.\n7. **Conclude narrowly**\n   - Use one of: supported, suspicious, no signal observed within scope, or\n     inconclusive.\n   - Never turn missing data into a clean result.\n\n## Detector and telemetry evaluation\n\n- Do not copy universal thresholds across games or populations. Calibrate for\n  the title, build, mode, rank, input method, platform, region, and telemetry\n  pipeline where the detector will operate.\n- Split evaluation data by player\u002Fsession and, where appropriate, by time.\n  Prevent the same player or near-duplicate session from leaking across train,\n  calibration, and test sets.\n- Include representative legitimate users, top-skill players, accessibility\n  tools, unusual hardware, and controlled or independently adjudicated positive\n  cases.\n- Report prevalence and a confusion matrix with uncertainty: false-positive\n  rate, false-negative rate, precision\u002Fpositive predictive value, recall, and\n  calibration. Use PR-oriented metrics for rare events.\n- Evaluate the deployed decision volume, not only per-event error rates. A small\n  per-test false-positive rate can still create many false alerts when applied\n  repeatedly across large populations, time windows, features, or models.\n  Report expected alert and review counts; control repeated-testing and\n  false-discovery effects where applicable.\n- A score in `[0, 1]` is not a probability or calibrated confidence unless this\n  interpretation has been validated on held-out representative data.\n- Derive minimum sample requirements empirically. Round numbers such as 40 or 50\n  samples are not general stability guarantees.\n- Model signal dependence. Taking the maximum score or counting several\n  correlated signals does not guarantee corroboration or a lower joint\n  false-positive rate.\n- Revalidate after patches, balance changes, input changes, and population\n  drift. Version thresholds, features, models, and schemas.\n- Document label origin, adjudication criteria, reviewer disagreement, and\n  uncertainty. Separate controlled positives from suspected cases; check\n  training and evaluation data for contamination, duplication, and poisoning.\n\n## Invariant checks\n\nBefore treating an invariant violation as strong evidence:\n\n1. Confirm the invariant is actually guaranteed for that state and build.\n2. Confirm the observation came from an authoritative, correctly ordered source.\n3. Exclude replication delay, rollback, retries, reconnects, transitions,\n   administrator\u002Ftest paths, legitimate teleports or grants, schema errors,\n   stale baselines, and game bugs.\n4. Distinguish a state-integrity violation from attribution of exploitation.\n\nAn invariant can justify containment or investigation sooner than a soft\nbehavioral anomaly, but attribution and punitive action still require evidence\nappropriate to their impact.\n\n## Data and decision governance\n\n- Collect only telemetry needed for a declared detection purpose. Define field\n  ownership, access controls, retention, deletion, and incident-response rules.\n- Prefer pseudonymous identifiers in analysis data and keep re-identification\n  material separately protected. Do not place secrets or unnecessary personal\n  data in evidence logs.\n- Protect evidence integrity with immutable references, hashes where useful,\n  schema validation, ordering information, and an auditable access trail.\n- Evaluate performance for relevant populations and legitimate edge cases,\n  including accessibility tools and unusual hardware, without assuming that a\n  population difference implies abuse.\n- Keep detector output separate from enforcement policy. Record who or what made\n  the final decision, preserve counterevidence, and make consequential outcomes\n  reviewable and appealable.\n\n## Quality gates\n\n- **Scope:** versions, trust boundaries, and decision stakes are explicit.\n- **Identity:** citation metadata and source identity were verified.\n- **Support:** each material claim is supported by the cited content.\n- **Alternatives:** plausible benign causes and contradictory evidence were\n  considered.\n- **Validity:** empirical claims include representative evaluation and suitable\n  metrics.\n- **Reproducibility:** inputs, configuration, and transformations are traceable.\n- **Calibration:** conclusion wording matches evidence strength and scope.\n- **Action:** response is proportional, reviewable, and preserves an appeal path\n  for consequential enforcement.\n\nIf a gate fails, narrow the claim or return inconclusive. Never auto-fill a\nmissing source, fabricate a citation, or raise confidence to satisfy a template.\n\n## What tests establish\n\n- Unit and fixture tests establish implementation behavior.\n- Calibration tests establish an operating threshold on a defined population.\n- Held-out, temporal, and external tests assess generalization.\n- Shadow\u002Fcanary monitoring assesses production drift and operational impact.\n\nA green suite built from hand-authored threshold-triggering fixtures does not\nestablish detector validity, low false-positive rates, or production readiness.\n\n## Source roles\n\n| Source | Strongest appropriate use | Main limitation |\n|---|---|---|\n| Primary artifact or raw trace | What this exact version did | May be incomplete or untrusted |\n| Official specification\u002Fdocumentation | Intended behavior and interfaces | May omit implementation details |\n| Peer-reviewed study | Evidence under its study design | External validity may be limited |\n| Independent reproduction | Corroboration and failure discovery | Often version-specific |\n| Vendor\u002Fcommunity report | Leads and operational context | Bias and unverifiable details |\n\nDo not assign a universal quality tier solely from publication venue or source\ntype. Judge authority, directness, methodology, independence, recency, and\nclaim fit separately.\n",{},"main","19a54ac988e9929160334271f5c1924ddd9b227e","_modules\u002Fresearch-rigor",19,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill","https:\u002F\u002Fgithub.com\u002Falicewe1","写一些自己用得上的工具，能自动化就绝不手动 · 自动化 \u002F 工程效率 \u002F Agent 技能生态 · 保持好奇，持续构建","2026-09-30 00:41:20",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add alicewe1\u002Falice_skill --skill research-rigor",{"tool":37,"command":38},"bunx","bunx skills add alicewe1\u002Falice_skill --skill research-rigor",{"tool":40,"command":41},"pnpm","pnpm dlx skills add alicewe1\u002Falice_skill --skill research-rigor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fresearch-rigor\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7DBMD9P6R27SWQCW5HYVWG0","alice","Alice 六类技能总路由。用户输入 Alice 或要求查看 Alice 技能菜单时，严格输出固定菜单；输入攻\u002F防模式、六类入口或直接描述任务时，按类别→领域→模块渐进路由。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Faliceskill\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M7DBM8X5M7YXPYBVFMWF8HRC","alice-reverse","逆向分析渐进路由（二进制 \u002F 移动端 \u002F 协议 \u002F 取证 \u002F 保护机制 \u002F 运行时观测）。触发词：二进制\u002F移动端\u002F反编译\u002FFrida\u002FIDA\u002FGhidra\u002FPE\u002FELF\u002FAPK\u002F协议\u002F取证；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-reverse\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7DBM630E2YKQP29194TT7HC","alice-pentest","web安全渐进路由（Web \u002F API \u002F 资产发现 \u002F 漏洞验证 \u002F 云与网络安全）。触发词：Web\u002FAPI\u002F资产发现\u002F端口\u002F漏洞验证\u002F云与网络安全；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-pentest\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7DBM20M2VDYV5D3MYDGBTQX","alice-game","游戏攻防渐进路由（游戏客户端 \u002F 内存 \u002F 图形 \u002F 反作弊 \u002F 安全研究）。触发词：游戏客户端\u002F内存\u002F图形\u002F偏移\u002F反作弊\u002F模拟器\u002F覆盖层；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-game\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7DBKXVEKB8931MZG23VACFN","alice-crack","卡密授权渐进路由（卡密 \u002F 激活 \u002F 授权验证 \u002F 许可证管理 \u002F 本地授权分析）。触发词：卡密\u002F激活\u002F授权验证\u002Flicense\u002F机器码\u002F试用状态；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-crack\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7DBKTMT90MGV2WP8K73TMQD","alice-assist","技能指令渐进路由（技能路由 \u002F 评分 \u002F 吸收 \u002F 迁移 \u002F 自动化 \u002F 文档与平台集成）。触发词：技能创建\u002F吸收\u002F评分\u002F迁移\u002F自动化\u002F文档\u002F平台指令；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-assist\u002FSKILL.md",[],[]]