[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KATSG8FHAVX73Z98KS8KAC":3,"skill-same:01M6KATSG8FHAVX73Z98KS8KAC":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":23,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M6KATSG8FHAVX73Z98KS8KAC","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.","afaizalam2003\u002FMaster-claude-skill","afaizalam2003","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F222019359?v=4","01M6K8F2XNT0HKBPF00JQ78SV3","Faiz Alam","01M6K8F31EBXAPER0EG8R9HTR5",3,"MIT","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fcontext-engine\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"engine","context","context engine","stale","suite","external api","for","conversations","calls","loading","loads","advisor","orchestration","Rules","api","enrichment","privacy","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: Md Faiz Alam\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":46,"description":7},{"author":47,"domain":36,"updated":48,"version":49,"category":50,"frameworks":51},"Md Faiz Alam",1772668800000,"1.0.0","c-level","context-loading, anonymization, context-enrichment","main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","c-level-advisor\u002Fcontext-engine",2,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill","https:\u002F\u002Fgithub.com\u002Fafaizalam2003","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fmdfaizalam2003\u002F","2026-04-01 04:35:43",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill context-engine",{"tool":66,"command":67},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill context-engine",{"tool":69,"command":70},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill context-engine","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fcontext-engine\u002FSKILL.md",true,[74],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fanonymization-protocol.md","REFERENCE","参考文档",5766,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fcontext-engine\u002Freferences\u002Fanonymization-protocol.md",[81,110,135,160,192,212],{"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":90,"publishedAt":41},"01M6KC4E8MYR9DBAZTAXHKYMMH","soc2-compliance","Use when the user asks to prepare for SOC 2 audits, map Trust Service Criteria, build control matrices, collect audit evidence, perform gap analysis, or assess SOC 2 Type I vs Type II readiness.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fsoc2-compliance\u002FSKILL.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务",[91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,30],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","analysis","use","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":41},"01M6KC461R3GKGZ1TAYHVR1MW9","risk-management-specialist","Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[117,118,119,120,121,122,123,124,98,99,125,126,127,128,129,130,131,132,133,134],"risk","risk management specialist","management","risk management","risk evaluation","product","Evaluation","lifecycle","risk matrix","iso","medical","iso 14971","identification","information","post-production","tree","matrix","implementing",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":41},"01M6KC3HF5ZFSSP2NZF68PEPFB","regulatory-affairs-head","Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[142,143,144,145,146,147,148,149,150,99,151,152,153,154,155,156,157,158,159,30],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","strategy","standards","queries","manage","strategies","de","users","respond","medical devices","manager",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":174,"publishedAt":41},"01M6KC34Z8M1559EY1CXYBJB1A","quality-manager-qms-iso13485","ISO 13485 Quality Management System implementation and maintenance for medical device organizations. Provides QMS design, documentation control, internal auditing, CAPA management, and certification support. Use when working with medical device quality systems, preparing for ISO 13485 audits, managing regulatory compliance documentation, setting up corrective actions, or building audit preparation programs. Useful for quality management, audit preparation, regulatory compliance, medical device documentation, and corrective action workflows.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[166,171],{"categoryNo":167,"categoryName":168,"taxonomyType":169,"taxonomyTypeDesc":170},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":172,"categoryName":173,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",[175,176,159,177,178,179,180,181,182,99,183,184,185,186,187,188,189,190,30,191],"quality manager qms iso13485","quality","design","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"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":199,"publishedAt":41},"01M6KC2FXHBHXYX2ZZ17Y3GDB4","quality-manager-qmr","Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[198],{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},[200,176,159,201,202,203,204,205,91,206,182,207,143,208,209,210,126,187,30,211],"quality manager qmr","review","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":213,"name":214,"nameZh":6,"description":215,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":216,"categories":217,"keywords":225,"publishedAt":41},"01M6KC1VRR5JTDBNZANHPS6VR6","quality-documentation-manager","Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[218,221,224],{"categoryNo":219,"categoryName":220,"taxonomyType":169,"taxonomyTypeDesc":170},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":222,"categoryName":223,"taxonomyType":169,"taxonomyTypeDesc":170},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},[226,227,176,159,201,228,229,95,182,230,231,232,233,234,127,235,236,237,238,30],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]