[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75HFH1X7JBAR5HXGWSQSSPQ":3,"skill-same:01M75HFH1X7JBAR5HXGWSQSSPQ":47},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M75HFH1X7JBAR5HXGWSQSSPQ","portfolio-status",null,"Roll up the portfolio from _log.yaml — risk distribution, upcoming deadlines, stale matters, materiality totals, stage distribution, and flagged anomalies. Use when the user asks \"where do we stand\", \"how many open matters\", or wants a portfolio rollup or status across all active matters.","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\u002Fportfolio-status\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: portfolio-status\ndescription: Roll up the portfolio from _log.yaml — risk distribution, upcoming deadlines, stale matters, materiality totals, stage distribution, and flagged anomalies. Use when the user asks \"where do we stand\", \"how many open matters\", or wants a portfolio rollup or status across all active matters.\nargument-hint: \"[--all | --risk=high | --stale]\"\n---\n\n# \u002Fportfolio-status\n\n1. Load `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` → risk calibration (defines how to read the `risk:` field).\n2. Follow the workflow and reference below.\n3. Parse `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F_log.yaml`. Filter closed matters by default (include with `--all`).\n4. Produce rollup: risk distribution, deadlines in next 14\u002F30\u002F60 days, matters with no update in >30 days, materiality totals, stage distribution.\n5. Flag anomalies — everything marked critical, overdue next_deadline, matters without outside counsel assigned where risk is medium or high.\n\n---\n\n# Portfolio Status\n\n## Purpose\n\nOne read that answers: what do I own right now, what needs attention, and what's slipping? Output is scannable — designed for a counsel who has three minutes before their next call.\n\n## Load context\n\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F_log.yaml` — source of truth\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` — risk calibration (to interpret risk\u002Fmateriality fields correctly)\n\n## Flags & filters\n\nDefault: active matters only (exclude `status: closed`).\n\nFlags:\n- `--all` — include closed\n- `--risk=high` (or `critical` \u002F `medium` \u002F `low`) — filter by risk band\n- `--stale` — only matters with `last_updated` > 30 days\n- `--type=employment` — filter by matter type\n- `--owner=[name]` — filter by business\u002FHR\u002Fcomms owner\n\n## The rollup\n\n```markdown\n[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]\n\n# Portfolio Status — [today]\n\n**Active matters:** [N]\n**Closed (ytd):** [N] *(shown only with --all)*\n\n---\n\n## By risk\n\n| Risk | Count | Matters |\n|---|---|---|\n| Critical | [N] | [slugs] |\n| High | [N] | [slugs] |\n| Medium | [N] | [count only — expand with `--risk=medium`] |\n| Low | [N] | [count only] |\n\n## Upcoming deadlines\n\n| Within | Matters |\n|---|---|\n| 14 days | [slug — deadline — brief] |\n| 15–30 days | [...] |\n| 31–60 days | [...] |\n\n*Overdue `next_deadline` flagged separately below.*\n\n## Materiality\n\n| Category | Count | Total exposure (midpoint) |\n|---|---|---|\n| Reserved | [N] | [$X] |\n| Disclosed | [N] | [$X] |\n| Monitored | [N] | — |\n| None | [N] | — |\n\n## By stage\n\n[table: pleadings \u002F discovery \u002F dispositive motions \u002F trial prep \u002F settlement \u002F appeal]\n\n---\n\n## ⚠️ Anomalies & flags\n\n- **Overdue deadlines:** [list slugs where next_deadline has passed]\n- **Stale (>30d no update):** [list]\n- **Conflicts unresolved:** [list slugs with `conflicts.status in [pending, not-run]`]\n- **Conflicts bypassed (override active):** [list slugs where `conflicts.override.by` is populated — permanent flag until manually cleared]\n- **High\u002Fcritical risk without outside counsel:** [list]\n- **Reserved without last_updated in >60d:** [list] — reserve recalibration likely overdue\n- **Hold not issued on active litigation:** [list]\n- **Missing fields:** [slug → field]\n\n---\n\n## Closing advice\n\n[One or two sentences on what to look at first, if anything stands out. Not boilerplate — only if something truly stands out.]\n```\n\n## Anomaly rules\n\nThese are the checks that make the skill useful rather than decorative:\n\n1. **Overdue deadline:** `next_deadline \u003C today` and `status != closed`\n2. **Stale:** `last_updated \u003C today - 30d` and `status != closed`\n3. **Conflicts unresolved:** `conflicts.status in [pending, not-run]` and `status != closed`\n3b. **Conflicts override active:** `conflicts.override.by != null` (never auto-clears)\n4. **High-risk uncovered:** `risk in [high, critical]` and `outside_counsel.firm == null`\n5. **Stale reserve:** `materiality == reserved` and `last_updated \u003C today - 60d`\n6. **Hold gap:** `status in [threatened, active, discovery, trial, appeal]` and `legal_hold.issued == false` — preservation duty attaches at reasonable anticipation, so `threatened` matters are in scope.\n7. **Missing fields:** any required field null — `risk`, `materiality`, `status`, `opened`, `conflicts.status`\n\n## Close with the next-steps decision tree\n\nEnd with the next-steps decision tree per CLAUDE.md `## Outputs`. Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.\n\nIf the portfolio has more than ~10 matters, or any time the user asks: offer the dashboard (see CLAUDE.md `## Outputs → Dashboard offer for data-heavy outputs`). Shape the offer for this output — counts by risk tier, a timeline of upcoming deadlines, and a sortable matter ledger with status, conflicts check, and last-touched date.\n\n## What this skill does not do\n\n- Make decisions. It surfaces what needs attention; the user decides priority.\n- Pretend precision it doesn't have. Exposure midpoints are rough and should be labeled so.\n- Replace a real MMS. This is a working-memory rollup, not a system of record.\n","# \u002Fportfolio-status\n\n1. Load `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` → risk calibration (defines how to read the `risk:` field).\n2. Follow the workflow and reference below.\n3. Parse `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F_log.yaml`. Filter closed matters by default (include with `--all`).\n4. Produce rollup: risk distribution, deadlines in next 14\u002F30\u002F60 days, matters with no update in >30 days, materiality totals, stage distribution.\n5. Flag anomalies — everything marked critical, overdue next_deadline, matters without outside counsel assigned where risk is medium or high.\n\n---\n\n# Portfolio Status\n\n## Purpose\n\nOne read that answers: what do I own right now, what needs attention, and what's slipping? Output is scannable — designed for a counsel who has three minutes before their next call.\n\n## Load context\n\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F_log.yaml` — source of truth\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` — risk calibration (to interpret risk\u002Fmateriality fields correctly)\n\n## Flags & filters\n\nDefault: active matters only (exclude `status: closed`).\n\nFlags:\n- `--all` — include closed\n- `--risk=high` (or `critical` \u002F `medium` \u002F `low`) — filter by risk band\n- `--stale` — only matters with `last_updated` > 30 days\n- `--type=employment` — filter by matter type\n- `--owner=[name]` — filter by business\u002FHR\u002Fcomms owner\n\n## The rollup\n\n```markdown\n[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]\n\n# Portfolio Status — [today]\n\n**Active matters:** [N]\n**Closed (ytd):** [N] *(shown only with --all)*\n\n---\n\n## By risk\n\n| Risk | Count | Matters |\n|---|---|---|\n| Critical | [N] | [slugs] |\n| High | [N] | [slugs] |\n| Medium | [N] | [count only — expand with `--risk=medium`] |\n| Low | [N] | [count only] |\n\n## Upcoming deadlines\n\n| Within | Matters |\n|---|---|\n| 14 days | [slug — deadline — brief] |\n| 15–30 days | [...] |\n| 31–60 days | [...] |\n\n*Overdue `next_deadline` flagged separately below.*\n\n## Materiality\n\n| Category | Count | Total exposure (midpoint) |\n|---|---|---|\n| Reserved | [N] | [$X] |\n| Disclosed | [N] | [$X] |\n| Monitored | [N] | — |\n| None | [N] | — |\n\n## By stage\n\n[table: pleadings \u002F discovery \u002F dispositive motions \u002F trial prep \u002F settlement \u002F appeal]\n\n---\n\n## ⚠️ Anomalies & flags\n\n- **Overdue deadlines:** [list slugs where next_deadline has passed]\n- **Stale (>30d no update):** [list]\n- **Conflicts unresolved:** [list slugs with `conflicts.status in [pending, not-run]`]\n- **Conflicts bypassed (override active):** [list slugs where `conflicts.override.by` is populated — permanent flag until manually cleared]\n- **High\u002Fcritical risk without outside counsel:** [list]\n- **Reserved without last_updated in >60d:** [list] — reserve recalibration likely overdue\n- **Hold not issued on active litigation:** [list]\n- **Missing fields:** [slug → field]\n\n---\n\n## Closing advice\n\n[One or two sentences on what to look at first, if anything stands out. Not boilerplate — only if something truly stands out.]\n```\n\n## Anomaly rules\n\nThese are the checks that make the skill useful rather than decorative:\n\n1. **Overdue deadline:** `next_deadline \u003C today` and `status != closed`\n2. **Stale:** `last_updated \u003C today - 30d` and `status != closed`\n3. **Conflicts unresolved:** `conflicts.status in [pending, not-run]` and `status != closed`\n3b. **Conflicts override active:** `conflicts.override.by != null` (never auto-clears)\n4. **High-risk uncovered:** `risk in [high, critical]` and `outside_counsel.firm == null`\n5. **Stale reserve:** `materiality == reserved` and `last_updated \u003C today - 60d`\n6. **Hold gap:** `status in [threatened, active, discovery, trial, appeal]` and `legal_hold.issued == false` — preservation duty attaches at reasonable anticipation, so `threatened` matters are in scope.\n7. **Missing fields:** any required field null — `risk`, `materiality`, `status`, `opened`, `conflicts.status`\n\n## Close with the next-steps decision tree\n\nEnd with the next-steps decision tree per CLAUDE.md `## Outputs`. Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.\n\nIf the portfolio has more than ~10 matters, or any time the user asks: offer the dashboard (see CLAUDE.md `## Outputs → Dashboard offer for data-heavy outputs`). Shape the offer for this output — counts by risk tier, a timeline of upcoming deadlines, and a sortable matter ledger with status, conflicts check, and last-touched date.\n\n## What this skill does not do\n\n- Make decisions. It surfaces what needs attention; the user decides priority.\n- Pretend precision it doesn't have. Exposure midpoints are rough and should be labeled so.\n- Replace a real MMS. This is a working-memory rollup, not a system of record.\n",{"name":5,"description":7,"argument-hint":23},"[--all | --risk=high | --stale]","main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fportfolio-status",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":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add agisota\u002Fold-one --skill portfolio-status",{"tool":39,"command":40},"bunx","bunx skills add agisota\u002Fold-one --skill portfolio-status",{"tool":42,"command":43},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill portfolio-status","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fportfolio-status\u002FSKILL.md",true,[],[48,55,62,71,78,85],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"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":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"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":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":66,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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",[],[]]