[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EB985PSFYYB09S957PMPV0":3,"skill-same:01M6EB985PSFYYB09S957PMPV0":80},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6EB985PSFYYB09S957PMPV0","decision-logger",null,"Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions after a board meeting, reviewing past decisions with \u002Fcs:decisions, or checking overdue action items with \u002Fcs:review. Invoked automatically by the board-meeting skill after Phase 5 founder approval.","levalencia\u002Fagent-god-mode","levalencia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6962857?v=4","01M6EB0FZZ4BPQPC4HET4QY6NM","Luis Valencia ","01M6EB0G4HWHPWW0H9X7QKSAHP",3,"MIT","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002F.gemini-decision-logger\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"decision","decision logger","logger","review","memory","architecture","logging","decisions","board meeting","board","approval","use","tracker","founder","scripts","2026-11-10 10:12:30",false,"---\nname: \"decision-logger\"\ndescription: \"Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions after a board meeting, reviewing past decisions with \u002Fcs:decisions, or checking overdue action items with \u002Fcs:review. Invoked automatically by the board-meeting skill after Phase 5 founder approval.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: decision-memory\n  updated: 2026-03-05\n  python-tools: scripts\u002Fdecision_tracker.py\n---\n\n# Decision Logger\n\nTwo-layer memory system. Layer 1 stores everything. Layer 2 stores only what the founder approved. Future meetings read Layer 2 only — this prevents hallucinated consensus from past debates bleeding into new deliberations.\n\n## Keywords\ndecision log, memory, approved decisions, action items, board minutes, \u002Fcs:decisions, \u002Fcs:review, conflict detection, DO_NOT_RESURFACE\n\n## Quick Start\n\n```bash\npython scripts\u002Fdecision_tracker.py --demo             # See sample output\npython scripts\u002Fdecision_tracker.py --summary          # Overview + overdue\npython scripts\u002Fdecision_tracker.py --overdue          # Past-deadline actions\npython scripts\u002Fdecision_tracker.py --conflicts        # Contradiction detection\npython scripts\u002Fdecision_tracker.py --owner \"CTO\"      # Filter by owner\npython scripts\u002Fdecision_tracker.py --search \"pricing\" # Search decisions\n```\n\n---\n\n## Commands\n\n| Command | Effect |\n|---------|--------|\n| `\u002Fcs:decisions` | Last 10 approved decisions |\n| `\u002Fcs:decisions --all` | Full history |\n| `\u002Fcs:decisions --owner CMO` | Filter by owner |\n| `\u002Fcs:decisions --topic pricing` | Search by keyword |\n| `\u002Fcs:review` | Action items due within 7 days |\n| `\u002Fcs:review --overdue` | Items past deadline |\n\n---\n\n## Two-Layer Architecture\n\n### Layer 1 — Raw Transcripts\n**Location:** `memory\u002Fboard-meetings\u002FYYYY-MM-DD-raw.md`\n- Full Phase 2 agent contributions, Phase 3 critique, Phase 4 synthesis\n- All debates, including rejected arguments\n- **NEVER auto-loaded.** Only on explicit founder request.\n- Archive after 90 days → `memory\u002Fboard-meetings\u002Farchive\u002FYYYY\u002F`\n\n### Layer 2 — Approved Decisions\n**Location:** `memory\u002Fboard-meetings\u002Fdecisions.md`\n- ONLY founder-approved decisions, action items, user corrections\n- **Loaded automatically in Phase 1 of every board meeting**\n- Append-only. Decisions are never deleted — only superseded.\n- Managed by Chief of Staff after Phase 5. Never written by agents directly.\n\n---\n\n## Decision Entry Format\n\n```markdown\n## [YYYY-MM-DD] — [AGENDA ITEM TITLE]\n\n**Decision:** [One clear statement of what was decided.]\n**Owner:** [One person or role — accountable for execution.]\n**Deadline:** [YYYY-MM-DD]\n**Review:** [YYYY-MM-DD]\n**Rationale:** [Why this over alternatives. 1-2 sentences.]\n\n**User Override:** [If founder changed agent recommendation — what and why. Blank if not applicable.]\n\n**Rejected:**\n- [Proposal] — [reason] [DO_NOT_RESURFACE]\n\n**Action Items:**\n- [ ] [Action] — Owner: [name] — Due: [YYYY-MM-DD] — Review: [YYYY-MM-DD]\n\n**Supersedes:** [DATE of previous decision on same topic, if any]\n**Superseded by:** [Filled in retroactively if overridden later]\n**Raw transcript:** memory\u002Fboard-meetings\u002F[DATE]-raw.md\n```\n\n---\n\n## Conflict Detection\n\nBefore logging, Chief of Staff checks for:\n1. **DO_NOT_RESURFACE violations** — new decision matches a rejected proposal\n2. **Topic contradictions** — two active decisions on same topic with different conclusions\n3. **Owner conflicts** — same action assigned to different people in different decisions\n\nWhen a conflict is found:\n```\n⚠️ DECISION CONFLICT\nNew: [text]\nConflicts with: [DATE] — [existing text]\n\nOptions: (1) Supersede old  (2) Merge  (3) Defer to founder\n```\n\n**DO_NOT_RESURFACE enforcement:**\n```\n? BLOCKED: \"[Proposal]\" was rejected on [DATE]. Reason: [reason].\nTo reopen: founder must explicitly say \"reopen [topic] from [DATE]\".\n```\n\n---\n\n## Logging Workflow (Post Phase 5)\n\n1. Founder approves synthesis\n2. Write Layer 1 raw transcript → `YYYY-MM-DD-raw.md`\n3. Check conflicts against `decisions.md`\n4. Surface conflicts → wait for founder resolution\n5. Append approved entries to `decisions.md`\n6. Confirm: decisions logged, actions tracked, DO_NOT_RESURFACE flags added\n\n---\n\n## Marking Actions Complete\n\n```markdown\n- [x] [Action] — Owner: [name] — Completed: [DATE] — Result: [one sentence]\n```\n\nNever delete completed items. The history is the record.\n\n---\n\n## File Structure\n\n```\nmemory\u002Fboard-meetings\u002F\n├── decisions.md       # Layer 2: append-only, founder-approved\n├── YYYY-MM-DD-raw.md  # Layer 1: full transcript per meeting\n└── archive\u002FYYYY\u002F      # Raw files after 90 days\n```\n\n---\n\n## References\n- `templates\u002Fdecision-entry.md` — single entry template with field rules\n- `scripts\u002Fdecision_tracker.py` — CLI parser, overdue tracker, conflict detector\n","# Decision Logger\n\nTwo-layer memory system. Layer 1 stores everything. Layer 2 stores only what the founder approved. Future meetings read Layer 2 only — this prevents hallucinated consensus from past debates bleeding into new deliberations.\n\n## Keywords\ndecision log, memory, approved decisions, action items, board minutes, \u002Fcs:decisions, \u002Fcs:review, conflict detection, DO_NOT_RESURFACE\n\n## Quick Start\n\n```bash\npython scripts\u002Fdecision_tracker.py --demo             # See sample output\npython scripts\u002Fdecision_tracker.py --summary          # Overview + overdue\npython scripts\u002Fdecision_tracker.py --overdue          # Past-deadline actions\npython scripts\u002Fdecision_tracker.py --conflicts        # Contradiction detection\npython scripts\u002Fdecision_tracker.py --owner \"CTO\"      # Filter by owner\npython scripts\u002Fdecision_tracker.py --search \"pricing\" # Search decisions\n```\n\n---\n\n## Commands\n\n| Command | Effect |\n|---------|--------|\n| `\u002Fcs:decisions` | Last 10 approved decisions |\n| `\u002Fcs:decisions --all` | Full history |\n| `\u002Fcs:decisions --owner CMO` | Filter by owner |\n| `\u002Fcs:decisions --topic pricing` | Search by keyword |\n| `\u002Fcs:review` | Action items due within 7 days |\n| `\u002Fcs:review --overdue` | Items past deadline |\n\n---\n\n## Two-Layer Architecture\n\n### Layer 1 — Raw Transcripts\n**Location:** `memory\u002Fboard-meetings\u002FYYYY-MM-DD-raw.md`\n- Full Phase 2 agent contributions, Phase 3 critique, Phase 4 synthesis\n- All debates, including rejected arguments\n- **NEVER auto-loaded.** Only on explicit founder request.\n- Archive after 90 days → `memory\u002Fboard-meetings\u002Farchive\u002FYYYY\u002F`\n\n### Layer 2 — Approved Decisions\n**Location:** `memory\u002Fboard-meetings\u002Fdecisions.md`\n- ONLY founder-approved decisions, action items, user corrections\n- **Loaded automatically in Phase 1 of every board meeting**\n- Append-only. Decisions are never deleted — only superseded.\n- Managed by Chief of Staff after Phase 5. Never written by agents directly.\n\n---\n\n## Decision Entry Format\n\n```markdown\n## [YYYY-MM-DD] — [AGENDA ITEM TITLE]\n\n**Decision:** [One clear statement of what was decided.]\n**Owner:** [One person or role — accountable for execution.]\n**Deadline:** [YYYY-MM-DD]\n**Review:** [YYYY-MM-DD]\n**Rationale:** [Why this over alternatives. 1-2 sentences.]\n\n**User Override:** [If founder changed agent recommendation — what and why. Blank if not applicable.]\n\n**Rejected:**\n- [Proposal] — [reason] [DO_NOT_RESURFACE]\n\n**Action Items:**\n- [ ] [Action] — Owner: [name] — Due: [YYYY-MM-DD] — Review: [YYYY-MM-DD]\n\n**Supersedes:** [DATE of previous decision on same topic, if any]\n**Superseded by:** [Filled in retroactively if overridden later]\n**Raw transcript:** memory\u002Fboard-meetings\u002F[DATE]-raw.md\n```\n\n---\n\n## Conflict Detection\n\nBefore logging, Chief of Staff checks for:\n1. **DO_NOT_RESURFACE violations** — new decision matches a rejected proposal\n2. **Topic contradictions** — two active decisions on same topic with different conclusions\n3. **Owner conflicts** — same action assigned to different people in different decisions\n\nWhen a conflict is found:\n```\n⚠️ DECISION CONFLICT\nNew: [text]\nConflicts with: [DATE] — [existing text]\n\nOptions: (1) Supersede old  (2) Merge  (3) Defer to founder\n```\n\n**DO_NOT_RESURFACE enforcement:**\n```\n? BLOCKED: \"[Proposal]\" was rejected on [DATE]. Reason: [reason].\nTo reopen: founder must explicitly say \"reopen [topic] from [DATE]\".\n```\n\n---\n\n## Logging Workflow (Post Phase 5)\n\n1. Founder approves synthesis\n2. Write Layer 1 raw transcript → `YYYY-MM-DD-raw.md`\n3. Check conflicts against `decisions.md`\n4. Surface conflicts → wait for founder resolution\n5. Append approved entries to `decisions.md`\n6. Confirm: decisions logged, actions tracked, DO_NOT_RESURFACE flags added\n\n---\n\n## Marking Actions Complete\n\n```markdown\n- [x] [Action] — Owner: [name] — Completed: [DATE] — Result: [one sentence]\n```\n\nNever delete completed items. The history is the record.\n\n---\n\n## File Structure\n\n```\nmemory\u002Fboard-meetings\u002F\n├── decisions.md       # Layer 2: append-only, founder-approved\n├── YYYY-MM-DD-raw.md  # Layer 1: full transcript per meeting\n└── archive\u002FYYYY\u002F      # Raw files after 90 days\n```\n\n---\n\n## References\n- `templates\u002Fdecision-entry.md` — single entry template with field rules\n- `scripts\u002Fdecision_tracker.py` — CLI parser, overdue tracker, conflict detector\n",{"name":5,"license":15,"metadata":39,"description":7},{"author":40,"domain":41,"updated":42,"version":43,"category":44,"python-tools":45},"Alireza Rezvani","decision-memory",1772668800000,"1.0.0","c-level","scripts\u002Fdecision_tracker.py","main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002F.gemini-decision-logger",1,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode","https:\u002F\u002Fgithub.com\u002Flevalencia","https:\u002F\u002Fmedium.com\u002F@luisevalencia","Microsoft MVP - Artificial Intelligence\r\nMachine Learning Enthusiast\r\n","2026-05-02 06:55:36",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add levalencia\u002Fagent-god-mode --skill decision-logger",{"tool":61,"command":62},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill decision-logger",{"tool":64,"command":65},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill decision-logger","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002F.gemini-decision-logger\u002FSKILL.md",true,[69,74],{"path":45,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"SCRIPT","脚本",23369,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002F.gemini-decision-logger\u002Fscripts\u002Fdecision_tracker.py",{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"templates\u002Fdecision-entry.md","REFERENCE","参考文档",2286,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002F.gemini-decision-logger\u002Ftemplates\u002Fdecision-entry.md",[81,103,140,167,192,220],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":34},"01M6EM8ES5M9J4S8N78NJST0YC","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fzarr-python\u002FSKILL.md",[],[88,89,90,91,92,93,94,95,96,97,98,99,100,101,102],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":122,"publishedAt":34},"01M6EM8AR6ZFKZ9YVW8TTG850Z","zabbix","Zabbix monitoring system automation via API and Python. Use when: (1) Managing hosts, templates, items, triggers, or host groups, (2) Automating monitoring configuration, (3) Sending data via Zabbix trapper\u002Fsender, (4) Querying historical data or events, (5) Bulk operations on Zabbix objects, (6) Maintenance window management, (7) User\u002Fpermission management","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fzabbix-api-skill\u002FSKILL.md",[109,114,117],{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":115,"categoryName":116,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[105,88,123,124,125,126,127,128,129,130,30,131,132,133,134,135,136,137,138,139],"automation","window management","monitoring","data","templates","api","system","operations","maintenance","objects","permission","bulk operations","triggers","host","events","via","bulk",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":34},"01M6EM6Q9JG846ECQY9A210A26","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\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fx-twitter-growth\u002FSKILL.md",[],[147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166],"twitter","x twitter growth","growth","competitive intelligence","search","analyzing","plan","marketing","web search","competitors","analyze","write","optimize","social","intelligence","viral","growth engine","mechanics","grow","competitive",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":34},"01M6EM3FQNPYNKPC4CV9TCVNGD","what-if-oracle","Run structured What-If scenario analysis with multi-branch possibility exploration. Use this skill when the user asks speculative questions like \"what if...\", \"what would happen if...\", \"what are the possibilities\", \"explore scenarios\", \"scenario analysis\", \"possibility space\", \"what could go wrong\", \"best case \u002F worst case\", \"risk analysis\", \"contingency planning\", \"strategic options\", or any question about uncertain futures. Also trigger when the user faces a fork-in-the-road decision, wants to stress-test an idea, or needs to think through consequences before committing.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fwhat-if-oracle\u002FSKILL.md",[],[174,175,176,177,178,179,180,181,182,19,183,184,30,185,186,187,188,189,190,191],"oracle","what if oracle","test","planning","ux","futures","risk","analysis","explore","branch","question","exploration","options","stress-test","strategies","trigger","case","multi",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":201,"publishedAt":34},"01M6EM08C06RGDYCJ86HAPK0FF","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fvercel-react-best-practices\u002FSKILL.md",[198],{"categoryNo":199,"categoryName":200,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000009","前端开发",[202,203,204,205,206,207,208,209,210,211,212,213,214,126,215,216,217,218,219,135],"react","vercel react best practices","best practices","react best practices","vercel","writing","performance","components","react components","guidelines","tasks","code","Optimization","Next.js","refactoring","performance optimization","next","pages",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":224,"categories":225,"keywords":236,"publishedAt":34},"01M6EM00S13326QM08DTM94J6Z","venue-templates","Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fvenue-templates\u002FSKILL.md",[226,229,232,233],{"categoryNo":227,"categoryName":228,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":230,"categoryName":231,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":115,"categoryName":116,"taxonomyType":112,"taxonomyTypeDesc":113},{"categoryNo":234,"categoryName":235,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000036","内容创作者",[127,237,238,211,239,240,241,242,243,244,245,158,246,247,248,249,250,251,102,252],"venue templates","research","NeurIPS","ICML","LaTeX","science","Bash","access","read","edit","proposals","Academic","requirements","formatting","journal","chi"]