[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75BMK8PQ7KEXFPQ99S1AXN6":3,"skill-same:01M75BMK8PQ7KEXFPQ99S1AXN6":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},"01M75BMK8PQ7KEXFPQ99S1AXN6","analysis-artifacts",null,"Generate reproducible analysis artifacts — SQL queries, Python visualizations, and summary tables — as you work through a BigQuery data analysis. Use when asked to conduct a deep dive, exploratory analysis, or investigation that goes beyond a simple data lookup.","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\u002Fanalysis-artifacts\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: analysis-artifacts\ndescription: Generate reproducible analysis artifacts — SQL queries, Python visualizations, and summary tables — as you work through a BigQuery data analysis. Use when asked to conduct a deep dive, exploratory analysis, or investigation that goes beyond a simple data lookup.\n---\n\n# Analysis Artifacts\n\n## When to Use\n\n- When asked to do a \"deep dive\" or \"analysis\" on a question with a non-obvious answer\n- When the analysis requires exploratory querying in BigQuery\n- When the output should be reproducible and shareable (not just a one-off answer)\n\n## Workflow\n\n### 1. Scaffold the analysis directory\n\nAt the start of every analysis:\n\n- Create a new directory in the `analyses` folder, named according to the existing pattern there\n- Create subdirectories: `\u002Fassets\u002Fqueries` and `\u002Fassets\u002Fvisualizations`\n- Create a `README.md` at the root of the new directory — this is the main readable document for the analysis\n\n### 2. Plan the analysis\n\nAlways create a plan before starting, whether or not the user asked for one. Steps in the plan should map to the logical sub-questions or sub-areas you've deemed important to explore. Present the plan and wait for a go-ahead before proceeding.\n\n### 3. Set up the README\n\nOnce the plan is approved:\n\n- Add a title, author, and date to the top of the README\n- Add a **Problem Statement** section summarizing the analysis question and the sub-pieces you'll explore\n- Add a **Cohorts Definition** section. This must be extremely explicit about the groups being compared. If comparing two groups (e.g., free vs. paid, new vs. old, before vs. after a milestone), define cohorts in a way that controls for confounding factors. Consider:\n  - Signup\u002Factivation time (as defined by your product — e.g., first login, first meaningful action); this relates to user tenure\n  - Plan type or subscription tier (e.g., free vs. paid)\n  - Controlling for observation time window length across cohorts\n  - Product-specific usage propensity metrics relevant to the analysis question\n\n  Once defined, respect these cohort definitions in all queries throughout the analysis.\n\n### 4. Create artifacts as you go\n\nFor every material step in the analysis:\n\n- **SQL query artifact**: For any BigQuery query that powers a visualization, summary, or key insight, save a `.sql` file in `\u002Fassets\u002Fqueries\u002F` with a descriptive name and a comment block explaining the query's purpose. Only create the file after you're satisfied with the results. Skip trivial or one-off lookup queries.\n- **Visualization or table artifact**: For each key insight, assess whether it's best conveyed through a chart or a table. Lean toward visualizations. If a visualization, write a Python script to generate it and save both the script and the output image to `\u002Fassets\u002Fvisualizations\u002F` with descriptive names. If a table, save it as a `.csv` in `\u002Fassets\u002Fvisualizations\u002F`.\n\n### 5. Overwriting artifacts\n\nIf you need to redo part of the analysis (due to a methodology correction or user feedback), overwrite all associated artifacts:\n\n- Replace the `.sql` query file\n- Replace the visualization script and regenerate the image\n- Replace the `.csv` table file\n\nNote the change to the user when you do this.\n\n### 6. Summarize the analysis\n\nWhen the analysis is complete (either at the end of the plan or when the user asks), write the full README:\n\n- Summarize each step and sub-question in logical document sections\n- Be crisp and concise — avoid unnecessary verbosity\n- Embed saved viz images from `\u002Fassets\u002Fvisualizations\u002F` where appropriate\n- Generate markdown tables from `.csv` files in `\u002Fassets\u002Fvisualizations\u002F`\n- Include a small reference hyperlink to the associated query file in each section\n- Add a **TL;DR** section near the top (after Problem Statement, before Cohorts Definition)\n- Add a **Key Takeaways** section at the end\n\n## Examples\n\n```bash\nanalyses\u002F\n└── 2024-01-user-retention\u002F\n    ├── README.md\n    └── assets\u002F\n        ├── queries\u002F\n        │   ├── cohort_retention_by_week.sql\n        │   └── retention_by_plan_type.sql\n        └── visualizations\u002F\n            ├── retention_curve.py\n            ├── retention_curve.png\n            └── plan_type_summary.csv\n```\n","# Analysis Artifacts\n\n## When to Use\n\n- When asked to do a \"deep dive\" or \"analysis\" on a question with a non-obvious answer\n- When the analysis requires exploratory querying in BigQuery\n- When the output should be reproducible and shareable (not just a one-off answer)\n\n## Workflow\n\n### 1. Scaffold the analysis directory\n\nAt the start of every analysis:\n\n- Create a new directory in the `analyses` folder, named according to the existing pattern there\n- Create subdirectories: `\u002Fassets\u002Fqueries` and `\u002Fassets\u002Fvisualizations`\n- Create a `README.md` at the root of the new directory — this is the main readable document for the analysis\n\n### 2. Plan the analysis\n\nAlways create a plan before starting, whether or not the user asked for one. Steps in the plan should map to the logical sub-questions or sub-areas you've deemed important to explore. Present the plan and wait for a go-ahead before proceeding.\n\n### 3. Set up the README\n\nOnce the plan is approved:\n\n- Add a title, author, and date to the top of the README\n- Add a **Problem Statement** section summarizing the analysis question and the sub-pieces you'll explore\n- Add a **Cohorts Definition** section. This must be extremely explicit about the groups being compared. If comparing two groups (e.g., free vs. paid, new vs. old, before vs. after a milestone), define cohorts in a way that controls for confounding factors. Consider:\n  - Signup\u002Factivation time (as defined by your product — e.g., first login, first meaningful action); this relates to user tenure\n  - Plan type or subscription tier (e.g., free vs. paid)\n  - Controlling for observation time window length across cohorts\n  - Product-specific usage propensity metrics relevant to the analysis question\n\n  Once defined, respect these cohort definitions in all queries throughout the analysis.\n\n### 4. Create artifacts as you go\n\nFor every material step in the analysis:\n\n- **SQL query artifact**: For any BigQuery query that powers a visualization, summary, or key insight, save a `.sql` file in `\u002Fassets\u002Fqueries\u002F` with a descriptive name and a comment block explaining the query's purpose. Only create the file after you're satisfied with the results. Skip trivial or one-off lookup queries.\n- **Visualization or table artifact**: For each key insight, assess whether it's best conveyed through a chart or a table. Lean toward visualizations. If a visualization, write a Python script to generate it and save both the script and the output image to `\u002Fassets\u002Fvisualizations\u002F` with descriptive names. If a table, save it as a `.csv` in `\u002Fassets\u002Fvisualizations\u002F`.\n\n### 5. Overwriting artifacts\n\nIf you need to redo part of the analysis (due to a methodology correction or user feedback), overwrite all associated artifacts:\n\n- Replace the `.sql` query file\n- Replace the visualization script and regenerate the image\n- Replace the `.csv` table file\n\nNote the change to the user when you do this.\n\n### 6. Summarize the analysis\n\nWhen the analysis is complete (either at the end of the plan or when the user asks), write the full README:\n\n- Summarize each step and sub-question in logical document sections\n- Be crisp and concise — avoid unnecessary verbosity\n- Embed saved viz images from `\u002Fassets\u002Fvisualizations\u002F` where appropriate\n- Generate markdown tables from `.csv` files in `\u002Fassets\u002Fvisualizations\u002F`\n- Include a small reference hyperlink to the associated query file in each section\n- Add a **TL;DR** section near the top (after Problem Statement, before Cohorts Definition)\n- Add a **Key Takeaways** section at the end\n\n## Examples\n\n```bash\nanalyses\u002F\n└── 2024-01-user-retention\u002F\n    ├── README.md\n    └── assets\u002F\n        ├── queries\u002F\n        │   ├── cohort_retention_by_week.sql\n        │   └── retention_by_plan_type.sql\n        └── visualizations\u002F\n            ├── retention_curve.py\n            ├── retention_curve.png\n            └── plan_type_summary.csv\n```\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fanalysis-artifacts",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 analysis-artifacts",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill analysis-artifacts",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill analysis-artifacts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fanalysis-artifacts\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",[],[]]