[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EDRZXTP8SBM52PE6SRWTE6":3,"skill-same:01M6EDRZXTP8SBM52PE6SRWTE6":64},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M6EDRZXTP8SBM52PE6SRWTE6","context-engine",null,"Loads and manages company context for all C-suite advisor skills. Reads ~\u002F.claude\u002Fcompany-context.md, detects stale context (>90 days), enriches context during conversations, and enforces privacy\u002Fanonymization rules before external API calls.","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\u002Fcontext-engine\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29],"engine","context","context engine","orchestration","privacy","enrichment","api","Rules","stale","advisor","loads","2026-11-10 10:12:30",false,"---\nname: \"context-engine\"\ndescription: \"Loads and manages company context for all C-suite advisor skills. Reads ~\u002F.claude\u002Fcompany-context.md, detects stale context (>90 days), enriches context during conversations, and enforces privacy\u002Fanonymization rules before external API calls.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: orchestration\n  updated: 2026-03-05\n  frameworks: context-loading, anonymization, context-enrichment\n---\n\n# Company Context Engine\n\nThe memory layer for C-suite advisors. Every advisor skill loads this first. Context is what turns generic advice into specific insight.\n\n## Keywords\ncompany context, context loading, context engine, company profile, advisor context, stale context, context refresh, privacy, anonymization\n\n---\n\n## Load Protocol (Run at Start of Every C-Suite Session)\n\n**Step 1 — Check for context file:** `~\u002F.claude\u002Fcompany-context.md`\n- Exists → proceed to Step 2\n- Missing → prompt: *\"Run \u002Fcs:setup to build your company context — it makes every advisor conversation significantly more useful.\"*\n\n**Step 2 — Check staleness:** Read `Last updated` field.\n- **\u003C 90 days:** Load and proceed.\n- **≥ 90 days:** Prompt: *\"Your context is [N] days old. Quick 15-min refresh (\u002Fcs:update), or continue with what I have?\"*\n  - If continue: load with `[STALE — last updated DATE]` noted internally.\n\n**Step 3 — Parse into working memory.** Always active:\n- Company stage (pre-PMF \u002F scaling \u002F optimizing)\n- Founder archetype (product \u002F sales \u002F technical \u002F operator)\n- Current #1 challenge\n- Runway (as risk signal — never share externally)\n- Team size\n- Unfair advantage\n- 12-month target\n\n---\n\n## Context Quality Signals\n\n| Condition | Confidence | Action |\n|-----------|-----------|--------|\n| \u003C 30 days, full interview | High | Use directly |\n| 30–90 days, update done | Medium | Use, flag what may have changed |\n| > 90 days | Low | Flag stale, prompt refresh |\n| Key fields missing | Low | Ask in-session |\n| No file | None | Prompt \u002Fcs:setup |\n\nIf Low: *\"My context is [stale\u002Fincomplete] — I'm assuming [X]. Correct me if I'm wrong.\"*\n\n---\n\n## Context Enrichment\n\nDuring conversations, you'll learn things not in the file. Capture them.\n\n**Triggers:** New number or timeline revealed, key person mentioned, priority shift, constraint surfaces.\n\n**Protocol:**\n1. Note internally: `[CONTEXT UPDATE: {what was learned}]`\n2. At session end: *\"I picked up a few things to add to your context. Want me to update the file?\"*\n3. If yes: append to the relevant dimension, update timestamp.\n\n**Never silently overwrite.** Always confirm before modifying the context file.\n\n---\n\n## Privacy Rules\n\n### Never send externally\n- Specific revenue or burn figures\n- Customer names\n- Employee names (unless publicly known)\n- Investor names (unless public)\n- Specific runway months\n- Watch List contents\n\n### Safe to use externally (with anonymization)\n- Stage label\n- Team size ranges (1–10, 10–50, 50–200+)\n- Industry vertical\n- Challenge category\n- Market position descriptor\n\n### Before any external API call or web search\nApply `references\u002Fanonymization-protocol.md`:\n- Numbers → ranges or stage-relative descriptors\n- Names → roles\n- Revenue → percentages or stage labels\n- Customers → \"Customer A, B, C\"\n\n---\n\n## Missing or Partial Context\n\nHandle gracefully — never block the conversation.\n\n- **Missing stage:** \"Just to calibrate — are you still finding PMF or scaling what works?\"\n- **Missing financials:** Use stage + team size to infer. Note the gap.\n- **Missing founder profile:** Infer from conversation style. Mark as inferred.\n- **Multiple founders:** Context reflects the interviewee. Note co-founder perspective may differ.\n\n---\n\n## Required Context Fields\n\n```\nRequired:\n  - Last updated (date)\n  - Company Identity → What we do\n  - Stage & Scale → Stage\n  - Founder Profile → Founder archetype\n  - Current Challenges → Priority #1\n  - Goals & Ambition → 12-month target\n\nHigh-value optional:\n  - Unfair advantage\n  - Kill-shot risk\n  - Avoided decision\n  - Watch list\n```\n\nMissing required fields: note gaps, work around in session, ask in-session only when critical.\n\n---\n\n## References\n- `references\u002Fanonymization-protocol.md` — detailed rules for stripping sensitive data before external calls\n","# Company Context Engine\n\nThe memory layer for C-suite advisors. Every advisor skill loads this first. Context is what turns generic advice into specific insight.\n\n## Keywords\ncompany context, context loading, context engine, company profile, advisor context, stale context, context refresh, privacy, anonymization\n\n---\n\n## Load Protocol (Run at Start of Every C-Suite Session)\n\n**Step 1 — Check for context file:** `~\u002F.claude\u002Fcompany-context.md`\n- Exists → proceed to Step 2\n- Missing → prompt: *\"Run \u002Fcs:setup to build your company context — it makes every advisor conversation significantly more useful.\"*\n\n**Step 2 — Check staleness:** Read `Last updated` field.\n- **\u003C 90 days:** Load and proceed.\n- **≥ 90 days:** Prompt: *\"Your context is [N] days old. Quick 15-min refresh (\u002Fcs:update), or continue with what I have?\"*\n  - If continue: load with `[STALE — last updated DATE]` noted internally.\n\n**Step 3 — Parse into working memory.** Always active:\n- Company stage (pre-PMF \u002F scaling \u002F optimizing)\n- Founder archetype (product \u002F sales \u002F technical \u002F operator)\n- Current #1 challenge\n- Runway (as risk signal — never share externally)\n- Team size\n- Unfair advantage\n- 12-month target\n\n---\n\n## Context Quality Signals\n\n| Condition | Confidence | Action |\n|-----------|-----------|--------|\n| \u003C 30 days, full interview | High | Use directly |\n| 30–90 days, update done | Medium | Use, flag what may have changed |\n| > 90 days | Low | Flag stale, prompt refresh |\n| Key fields missing | Low | Ask in-session |\n| No file | None | Prompt \u002Fcs:setup |\n\nIf Low: *\"My context is [stale\u002Fincomplete] — I'm assuming [X]. Correct me if I'm wrong.\"*\n\n---\n\n## Context Enrichment\n\nDuring conversations, you'll learn things not in the file. Capture them.\n\n**Triggers:** New number or timeline revealed, key person mentioned, priority shift, constraint surfaces.\n\n**Protocol:**\n1. Note internally: `[CONTEXT UPDATE: {what was learned}]`\n2. At session end: *\"I picked up a few things to add to your context. Want me to update the file?\"*\n3. If yes: append to the relevant dimension, update timestamp.\n\n**Never silently overwrite.** Always confirm before modifying the context file.\n\n---\n\n## Privacy Rules\n\n### Never send externally\n- Specific revenue or burn figures\n- Customer names\n- Employee names (unless publicly known)\n- Investor names (unless public)\n- Specific runway months\n- Watch List contents\n\n### Safe to use externally (with anonymization)\n- Stage label\n- Team size ranges (1–10, 10–50, 50–200+)\n- Industry vertical\n- Challenge category\n- Market position descriptor\n\n### Before any external API call or web search\nApply `references\u002Fanonymization-protocol.md`:\n- Numbers → ranges or stage-relative descriptors\n- Names → roles\n- Revenue → percentages or stage labels\n- Customers → \"Customer A, B, C\"\n\n---\n\n## Missing or Partial Context\n\nHandle gracefully — never block the conversation.\n\n- **Missing stage:** \"Just to calibrate — are you still finding PMF or scaling what works?\"\n- **Missing financials:** Use stage + team size to infer. Note the gap.\n- **Missing founder profile:** Infer from conversation style. Mark as inferred.\n- **Multiple founders:** Context reflects the interviewee. Note co-founder perspective may differ.\n\n---\n\n## Required Context Fields\n\n```\nRequired:\n  - Last updated (date)\n  - Company Identity → What we do\n  - Stage & Scale → Stage\n  - Founder Profile → Founder archetype\n  - Current Challenges → Priority #1\n  - Goals & Ambition → 12-month target\n\nHigh-value optional:\n  - Unfair advantage\n  - Kill-shot risk\n  - Avoided decision\n  - Watch list\n```\n\nMissing required fields: note gaps, work around in session, ask in-session only when critical.\n\n---\n\n## References\n- `references\u002Fanonymization-protocol.md` — detailed rules for stripping sensitive data before external calls\n",{"name":5,"license":15,"metadata":35,"description":7},{"author":36,"domain":22,"updated":37,"version":38,"category":39,"frameworks":40},"Alireza Rezvani",1772668800000,"1.0.0","c-level","context-loading, anonymization, context-enrichment","main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002Fcontext-engine",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":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add levalencia\u002Fagent-god-mode --skill context-engine",{"tool":56,"command":57},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill context-engine",{"tool":59,"command":60},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill context-engine","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fcontext-engine\u002FSKILL.md",true,[],[65,87,124,151,177,205],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":30},"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",[],[72,73,74,75,76,77,78,79,80,81,82,83,84,85,86],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":106,"publishedAt":30},"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",[93,98,101],{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":99,"categoryName":100,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[89,72,107,108,109,110,111,25,112,113,114,115,116,117,118,119,120,121,122,123],"automation","window management","monitoring","data","templates","system","operations","use","maintenance","objects","permission","bulk operations","triggers","host","events","via","bulk",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":30},"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",[],[131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150],"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":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":30},"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",[],[158,159,160,161,162,163,164,165,166,167,168,169,114,170,171,172,173,174,175,176],"oracle","what if oracle","test","planning","ux","futures","risk","analysis","explore","decision","branch","question","exploration","options","stress-test","strategies","trigger","case","multi",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":186,"publishedAt":30},"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",[183],{"categoryNo":184,"categoryName":185,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000009","前端开发",[187,188,189,190,191,192,193,194,195,196,197,198,199,110,200,201,202,203,204,119],"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":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":209,"categories":210,"keywords":221,"publishedAt":30},"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",[211,214,217,218],{"categoryNo":212,"categoryName":213,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":215,"categoryName":216,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":99,"categoryName":100,"taxonomyType":96,"taxonomyTypeDesc":97},{"categoryNo":219,"categoryName":220,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000036","内容创作者",[111,222,223,196,224,225,226,227,228,229,230,142,231,232,233,234,235,236,86,237],"venue templates","research","NeurIPS","ICML","LaTeX","science","Bash","access","read","edit","proposals","Academic","requirements","formatting","journal","chi"]