[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75BJY7M3SQ87JJ8D25JDZTH":3,"skill-same:01M75BJY7M3SQ87JJ8D25JDZTH":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},"01M75BJY7M3SQ87JJ8D25JDZTH","ai-inventory",null,"EU AI Act per-system inventory — track each AI system's role (provider, deployer, importer, distributor, authorized representative, product manufacturer) and risk tier (prohibited, high-risk, limited, minimal, GPAI, GPAI+systemic). Role and tier are assessed per system, not per company. Use when the user says \"ai inventory\", \"add an ai system\", \"what systems do we have\", \"classify this ai system\", \"eu ai act register\", or \"ai system registry\".","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\u002Fai-inventory\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: ai-inventory\ndescription: >\n  EU AI Act per-system inventory — track each AI system's role (provider,\n  deployer, importer, distributor, authorized representative, product\n  manufacturer) and risk tier (prohibited, high-risk, limited, minimal,\n  GPAI, GPAI+systemic). Role and tier are assessed per system, not per\n  company. Use when the user says \"ai inventory\", \"add an ai system\",\n  \"what systems do we have\", \"classify this ai system\", \"eu ai act\n  register\", or \"ai system registry\".\nargument-hint: \"[list | add | edit \u003Cid> | classify \u003Cid> | show \u003Cid>]\"\n---\n\n# \u002Fai-inventory\n\n## When this runs\n\nThe user wants to manage their AI system inventory under the EU AI Act. The\ncore idea the skill exists to enforce: **role and tier are per-system, not\nper-company.** A single organization can be a *provider* of System A, a\n*deployer* of System B, and an *importer* of System C. Each combination\ntriggers a different set of obligations under the AI Act. The inventory\nexists so those assessments are tracked where you can find them — the\nobligations themselves are derived in conversation, not from a table.\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   If it doesn't exist or still has `[PLACEHOLDER]` markers, direct the user\n   to `\u002Fai-governance-legal:cold-start-interview` first.\n\n2. **Read the inventory.** Inventory lives at\n   `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fai-governance-legal\u002Fai-systems.yaml`.\n   If it doesn't exist, create it with an empty `systems:` list when the\n   first `add` runs.\n\n3. **Dispatch on the argument:**\n\n   - No argument, or `list` → show the inventory table (see **List** below).\n   - `add` → run the **Add** flow.\n   - `edit \u003Cid>` → show the current record, ask what to change, update one\n     field, confirm, write.\n   - `classify \u003Cid>` → run the **Classification walk-through** on an\n     existing record, updating role, tier, role_basis, and tier_basis.\n   - `show \u003Cid>` → show the full record.\n\n4. **On list, offer the dashboard:**\n   \"Want the full dashboard? Filter by status \u002F tier \u002F EU nexus \u002F owner.\n   Say the word.\"\n\n5. **Close every action with a hook into the lawyer's work.**\n   After any write, say:\n   > Recorded. When you're ready to walk through obligations for this\n   > system, just ask — I'll do it in-conversation and flag where the AI\n   > Act article mapping needs your verification. I don't derive\n   > obligations from a table because the mapping is complex and changing.\n\n## List format\n\nRender as a compact table:\n\n| ID | Name | Owner | Status | EU nexus | Role | Tier | Next review |\n|----|------|-------|--------|----------|------|------|-------------|\n| sys-001 | Resume screening | HR \u002F Jamie | in_production | yes | deployer | high_risk | 2026-08-01 |\n| sys-002 | Email drafting assistant | IT \u002F Priya | in_production | no | deployer | limited | 2026-12-01 |\n\nUnder the table, show counts by tier and a line: \"N systems flagged for\nreview within 30 days.\"\n\n## Add flow (interview)\n\nAsk, one field at a time (or accept a paste). The required fields are\n`name`, `owner`, `description`, `status`, `eu_nexus`. The rest can be\ndeferred — say so explicitly: \"you can come back to classification with\n`\u002Fai-governance-legal:ai-inventory classify \u003Cid>`.\"\n\n1. **Name.** Short label for the system.\n2. **Owner.** Person or team accountable for it day-to-day.\n3. **Description.** One or two sentences. What does it do, and against\n   what data?\n4. **Status.** `planned | in_development | in_production | deprecated`.\n5. **EU nexus.** Is the system deployed in the EU\u002FEEA, offered to users in\n   the EU\u002FEEA, or used to produce outputs that affect people in the\n   EU\u002FEEA? If any of these are true, EU AI Act analysis applies.\n6. **Proceed to classification?** Offer to run the walk-through now, or\n   skip and come back later.\n\nAssign an ID: `sys-NNN` where NNN is the next integer in the file.\n\n## Classification walk-through\n\nThe walk-through produces `role`, `role_basis`, `tier`, `tier_basis`. Both\nbases are tagged `[verify against current AI Act text]` — not because the\nskill is hedging, but because the article mapping is complex and the AI\nAct is still phasing in. The lawyer owns verification.\n\n### Step 1: Role\n\n> **Who does what to this system?**\n\nOptions, with the distinguishing test:\n\n- **Provider** — you develop it (or have it developed) and place it on the\n  EU market or put it into service under your own name or trademark.\n- **Deployer** — you use it under your own authority, not for personal\n  non-professional use. (Most common inside companies.)\n- **Importer** — you bring an AI system into the EU from a provider\n  established outside the EU.\n- **Distributor** — you make an AI system available on the EU market\n  without being the provider or importer.\n- **Authorized representative** — you act on behalf of a non-EU provider\n  and are established in the EU.\n- **Product manufacturer** — you put a general-purpose AI system (or\n  another AI system) into a product under your own name\u002Ftrademark. Treated\n  as provider for the product.\n\n**Dual-role flag.** If the user substantially modifies a vendor system\n(fine-tunes on their own data, changes the intended purpose, rebrands),\nthey may become a **provider** of the modified system even if they started\nas a deployer. Call this out when they describe any modification beyond\nconfiguration. `[verify against current AI Act text — Article 25, provider\nobligations and substantial modification]`\n\nWrite the role. Write `role_basis` in one sentence.\n\n### Step 2: Tier\n\n> **What does the system do, and does the use case fall into a regulated\n> category?**\n\nCheck in order:\n\n**A. Article 5 prohibited practices.** `[verify against current AI Act\ntext — Article 5]`\n\nSummaries, not definitive text:\n- Subliminal or deceptive techniques materially distorting behavior\n- Exploiting vulnerabilities (age, disability, socio-economic status) to\n  materially distort behavior\n- Social scoring by public authorities leading to detrimental treatment\n- Real-time remote biometric ID in publicly accessible spaces for law\n  enforcement (narrow exceptions)\n- Biometric categorization inferring race, political opinions, union\n  membership, religious or philosophical beliefs, sex life, or sexual\n  orientation\n- Emotion recognition in the workplace or education (medical and safety\n  exceptions)\n- Facial image database scraping from the internet or CCTV\n- Predictive policing based solely on personality traits\n\nIf matched → tier is `prohibited`. Flag the use case as stop and route to\nthe governance team's prohibited-practice workflow.\n\n**B. Annex III high-risk areas.** `[verify against current AI Act text —\nAnnex III]`\n\nSummaries:\n1. Biometric identification and categorization\n2. Critical infrastructure (digital infrastructure, road traffic, supply of\n   water \u002F gas \u002F heating \u002F electricity)\n3. Education and vocational training (access, evaluation, proctoring,\n   monitoring prohibited behavior)\n4. Employment, worker management, self-employment access — recruitment,\n   selection, promotion, termination, task allocation, monitoring, performance\n5. Essential private and public services (public benefits, credit scoring\n   for individuals, risk assessment and pricing for life\u002Fhealth insurance,\n   emergency dispatch)\n6. Law enforcement (risk assessment, polygraphs, deepfake detection,\n   reliability of evidence, profiling)\n7. Migration, asylum, border control (risk assessment, travel document\n   verification, examination of applications)\n8. Administration of justice and democratic processes (research and\n   interpretation, influencing elections)\n\nIf matched → tier is `high_risk`. Note the Annex III area and subsection.\n\n**C. GPAI.** `[verify against current AI Act text — Article 51 and\nsurrounding]`\n\n- **GPAI:** model trained on broad data at scale, designed for generality,\n  capable of competently performing a wide range of distinct tasks.\n- **GPAI + systemic risk:** cumulative compute > 10^25 FLOPs, or designated\n  by the Commission.\n\n**D. Limited risk.** Chatbots interacting with natural persons, deepfakes,\nemotion recognition and biometric categorization systems outside Article 5\nscope — transparency obligations apply.\n\n**E. Minimal risk.** Everything else.\n\nWrite the tier. Write `tier_basis` in one sentence, citing the article or\nAnnex entry that matched, tagged `[verify against current AI Act text]`.\n\n### Step 3: Recommendations\n\nOffer three next steps:\n1. \"Want me to walk through obligations for this system? I'll do it in\n   conversation — I don't derive them from a table.\"\n2. \"Want to run `\u002Fai-governance-legal:aia-generation` to produce a full\n   impact assessment?\"\n3. \"Want to set a next review date? I'll add it to the inventory.\"\n\n## Record format\n\n```yaml\nsystems:\n  - id: sys-001\n    name: \"Resume screening tool\"\n    owner: \"HR \u002F Jamie\"\n    description: \"Filters inbound CVs against job criteria\"\n    status: in_production          # planned | in_development | in_production | deprecated\n    eu_nexus: true                 # deployed, offered, or affects people in the EU\u002FEEA\n    role: deployer                 # provider | deployer | importer | distributor | authorized_rep | product_manufacturer\n    role_basis: \"We license from VendorX and deploy internally [verify against current AI Act text]\"\n    tier: high_risk                # prohibited | high_risk | limited | minimal | gpai | gpai_systemic\n    tier_basis: \"Annex III(4)(a) — employment, recruitment selection [verify against current AI Act text]\"\n    obligations_assessed: false\n    obligations_note: \"To assess: as deployer of a high-risk system — human oversight, input data quality, monitoring, record-keeping, informing workers, FRIA if public body\u002Fservice — see Article 26 [verify against current AI Act text]\"\n    next_review: \"2026-08-01\"\n    review_trigger: \"on substantial modification or annually\"\n    created: \"2026-05-11\"\n    updated: \"2026-05-11\"\n```\n\n## Why this skill does NOT auto-derive obligations\n\nThe inventory stores role, tier, and the basis for each. It does NOT\ncontain a hardcoded role × tier → obligations table.\n\nWhen the user asks \"what are my obligations for System X?\", the skill\ndoes the analysis **in conversation**, tagged `[verify]`, and routes to\n`\u002Fai-governance-legal:aia-generation` for the formal impact assessment\nif needed.\n\nThis is deliberate:\n- Article mapping is complex and the AI Act is phasing in through 2027.\n- Confident-and-wrong on a compliance obligation ends up in a board memo.\n- The inventory is a registry for the lawyer. The lawyer owns the\n  obligation analysis.\n\n## Guardrails\n\n- **Never classify silently.** The classification walk-through must be\n  visible; do not auto-classify from a system description.\n- **`[verify]` tags stay.** They are not hedging — they are the point.\n  Do not strip them in outputs.\n- **Flag substantial modification.** Whenever a system is modified beyond\n  configuration, prompt the user to re-run `\u002Fai-inventory classify` —\n  modification can change role.\n- **Don't declare obligations from a table.** If asked, do the analysis\n  in conversation and route to `\u002Faia-generation` for anything that needs\n  a formal record.\n","# \u002Fai-inventory\n\n## When this runs\n\nThe user wants to manage their AI system inventory under the EU AI Act. The\ncore idea the skill exists to enforce: **role and tier are per-system, not\nper-company.** A single organization can be a *provider* of System A, a\n*deployer* of System B, and an *importer* of System C. Each combination\ntriggers a different set of obligations under the AI Act. The inventory\nexists so those assessments are tracked where you can find them — the\nobligations themselves are derived in conversation, not from a table.\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   If it doesn't exist or still has `[PLACEHOLDER]` markers, direct the user\n   to `\u002Fai-governance-legal:cold-start-interview` first.\n\n2. **Read the inventory.** Inventory lives at\n   `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fai-governance-legal\u002Fai-systems.yaml`.\n   If it doesn't exist, create it with an empty `systems:` list when the\n   first `add` runs.\n\n3. **Dispatch on the argument:**\n\n   - No argument, or `list` → show the inventory table (see **List** below).\n   - `add` → run the **Add** flow.\n   - `edit \u003Cid>` → show the current record, ask what to change, update one\n     field, confirm, write.\n   - `classify \u003Cid>` → run the **Classification walk-through** on an\n     existing record, updating role, tier, role_basis, and tier_basis.\n   - `show \u003Cid>` → show the full record.\n\n4. **On list, offer the dashboard:**\n   \"Want the full dashboard? Filter by status \u002F tier \u002F EU nexus \u002F owner.\n   Say the word.\"\n\n5. **Close every action with a hook into the lawyer's work.**\n   After any write, say:\n   > Recorded. When you're ready to walk through obligations for this\n   > system, just ask — I'll do it in-conversation and flag where the AI\n   > Act article mapping needs your verification. I don't derive\n   > obligations from a table because the mapping is complex and changing.\n\n## List format\n\nRender as a compact table:\n\n| ID | Name | Owner | Status | EU nexus | Role | Tier | Next review |\n|----|------|-------|--------|----------|------|------|-------------|\n| sys-001 | Resume screening | HR \u002F Jamie | in_production | yes | deployer | high_risk | 2026-08-01 |\n| sys-002 | Email drafting assistant | IT \u002F Priya | in_production | no | deployer | limited | 2026-12-01 |\n\nUnder the table, show counts by tier and a line: \"N systems flagged for\nreview within 30 days.\"\n\n## Add flow (interview)\n\nAsk, one field at a time (or accept a paste). The required fields are\n`name`, `owner`, `description`, `status`, `eu_nexus`. The rest can be\ndeferred — say so explicitly: \"you can come back to classification with\n`\u002Fai-governance-legal:ai-inventory classify \u003Cid>`.\"\n\n1. **Name.** Short label for the system.\n2. **Owner.** Person or team accountable for it day-to-day.\n3. **Description.** One or two sentences. What does it do, and against\n   what data?\n4. **Status.** `planned | in_development | in_production | deprecated`.\n5. **EU nexus.** Is the system deployed in the EU\u002FEEA, offered to users in\n   the EU\u002FEEA, or used to produce outputs that affect people in the\n   EU\u002FEEA? If any of these are true, EU AI Act analysis applies.\n6. **Proceed to classification?** Offer to run the walk-through now, or\n   skip and come back later.\n\nAssign an ID: `sys-NNN` where NNN is the next integer in the file.\n\n## Classification walk-through\n\nThe walk-through produces `role`, `role_basis`, `tier`, `tier_basis`. Both\nbases are tagged `[verify against current AI Act text]` — not because the\nskill is hedging, but because the article mapping is complex and the AI\nAct is still phasing in. The lawyer owns verification.\n\n### Step 1: Role\n\n> **Who does what to this system?**\n\nOptions, with the distinguishing test:\n\n- **Provider** — you develop it (or have it developed) and place it on the\n  EU market or put it into service under your own name or trademark.\n- **Deployer** — you use it under your own authority, not for personal\n  non-professional use. (Most common inside companies.)\n- **Importer** — you bring an AI system into the EU from a provider\n  established outside the EU.\n- **Distributor** — you make an AI system available on the EU market\n  without being the provider or importer.\n- **Authorized representative** — you act on behalf of a non-EU provider\n  and are established in the EU.\n- **Product manufacturer** — you put a general-purpose AI system (or\n  another AI system) into a product under your own name\u002Ftrademark. Treated\n  as provider for the product.\n\n**Dual-role flag.** If the user substantially modifies a vendor system\n(fine-tunes on their own data, changes the intended purpose, rebrands),\nthey may become a **provider** of the modified system even if they started\nas a deployer. Call this out when they describe any modification beyond\nconfiguration. `[verify against current AI Act text — Article 25, provider\nobligations and substantial modification]`\n\nWrite the role. Write `role_basis` in one sentence.\n\n### Step 2: Tier\n\n> **What does the system do, and does the use case fall into a regulated\n> category?**\n\nCheck in order:\n\n**A. Article 5 prohibited practices.** `[verify against current AI Act\ntext — Article 5]`\n\nSummaries, not definitive text:\n- Subliminal or deceptive techniques materially distorting behavior\n- Exploiting vulnerabilities (age, disability, socio-economic status) to\n  materially distort behavior\n- Social scoring by public authorities leading to detrimental treatment\n- Real-time remote biometric ID in publicly accessible spaces for law\n  enforcement (narrow exceptions)\n- Biometric categorization inferring race, political opinions, union\n  membership, religious or philosophical beliefs, sex life, or sexual\n  orientation\n- Emotion recognition in the workplace or education (medical and safety\n  exceptions)\n- Facial image database scraping from the internet or CCTV\n- Predictive policing based solely on personality traits\n\nIf matched → tier is `prohibited`. Flag the use case as stop and route to\nthe governance team's prohibited-practice workflow.\n\n**B. Annex III high-risk areas.** `[verify against current AI Act text —\nAnnex III]`\n\nSummaries:\n1. Biometric identification and categorization\n2. Critical infrastructure (digital infrastructure, road traffic, supply of\n   water \u002F gas \u002F heating \u002F electricity)\n3. Education and vocational training (access, evaluation, proctoring,\n   monitoring prohibited behavior)\n4. Employment, worker management, self-employment access — recruitment,\n   selection, promotion, termination, task allocation, monitoring, performance\n5. Essential private and public services (public benefits, credit scoring\n   for individuals, risk assessment and pricing for life\u002Fhealth insurance,\n   emergency dispatch)\n6. Law enforcement (risk assessment, polygraphs, deepfake detection,\n   reliability of evidence, profiling)\n7. Migration, asylum, border control (risk assessment, travel document\n   verification, examination of applications)\n8. Administration of justice and democratic processes (research and\n   interpretation, influencing elections)\n\nIf matched → tier is `high_risk`. Note the Annex III area and subsection.\n\n**C. GPAI.** `[verify against current AI Act text — Article 51 and\nsurrounding]`\n\n- **GPAI:** model trained on broad data at scale, designed for generality,\n  capable of competently performing a wide range of distinct tasks.\n- **GPAI + systemic risk:** cumulative compute > 10^25 FLOPs, or designated\n  by the Commission.\n\n**D. Limited risk.** Chatbots interacting with natural persons, deepfakes,\nemotion recognition and biometric categorization systems outside Article 5\nscope — transparency obligations apply.\n\n**E. Minimal risk.** Everything else.\n\nWrite the tier. Write `tier_basis` in one sentence, citing the article or\nAnnex entry that matched, tagged `[verify against current AI Act text]`.\n\n### Step 3: Recommendations\n\nOffer three next steps:\n1. \"Want me to walk through obligations for this system? I'll do it in\n   conversation — I don't derive them from a table.\"\n2. \"Want to run `\u002Fai-governance-legal:aia-generation` to produce a full\n   impact assessment?\"\n3. \"Want to set a next review date? I'll add it to the inventory.\"\n\n## Record format\n\n```yaml\nsystems:\n  - id: sys-001\n    name: \"Resume screening tool\"\n    owner: \"HR \u002F Jamie\"\n    description: \"Filters inbound CVs against job criteria\"\n    status: in_production          # planned | in_development | in_production | deprecated\n    eu_nexus: true                 # deployed, offered, or affects people in the EU\u002FEEA\n    role: deployer                 # provider | deployer | importer | distributor | authorized_rep | product_manufacturer\n    role_basis: \"We license from VendorX and deploy internally [verify against current AI Act text]\"\n    tier: high_risk                # prohibited | high_risk | limited | minimal | gpai | gpai_systemic\n    tier_basis: \"Annex III(4)(a) — employment, recruitment selection [verify against current AI Act text]\"\n    obligations_assessed: false\n    obligations_note: \"To assess: as deployer of a high-risk system — human oversight, input data quality, monitoring, record-keeping, informing workers, FRIA if public body\u002Fservice — see Article 26 [verify against current AI Act text]\"\n    next_review: \"2026-08-01\"\n    review_trigger: \"on substantial modification or annually\"\n    created: \"2026-05-11\"\n    updated: \"2026-05-11\"\n```\n\n## Why this skill does NOT auto-derive obligations\n\nThe inventory stores role, tier, and the basis for each. It does NOT\ncontain a hardcoded role × tier → obligations table.\n\nWhen the user asks \"what are my obligations for System X?\", the skill\ndoes the analysis **in conversation**, tagged `[verify]`, and routes to\n`\u002Fai-governance-legal:aia-generation` for the formal impact assessment\nif needed.\n\nThis is deliberate:\n- Article mapping is complex and the AI Act is phasing in through 2027.\n- Confident-and-wrong on a compliance obligation ends up in a board memo.\n- The inventory is a registry for the lawyer. The lawyer owns the\n  obligation analysis.\n\n## Guardrails\n\n- **Never classify silently.** The classification walk-through must be\n  visible; do not auto-classify from a system description.\n- **`[verify]` tags stay.** They are not hedging — they are the point.\n  Do not strip them in outputs.\n- **Flag substantial modification.** Whenever a system is modified beyond\n  configuration, prompt the user to re-run `\u002Fai-inventory classify` —\n  modification can change role.\n- **Don't declare obligations from a table.** If asked, do the analysis\n  in conversation and route to `\u002Faia-generation` for anything that needs\n  a formal record.\n",{"name":5,"description":23,"argument-hint":24},"EU AI Act per-system inventory — track each AI system's role (provider, deployer, importer, distributor, authorized representative, product manufacturer) and risk tier (prohibited, high-risk, limited, minimal, GPAI, GPAI+systemic). Role and tier are assessed per system, not per company. Use when the user says \"ai inventory\", \"add an ai system\", \"what systems do we have\", \"classify this ai system\", \"eu ai act register\", or \"ai system registry\".\n","[list | add | edit \u003Cid> | classify \u003Cid> | show \u003Cid>]","main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fai-inventory",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 ai-inventory",{"tool":40,"command":41},"bunx","bunx skills add agisota\u002Fold-one --skill ai-inventory",{"tool":43,"command":44},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill ai-inventory","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fai-inventory\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",[],[]]