[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75FYZWDMSVCXV3TZD249TSV":3,"skill-same:01M75FYZWDMSVCXV3TZD249TSV":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75FYZWDMSVCXV3TZD249TSV","analyze",null,"Run read-only deep repository analysis and return a ranked synthesis with explicit confidence, concrete file references, and clear evidence-vs-inference boundaries. Use when a user says 'analyze', 'investigate', 'why does', 'what's causing', or needs grounded cross-file explanation before any changes are proposed.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Foh-my-codex\u002Fskills\u002Fanalyze\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: analyze\ndescription: \"Run read-only deep repository analysis and return a ranked synthesis with explicit confidence, concrete file references, and clear evidence-vs-inference boundaries. Use when a user says 'analyze', 'investigate', 'why does', 'what's causing', or needs grounded cross-file explanation before any changes are proposed.\"\n---\n\n# Analyze — Read-Only Deep Analysis\n\nUse this skill to answer the user’s question through **read-only repository analysis**. The goal is to explain what the codebase most likely says about the question, not to drift into implementation, debugging theater, or generic fix planning.\n\n## Use `$analyze` when\n\n- the user wants a grounded explanation, not code changes\n- the answer requires reading multiple files or tracing behavior across boundaries\n- there are several plausible explanations and they need to be ranked\n- confidence should reflect the strength of the available evidence\n- the user wants to understand architecture, behavior, causality, impact, or tradeoffs before changing anything\n\nExamples:\n- why a workflow behaves a certain way\n- how a feature is wired across modules\n- what likely explains a failure, regression, or mismatch\n- what would be impacted by changing a dependency or contract\n- which interpretation of the current codebase is best supported\n\n## Do not use `$analyze` when\n\n- the user explicitly wants code edits, a fix, or execution — use the appropriate implementation lane instead\n- the user wants a new product plan or acceptance criteria — use `$plan` \u002F `$ralplan`\n- the request is a simple one-file fact lookup — read the file and answer directly\n- the request is purely about running the OMX tmux team runtime — use `$team` only when OMX runtime is active\n\n## Non-negotiable contract\n\nAnalyze is **read-only by contract**.\n\n- Do not edit files.\n- Do not turn the answer into an implementation plan.\n- Do not recommend fixes as the primary output.\n- Do not silently switch into execution work.\n- Do not overclaim certainty.\n- Do not invent facts that are not supported by repository evidence.\n- Do not use judgmental, normative, or speculative language that outruns the evidence.\n\nIf a next step is helpful, keep it to a **discriminating read-only probe** that would reduce uncertainty.\n\n## Question-aligned synthesis\n\nAnswer the user’s actual question first.\n\n- Start from the asked question, not a generic debugger template.\n- Keep the synthesis scoped to what the user needs to know.\n- Scale the depth to the request: for simple or obvious questions, reduce swarm intensity and answer directly after enough reading.\n- For broader questions, expand the search surface but keep the final answer tightly synthesized.\n\n## Evidence rules\n\nMaintain an explicit **evidence-vs-inference distinction**. Every material claim must be labeled as one of:\n\n1. **Evidence** — directly supported by concrete repository artifacts\n2. **Inference** — a reasoned conclusion drawn from evidence\n3. **Unknown** — a question the current repository evidence does not resolve\n\nNever present an inference as if it were direct evidence.\nNever present a guess as if it were an inference.\nCall out uncertainty explicitly when the codebase does not settle the question.\n\n### Acceptable evidence\n\nPrefer stronger evidence over weaker evidence:\n\n1. direct code paths, contracts, tests, generated artifacts, configs, or docs with concrete file references\n2. multiple independent files pointing to the same conclusion\n3. localized behavioral inference from well-supported code structure\n4. weaker contextual clues that remain explicitly marked as tentative\n\nUnsupported speculation is not evidence.\n\n## Parallel exploration policy\n\nParallel exploration is allowed when it improves quality, but it must stay runtime-safe.\n\n- Default to direct read-only analysis when the answer is simple.\n- When parallelism helps, prefer **native subagents by default** or equivalent in-session parallel exploration when available.\n- Keep parallel lanes bounded: each lane should answer a concrete sub-question or inspect a specific subsystem.\n- Use **`$team` only when OMX runtime is active** and durable tmux-based coordination is actually needed.\n- Do not imply that `$team` is available in plain Codex\u002FApp sessions.\n\nA good default split for complex analysis is:\n- one lane for primary code path \u002F contracts\n- one lane for config \u002F orchestration \u002F generated surfaces\n- one lane for tests \u002F docs \u002F secondary corroboration\n\n## Execution policy\n\n- Default to concise, evidence-dense progress and completion reporting unless the user or risk level requires more detail.\n- Treat newer user task updates as local overrides for the active workflow branch while preserving earlier non-conflicting constraints.\n- If the user says `continue`, keep working from the current analysis state instead of restarting discovery.\n\n## Working method\n\n1. Restate the question in one sentence.\n2. Identify the smallest set of files most likely to answer it.\n3. Read for direct evidence first.\n4. If needed, open bounded parallel exploration lanes.\n5. Compare competing explanations.\n6. Rank the explanations by support.\n7. Return a synthesis that clearly separates evidence from inference.\n\n## Output contract\n\nStructure the answer so the user can see what is known, what is inferred, and how confident the synthesis is.\n\n### Question\n[Restate the user’s question briefly]\n\n### Ranked synthesis\n| Rank | Explanation | Confidence | Basis |\n|------|-------------|------------|-------|\n| 1 | ... | High \u002F Medium \u002F Low | strongest supporting evidence |\n| 2 | ... | High \u002F Medium \u002F Low | why it trails |\n| 3 | ... | High \u002F Medium \u002F Low | why it remains possible |\n\n### Evidence\n- `path\u002Fto\u002Ffile:line-line` — what this artifact directly shows\n- `path\u002Fto\u002Ffile:line-line` — corroborating evidence\n\n### Inference\n- What the evidence most strongly implies\n- Why weaker alternatives were down-ranked\n\n### Unknowns \u002F limits\n- What the repository evidence does not establish\n- What would need to be checked next to reduce uncertainty\n\n## Quality bar\n\nA good analyze response is:\n- read-only and question-aligned\n- ranked rather than flat\n- explicit about confidence\n- concrete about file references\n- careful about evidence vs inference\n- free of unsupported speculation\n- free of normative drift or judgmental filler\n- explicit about the evidence-vs-inference distinction\n- concise for simple cases, broader only when the question truly needs it\n\nTask: {{ARGUMENTS}}\n","# Analyze — Read-Only Deep Analysis\n\nUse this skill to answer the user’s question through **read-only repository analysis**. The goal is to explain what the codebase most likely says about the question, not to drift into implementation, debugging theater, or generic fix planning.\n\n## Use `$analyze` when\n\n- the user wants a grounded explanation, not code changes\n- the answer requires reading multiple files or tracing behavior across boundaries\n- there are several plausible explanations and they need to be ranked\n- confidence should reflect the strength of the available evidence\n- the user wants to understand architecture, behavior, causality, impact, or tradeoffs before changing anything\n\nExamples:\n- why a workflow behaves a certain way\n- how a feature is wired across modules\n- what likely explains a failure, regression, or mismatch\n- what would be impacted by changing a dependency or contract\n- which interpretation of the current codebase is best supported\n\n## Do not use `$analyze` when\n\n- the user explicitly wants code edits, a fix, or execution — use the appropriate implementation lane instead\n- the user wants a new product plan or acceptance criteria — use `$plan` \u002F `$ralplan`\n- the request is a simple one-file fact lookup — read the file and answer directly\n- the request is purely about running the OMX tmux team runtime — use `$team` only when OMX runtime is active\n\n## Non-negotiable contract\n\nAnalyze is **read-only by contract**.\n\n- Do not edit files.\n- Do not turn the answer into an implementation plan.\n- Do not recommend fixes as the primary output.\n- Do not silently switch into execution work.\n- Do not overclaim certainty.\n- Do not invent facts that are not supported by repository evidence.\n- Do not use judgmental, normative, or speculative language that outruns the evidence.\n\nIf a next step is helpful, keep it to a **discriminating read-only probe** that would reduce uncertainty.\n\n## Question-aligned synthesis\n\nAnswer the user’s actual question first.\n\n- Start from the asked question, not a generic debugger template.\n- Keep the synthesis scoped to what the user needs to know.\n- Scale the depth to the request: for simple or obvious questions, reduce swarm intensity and answer directly after enough reading.\n- For broader questions, expand the search surface but keep the final answer tightly synthesized.\n\n## Evidence rules\n\nMaintain an explicit **evidence-vs-inference distinction**. Every material claim must be labeled as one of:\n\n1. **Evidence** — directly supported by concrete repository artifacts\n2. **Inference** — a reasoned conclusion drawn from evidence\n3. **Unknown** — a question the current repository evidence does not resolve\n\nNever present an inference as if it were direct evidence.\nNever present a guess as if it were an inference.\nCall out uncertainty explicitly when the codebase does not settle the question.\n\n### Acceptable evidence\n\nPrefer stronger evidence over weaker evidence:\n\n1. direct code paths, contracts, tests, generated artifacts, configs, or docs with concrete file references\n2. multiple independent files pointing to the same conclusion\n3. localized behavioral inference from well-supported code structure\n4. weaker contextual clues that remain explicitly marked as tentative\n\nUnsupported speculation is not evidence.\n\n## Parallel exploration policy\n\nParallel exploration is allowed when it improves quality, but it must stay runtime-safe.\n\n- Default to direct read-only analysis when the answer is simple.\n- When parallelism helps, prefer **native subagents by default** or equivalent in-session parallel exploration when available.\n- Keep parallel lanes bounded: each lane should answer a concrete sub-question or inspect a specific subsystem.\n- Use **`$team` only when OMX runtime is active** and durable tmux-based coordination is actually needed.\n- Do not imply that `$team` is available in plain Codex\u002FApp sessions.\n\nA good default split for complex analysis is:\n- one lane for primary code path \u002F contracts\n- one lane for config \u002F orchestration \u002F generated surfaces\n- one lane for tests \u002F docs \u002F secondary corroboration\n\n## Execution policy\n\n- Default to concise, evidence-dense progress and completion reporting unless the user or risk level requires more detail.\n- Treat newer user task updates as local overrides for the active workflow branch while preserving earlier non-conflicting constraints.\n- If the user says `continue`, keep working from the current analysis state instead of restarting discovery.\n\n## Working method\n\n1. Restate the question in one sentence.\n2. Identify the smallest set of files most likely to answer it.\n3. Read for direct evidence first.\n4. If needed, open bounded parallel exploration lanes.\n5. Compare competing explanations.\n6. Rank the explanations by support.\n7. Return a synthesis that clearly separates evidence from inference.\n\n## Output contract\n\nStructure the answer so the user can see what is known, what is inferred, and how confident the synthesis is.\n\n### Question\n[Restate the user’s question briefly]\n\n### Ranked synthesis\n| Rank | Explanation | Confidence | Basis |\n|------|-------------|------------|-------|\n| 1 | ... | High \u002F Medium \u002F Low | strongest supporting evidence |\n| 2 | ... | High \u002F Medium \u002F Low | why it trails |\n| 3 | ... | High \u002F Medium \u002F Low | why it remains possible |\n\n### Evidence\n- `path\u002Fto\u002Ffile:line-line` — what this artifact directly shows\n- `path\u002Fto\u002Ffile:line-line` — corroborating evidence\n\n### Inference\n- What the evidence most strongly implies\n- Why weaker alternatives were down-ranked\n\n### Unknowns \u002F limits\n- What the repository evidence does not establish\n- What would need to be checked next to reduce uncertainty\n\n## Quality bar\n\nA good analyze response is:\n- read-only and question-aligned\n- ranked rather than flat\n- explicit about confidence\n- concrete about file references\n- careful about evidence vs inference\n- free of unsupported speculation\n- free of normative drift or judgmental filler\n- explicit about the evidence-vs-inference distinction\n- concise for simple cases, broader only when the question truly needs it\n\nTask: {{ARGUMENTS}}\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Foh-my-codex\u002Fskills\u002Fanalyze",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill analyze",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill analyze",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill analyze","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Foh-my-codex\u002Fskills\u002Fanalyze\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]