[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75CRYTYNEQTYYAK680SF341":3,"skill-same:01M75CRYTYNEQTYYAK680SF341":48},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M75CRYTYNEQTYYAK680SF341","customize",null,"Guided customization of your AI governance practice profile — change one thing without re-running the whole cold-start interview. Adjust risk posture, escalation contacts, use-case registry entries, vendor AI positions, AI policy commitments, impact-assessment house style, or matter workspace paths. Use when the user says \"change my [thing]\", \"update my profile\", \"edit my config\", \"tune my playbook\", or \"customize\".","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\u002Fcustomize\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: customize\ndescription: >\n  Guided customization of your AI governance practice profile — change one thing\n  without re-running the whole cold-start interview. Adjust risk posture,\n  escalation contacts, use-case registry entries, vendor AI positions,\n  AI policy commitments, impact-assessment house style, or matter workspace\n  paths. Use when the user says \"change my [thing]\", \"update my profile\",\n  \"edit my config\", \"tune my playbook\", or \"customize\".\nargument-hint: \"[section name, or describe what you want to change]\"\n---\n\n# \u002Fcustomize\n\n## When this runs\n\nThe user typed `\u002Fai-governance-legal:customize`. They want to change something\nin their practice profile — a risk posture, an escalation contact, a playbook\nposition, a jurisdiction, an output format — without re-running the whole\ncold-start interview and without hand-editing YAML.\n\n## What to do\n\n1. **Read the config.** Read\n   `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fai-governance-legal\u002FCLAUDE.md`\n   (and `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcompany-profile.md` one\n   level up). If the plugin config does not exist or still contains\n   `[PLACEHOLDER]` values, say:\n\n   > You haven't run setup yet. Run `\u002Fai-governance-legal:cold-start-interview`\n   > first — customize is for adjusting a profile you already have.\n\n2. **Show the customizable map.** List what's in the profile, grouped, with a\n   one-line summary of the current value:\n\n   - **Company \u002F who you are** — name, industry, jurisdictions, stage, practice\n     setting *(shared across all 12 plugins — changes flow through\n     `company-profile.md`)*\n   - **Regulatory footprint** — EU AI Act, state AI laws, sector regulators in\n     scope\n   - **Risk posture** — conservative \u002F middle \u002F aggressive, what each means for\n     triage and AIA output\n   - **People** — governance team, AI risk owner, escalation chain, approvers\n   - **Use case registry** — approved \u002F conditional \u002F never entries, and\n     conditions attached to each\n   - **AI system inventory** — per-system role (provider \u002F deployer \u002F etc.) and\n     tier under the EU AI Act. Run `\u002Fai-governance-legal:ai-inventory` for\n     the dedicated editor.\n   - **Vendor AI governance** — training-on-data, liability, model-change\n     notice, and other positions in your vendor AI playbook\n   - **AI policy commitments** — the public or internal commitments your AI\n     policy has made, that the plugin cross-checks against\n   - **Impact assessment house style** — AIA section order, risk scoring\n     format, stakeholder framing\n   - **Workflow** — intake path, output format, matter workspace paths, review\n     cadence for the policy monitor\n   - **Integrations** — what's connected (Slack, document storage,\n     scheduled-tasks), what falls back\n\n3. **Ask what they want to change.**\n\n   > What would you like to adjust? Pick a section, or describe the change in\n   > your own words.\n\n4. **Make the change.** Show the current value, ask for the new value, explain\n   what changes downstream, confirm, write it to the config.\n\n   Examples of downstream explanation:\n   - *Risk posture middle → conservative:* \"I'll flag more use cases as\n     conditional rather than approved, surface more AIA follow-ups, and\n     recommend more conservative vendor AI redlines.\"\n   - *Adding an escalation contact:* \"Every skill that routes escalations\n     (`\u002Ftriage`, `\u002Freview-vendor-ai`, `\u002Fgap-check`) will now include this\n     contact on the relevant risk bands.\"\n   - *New use case registry entry:* \"`\u002Ftriage` will match against this entry\n     on its next run. Existing AIAs aren't rewritten — re-run them if you want\n     the new posture reflected.\"\n\n5. **For shared-profile changes** (company name, industry, jurisdictions,\n   practice setting, stage): write to\n   `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcompany-profile.md` and note:\n\n   > This change affects all 12 plugins — any plugin that reads your\n   > jurisdiction footprint now sees [new value].\n\n6. **Close.**\n\n   > Done. Your next output will reflect the change. Anything else? You can\n   > run `\u002Fai-governance-legal:customize` anytime.\n\n## Guardrails\n\n- **Never delete a section.** If the user wants to \"remove\" something, set it\n  to `[Not configured]` and explain what that means for the plugin's behavior.\n  (\"Removing your escalation chain means `\u002Ftriage` will flag escalation-worthy\n  items but won't route them to a specific person.\")\n- **Flag internal inconsistency.** If the change would make the profile\n  inconsistent (e.g., risk posture aggressive + escalation \"everything goes to\n  the GC\"; or \"EU AI Act in scope\" + \"no systems flagged for the EU\"), flag\n  the tension and ask which one they want.\n- **Flag guardrail degradation.** If the user asks to turn off a guardrail\n  (\"stop adding the `[review]` flag,\" \"drop the citations warning,\" \"skip the\n  privilege header\"), explain what the guardrail protects against and confirm\n  they understand the trade-off. Most guardrails are adjustable — a few are\n  structural:\n  - The `[review]` flag mechanism (tells the user when legal judgment is\n    needed rather than a confident wrong answer) — load-bearing, don't\n    remove.\n  - Source attribution tags on retrieved content — load-bearing, don't remove.\n  - `[verify]` tags on cited statutes\u002Fregulations — load-bearing, don't\n    remove.\n- **One change at a time.** Don't re-ask the whole interview. If the user\n  wants multiple changes, handle them sequentially and confirm each before\n  moving on.\n","# \u002Fcustomize\n\n## When this runs\n\nThe user typed `\u002Fai-governance-legal:customize`. They want to change something\nin their practice profile — a risk posture, an escalation contact, a playbook\nposition, a jurisdiction, an output format — without re-running the whole\ncold-start interview and without hand-editing YAML.\n\n## What to do\n\n1. **Read the config.** Read\n   `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fai-governance-legal\u002FCLAUDE.md`\n   (and `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcompany-profile.md` one\n   level up). If the plugin config does not exist or still contains\n   `[PLACEHOLDER]` values, say:\n\n   > You haven't run setup yet. Run `\u002Fai-governance-legal:cold-start-interview`\n   > first — customize is for adjusting a profile you already have.\n\n2. **Show the customizable map.** List what's in the profile, grouped, with a\n   one-line summary of the current value:\n\n   - **Company \u002F who you are** — name, industry, jurisdictions, stage, practice\n     setting *(shared across all 12 plugins — changes flow through\n     `company-profile.md`)*\n   - **Regulatory footprint** — EU AI Act, state AI laws, sector regulators in\n     scope\n   - **Risk posture** — conservative \u002F middle \u002F aggressive, what each means for\n     triage and AIA output\n   - **People** — governance team, AI risk owner, escalation chain, approvers\n   - **Use case registry** — approved \u002F conditional \u002F never entries, and\n     conditions attached to each\n   - **AI system inventory** — per-system role (provider \u002F deployer \u002F etc.) and\n     tier under the EU AI Act. Run `\u002Fai-governance-legal:ai-inventory` for\n     the dedicated editor.\n   - **Vendor AI governance** — training-on-data, liability, model-change\n     notice, and other positions in your vendor AI playbook\n   - **AI policy commitments** — the public or internal commitments your AI\n     policy has made, that the plugin cross-checks against\n   - **Impact assessment house style** — AIA section order, risk scoring\n     format, stakeholder framing\n   - **Workflow** — intake path, output format, matter workspace paths, review\n     cadence for the policy monitor\n   - **Integrations** — what's connected (Slack, document storage,\n     scheduled-tasks), what falls back\n\n3. **Ask what they want to change.**\n\n   > What would you like to adjust? Pick a section, or describe the change in\n   > your own words.\n\n4. **Make the change.** Show the current value, ask for the new value, explain\n   what changes downstream, confirm, write it to the config.\n\n   Examples of downstream explanation:\n   - *Risk posture middle → conservative:* \"I'll flag more use cases as\n     conditional rather than approved, surface more AIA follow-ups, and\n     recommend more conservative vendor AI redlines.\"\n   - *Adding an escalation contact:* \"Every skill that routes escalations\n     (`\u002Ftriage`, `\u002Freview-vendor-ai`, `\u002Fgap-check`) will now include this\n     contact on the relevant risk bands.\"\n   - *New use case registry entry:* \"`\u002Ftriage` will match against this entry\n     on its next run. Existing AIAs aren't rewritten — re-run them if you want\n     the new posture reflected.\"\n\n5. **For shared-profile changes** (company name, industry, jurisdictions,\n   practice setting, stage): write to\n   `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcompany-profile.md` and note:\n\n   > This change affects all 12 plugins — any plugin that reads your\n   > jurisdiction footprint now sees [new value].\n\n6. **Close.**\n\n   > Done. Your next output will reflect the change. Anything else? You can\n   > run `\u002Fai-governance-legal:customize` anytime.\n\n## Guardrails\n\n- **Never delete a section.** If the user wants to \"remove\" something, set it\n  to `[Not configured]` and explain what that means for the plugin's behavior.\n  (\"Removing your escalation chain means `\u002Ftriage` will flag escalation-worthy\n  items but won't route them to a specific person.\")\n- **Flag internal inconsistency.** If the change would make the profile\n  inconsistent (e.g., risk posture aggressive + escalation \"everything goes to\n  the GC\"; or \"EU AI Act in scope\" + \"no systems flagged for the EU\"), flag\n  the tension and ask which one they want.\n- **Flag guardrail degradation.** If the user asks to turn off a guardrail\n  (\"stop adding the `[review]` flag,\" \"drop the citations warning,\" \"skip the\n  privilege header\"), explain what the guardrail protects against and confirm\n  they understand the trade-off. Most guardrails are adjustable — a few are\n  structural:\n  - The `[review]` flag mechanism (tells the user when legal judgment is\n    needed rather than a confident wrong answer) — load-bearing, don't\n    remove.\n  - Source attribution tags on retrieved content — load-bearing, don't remove.\n  - `[verify]` tags on cited statutes\u002Fregulations — load-bearing, don't\n    remove.\n- **One change at a time.** Don't re-ask the whole interview. If the user\n  wants multiple changes, handle them sequentially and confirm each before\n  moving on.\n",{"name":5,"description":23,"argument-hint":24},"Guided customization of your AI governance practice profile — change one thing without re-running the whole cold-start interview. Adjust risk posture, escalation contacts, use-case registry entries, vendor AI positions, AI policy commitments, impact-assessment house style, or matter workspace paths. Use when the user says \"change my [thing]\", \"update my profile\", \"edit my config\", \"tune my playbook\", or \"customize\".\n","[section name, or describe what you want to change]","main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fcustomize",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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add agisota\u002Fold-one --skill customize",{"tool":40,"command":41},"bunx","bunx skills add agisota\u002Fold-one --skill customize",{"tool":43,"command":44},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill customize","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fcustomize\u002FSKILL.md",true,[],[49,56,63,72,79,86],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"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":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"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":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":67,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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",[],[]]