[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MZ3WGM882GD60DH425V0P1":3,"skill-same:01M6MZ3WGM882GD60DH425V0P1":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":27,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":13,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":62,"install":63,"resources":76},"01M6MZ3WGM882GD60DH425V0P1","knowledge",null,"Capture and structure institutional knowledge before it is lost. Activate for: institutional knowledge, knowledge capture, knowledge transfer, knowledge base article, knowledge management, preserve knowledge, what do they know, departing employee knowledge, exit knowledge, succession knowledge, tacit knowledge, undocumented knowledge, before they leave, knowledge interview, knowledge extraction, document what we know, knowledge at risk, knowledge map. NOT for: policy lookup or FAQ queries (use policy-lookup), onboarding plans (use onboarding), offboarding checklists (use offboard).","JiayiV\u002Fquestion_mixing","JiayiV","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54466889?v=4","01M6JFJYYMRZ3QRGP9339JNQ2K","01M6JFJZ35KB0QVT50NAHPJA7G",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-06-agentfactory-business-plugins-main-hr-operations-skills-knowledge-skill-d9795f35\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[5,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"do","for","at","knowledge base article","policy lookup","plans","article","knowledge base","map","structure","knowledge capture","activate","exit","knowledge transfer","knowledge management","interview","risk","institutional knowledge","policy","2026-11-10 10:12:30",false,"---\nname: knowledge\ndescription: >\n  Capture and structure institutional knowledge before it is lost. Activate for:\n  institutional knowledge, knowledge capture, knowledge transfer, knowledge\n  base article, knowledge management, preserve knowledge, what do they know,\n  departing employee knowledge, exit knowledge, succession knowledge, tacit\n  knowledge, undocumented knowledge, before they leave, knowledge interview,\n  knowledge extraction, document what we know, knowledge at risk, knowledge map.\n  NOT for: policy lookup or FAQ queries (use policy-lookup),\n  onboarding plans (use onboarding), offboarding checklists (use offboard).\nlicense: Apache-2.0\nmetadata:\n  author: Panaversity\n  version: \"1.0\"\n  plugin-commands: \"\u002Fknowledge\"\n---\n\n## UNIVERSAL RULES (apply to every knowledge capture task)\n\n- NEVER treat the departing employee's account as the complete truth --\n  cross-reference with documentation and other stakeholders where possible\n- NEVER let knowledge capture become a blame session --\n  frame all capture as organisational learning, not performance review\n- NEVER classify knowledge as LOW RISK without checking whether\n  anyone else actually holds it -- \"I thought [person] knew this too\"\n  is a common and expensive mistake\n- NEVER publish a knowledge article without a reviewer confirming\n  accuracy -- mark as DRAFT until reviewed\n- NEVER skip the \"what we should NOT try again\" question --\n  this is often the most valuable institutional knowledge captured\n- ALWAYS include specific recommended actions and timeline\n\n## BEFORE IMPLEMENTATION\n\n| Source            | Check                                                                                                                                                  |\n| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |\n| **Conversation**  | Departing employee name, role, tenure, last working day, known critical knowledge areas                                                                |\n| **hr.local.md**   | HR contact directory (who conducts capture sessions), data retention policy (how long knowledge articles are kept), knowledge article storage location |\n| **Prior outputs** | None — \u002Fknowledge is typically the first skill invoked in a departure workflow                                                                         |\n\n## CLARIFICATION QUESTIONS\n\n**Required** (ask if not provided):\n\n- Who is the departing employee? (name and role)\n- When is their departure date?\n\n**Optional** (ask if context suggests value):\n\n- What are the known critical knowledge areas this person holds?\n- Has a successor been identified?\n- Is this reactive (departure confirmed) or proactive (no departure planned)?\n\n**If information is missing**: Run the full five-factor risk assessment to identify knowledge areas. Use hr.local.md defaults for session logistics and article storage. State assumptions about risk classification explicitly.\n\n## MANDATORY OUTPUT HEADER\n\nEvery output must begin with:\n\n```\nTASK:          Knowledge Capture Plan -- [Employee Name]\nDOCUMENT TYPE: Knowledge Capture Plan\nJURISDICTION:  [From hr.local.md or user input]\nCONFIGURATION: [hr.local.md loaded \u002F best practices]\nSENSITIVITY:   CONFIDENTIAL\n```\n\n## KNOWLEDGE CAPTURE WORKFLOW\n\n### Phase 1: Knowledge Risk Assessment\n\nBefore designing a capture plan, assess the risk:\n\nHIGH RISK:\n\n- Sole holder of critical knowledge (no one else knows this)\n- Knowledge is client-facing or revenue-critical\n- Departure is confirmed or imminent\n- Knowledge is undocumented\n- No successor identified or ready\n\nMEDIUM RISK:\n\n- Significant knowledge holder (others have partial knowledge)\n- Some documentation exists but incomplete\n- Departure possible in 6-12 months\n- Successor exists but not yet fully prepared\n\nLOW RISK:\n\n- Knowledge broadly distributed in team\n- Well-documented\n- Multiple holders\n- Successor fully prepared\n\nRISK SCORING (score each factor 1-3):\nTenure: \u003C2 years (1) | 2-5 years (2) | 5+ years (3)\nRole criticality: Support (1) | Specialist (2) | Leadership\u002Fsole expert (3)\nDocumentation level: Well documented (1) | Partial (2) | Undocumented (3)\nSuccessor readiness: Ready (1) | Developing (2) | None identified (3)\nClient\u002Frevenue impact: None (1) | Some (2) | Direct and significant (3)\n\nTOTAL SCORE:\n5-7: LOW RISK -- standard handover document\n8-10: MEDIUM RISK -- 2 knowledge capture sessions; 3-4 knowledge articles\n11-15: HIGH RISK -- full capture programme; 3+ sessions; immediate escalation\n\n### Phase 2: Proactive vs. Reactive Capture\n\nREACTIVE (triggered by departure): Urgent; comprehensive; time-limited\nGenerate a knowledge capture plan immediately on resignation.\nPrioritise: what is ONLY in this person's head?\n\nPROACTIVE (no departure planned): Systematic; can be thorough\nAnnual knowledge review for HIGH-risk knowledge holders.\nFocus on the knowledge most likely to be lost if departure occurs.\nBuild knowledge articles over time, not all at once.\n\n### Phase 3: Generate Capture Plan\n\nFor each knowledge holder, capture plan includes:\n\nEMPLOYEE: [Name] | ROLE: [Role] | TENURE: [Years] | RISK: [H\u002FM\u002FL]\nKEY KNOWLEDGE AREAS (ranked by risk):\n\n1. [Area -- describe what makes this knowledge unique or hard to replace]\n2. [Area]\n3. [Area]\n\nCAPTURE METHOD:\n\n- Interview-based (recommended for complex tacit knowledge)\n- Document review (for knowledge that IS documented but needs curation)\n- Shadowing \u002F observation (for procedural or behavioural knowledge)\n- Pair working (for technical or skills transfer)\n\nSESSIONS RECOMMENDED:\n[N] sessions x [duration] = [total hours]\nSession 1: [Knowledge area] -- [Method] -- [Date]\nSession 2: [Knowledge area] -- [Method] -- [Date]\n\nOUTPUTS:\n[Document type] -- [Title] -- [Target completion]\n\n### Phase 4: Knowledge Interview Guide\n\nOPENING (5 minutes):\n\"The goal of this session is to make sure the knowledge and\ninsights you've built up over [N] years here don't disappear\nwhen you leave. There are no wrong answers -- we want what's\nin your head, not what's in the documents.\"\n\nCORE QUESTIONS (by knowledge area):\n\nFOR CLIENT \u002F STAKEHOLDER KNOWLEDGE:\n\n- \"Tell me about [client\u002Fstakeholder]. Who are the real decision-makers\n  -- not just the named contacts but the people whose opinion actually counts?\"\n- \"What has gone wrong in this relationship and how was it recovered?\n  What would you do differently?\"\n- \"What are the unwritten rules? Things that aren't in any document\n  but that the next person needs to know?\"\n- \"What does [client\u002Fstakeholder] actually care about most?\n  Not what the contract says -- what makes them feel it's working?\"\n\nFOR PROCESS \u002F METHODOLOGY KNOWLEDGE:\n\n- \"Our process says [X]. Where does reality differ from the documentation?\"\n- \"What are the early warning signs that something is going wrong?\n  The signals you've learned to watch for?\"\n- \"What decisions do you make yourself vs. escalate?\n  Walk me through a recent example.\"\n- \"If I followed our documented process exactly, what would I get wrong?\"\n\nFOR ORGANISATIONAL \u002F CONTEXT KNOWLEDGE:\n\n- \"What would you tell someone starting your role tomorrow\n  that is not in any document?\"\n- \"What has this organisation tried that didn't work,\n  and why? What should we not try again?\"\n- \"Who are the internal stakeholders I need to manage carefully?\n  What do I need to know about each of them?\"\n- \"What are you most worried we'll get wrong after you leave?\"\n- \"If you were staying, what would you do in the next 12 months\n  that we haven't done yet?\"\n\nCLOSING:\n\"Is there anything we haven't talked about that you think\nis important for the next person to know?\"\n\n### Phase 5: Knowledge Article Structure (output from sessions)\n\n```\nKNOWLEDGE ARTICLE: [Title]\n================================================================\nAuthor:    [Departing employee] | Captured by: [HR\u002Fmanager]\nDate:      [Date of capture] | Reviewed by: [HR] | Status: DRAFT\nCategory:  [Client \u002F Process \u002F Organisational \u002F Technical]\nAudience:  [Successor \u002F Team \u002F Whole organisation]\n\nTHE KNOWLEDGE\n[What to know -- the substance, in plain language]\n\nWHEN IT APPLIES\n[Context: when does this knowledge become relevant?]\n\nEXCEPTIONS AND EDGE CASES\n[When does the standard approach NOT apply?]\n\nRELATED CONTACTS\n[Who else holds related knowledge?]\n\nRELATED DOCUMENTS\n[What documentation exists that this supplements?]\n\nCONFIDENCE LEVEL\n[HIGH: this is definitely how it works\n MEDIUM: this is the expert's interpretation; verify with [name]\n LOW: this may be out of date; confirm with [name] before relying]\n================================================================\n```\n\n## OUTPUT FORMAT\n\n```\nTASK:          Knowledge Capture Plan -- [Employee Name]\nDOCUMENT TYPE: Knowledge Capture Plan\nJURISDICTION:  [Jurisdiction]\nCONFIGURATION: [hr.local.md status]\nSENSITIVITY:   CONFIDENTIAL\n\nKNOWLEDGE CAPTURE PLAN: [Name]\n================================================================\nRole: [Title] | Tenure: [Years] | Risk: [HIGH\u002FMEDIUM\u002FLOW]\n\nKEY KNOWLEDGE AREAS:\n  1. [Area -- what makes it unique]\n  2. [Area]\n\nCAPTURE METHOD: [Interview \u002F Document review \u002F Shadowing \u002F Pair working]\n\nSESSIONS:\n  Session 1: [Knowledge area] -- [Duration] -- [Date]\n  Session 2: [Knowledge area] -- [Duration] -- [Date]\n\nOUTPUTS:\n  [Document type] -- [Title] -- [Target date]\n\nINTERVIEW GUIDE:\n  [Questions by knowledge area -- client\u002Fprocess\u002Forganisational]\n================================================================\n```\n\n## NEVER DO THESE\n\n- NEVER treat the departing employee's account as the complete truth --\n  cross-reference with documentation and other stakeholders where possible\n- NEVER let knowledge capture become a blame session --\n  frame all capture as organisational learning, not performance review\n- NEVER classify knowledge as LOW RISK without checking whether\n  anyone else actually holds it\n- NEVER publish a knowledge article without a reviewer confirming\n  accuracy -- mark as DRAFT until reviewed\n- NEVER skip the \"what we should NOT try again\" question --\n  this is often the most valuable institutional knowledge captured\n\n## AUTHORITATIVE SOURCES\n\n- APQC (apqc.org) — Knowledge management best practices, maturity model, benchmarking data\n- Nonaka & Takeuchi, _The Knowledge-Creating Company_ (1995) — SECI model for tacit-to-explicit knowledge conversion\n- NASA Lessons Learned database (llis.nasa.gov) — Example of institutional knowledge capture at scale\n- KM World (kmworld.com) — Knowledge management industry research and case studies\n\nALL OUTPUTS REQUIRE REVIEW BY A QUALIFIED PROFESSIONAL BEFORE USE IN BUSINESS DECISIONS.\n","## UNIVERSAL RULES (apply to every knowledge capture task)\n\n- NEVER treat the departing employee's account as the complete truth --\n  cross-reference with documentation and other stakeholders where possible\n- NEVER let knowledge capture become a blame session --\n  frame all capture as organisational learning, not performance review\n- NEVER classify knowledge as LOW RISK without checking whether\n  anyone else actually holds it -- \"I thought [person] knew this too\"\n  is a common and expensive mistake\n- NEVER publish a knowledge article without a reviewer confirming\n  accuracy -- mark as DRAFT until reviewed\n- NEVER skip the \"what we should NOT try again\" question --\n  this is often the most valuable institutional knowledge captured\n- ALWAYS include specific recommended actions and timeline\n\n## BEFORE IMPLEMENTATION\n\n| Source            | Check                                                                                                                                                  |\n| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |\n| **Conversation**  | Departing employee name, role, tenure, last working day, known critical knowledge areas                                                                |\n| **hr.local.md**   | HR contact directory (who conducts capture sessions), data retention policy (how long knowledge articles are kept), knowledge article storage location |\n| **Prior outputs** | None — \u002Fknowledge is typically the first skill invoked in a departure workflow                                                                         |\n\n## CLARIFICATION QUESTIONS\n\n**Required** (ask if not provided):\n\n- Who is the departing employee? (name and role)\n- When is their departure date?\n\n**Optional** (ask if context suggests value):\n\n- What are the known critical knowledge areas this person holds?\n- Has a successor been identified?\n- Is this reactive (departure confirmed) or proactive (no departure planned)?\n\n**If information is missing**: Run the full five-factor risk assessment to identify knowledge areas. Use hr.local.md defaults for session logistics and article storage. State assumptions about risk classification explicitly.\n\n## MANDATORY OUTPUT HEADER\n\nEvery output must begin with:\n\n```\nTASK:          Knowledge Capture Plan -- [Employee Name]\nDOCUMENT TYPE: Knowledge Capture Plan\nJURISDICTION:  [From hr.local.md or user input]\nCONFIGURATION: [hr.local.md loaded \u002F best practices]\nSENSITIVITY:   CONFIDENTIAL\n```\n\n## KNOWLEDGE CAPTURE WORKFLOW\n\n### Phase 1: Knowledge Risk Assessment\n\nBefore designing a capture plan, assess the risk:\n\nHIGH RISK:\n\n- Sole holder of critical knowledge (no one else knows this)\n- Knowledge is client-facing or revenue-critical\n- Departure is confirmed or imminent\n- Knowledge is undocumented\n- No successor identified or ready\n\nMEDIUM RISK:\n\n- Significant knowledge holder (others have partial knowledge)\n- Some documentation exists but incomplete\n- Departure possible in 6-12 months\n- Successor exists but not yet fully prepared\n\nLOW RISK:\n\n- Knowledge broadly distributed in team\n- Well-documented\n- Multiple holders\n- Successor fully prepared\n\nRISK SCORING (score each factor 1-3):\nTenure: \u003C2 years (1) | 2-5 years (2) | 5+ years (3)\nRole criticality: Support (1) | Specialist (2) | Leadership\u002Fsole expert (3)\nDocumentation level: Well documented (1) | Partial (2) | Undocumented (3)\nSuccessor readiness: Ready (1) | Developing (2) | None identified (3)\nClient\u002Frevenue impact: None (1) | Some (2) | Direct and significant (3)\n\nTOTAL SCORE:\n5-7: LOW RISK -- standard handover document\n8-10: MEDIUM RISK -- 2 knowledge capture sessions; 3-4 knowledge articles\n11-15: HIGH RISK -- full capture programme; 3+ sessions; immediate escalation\n\n### Phase 2: Proactive vs. Reactive Capture\n\nREACTIVE (triggered by departure): Urgent; comprehensive; time-limited\nGenerate a knowledge capture plan immediately on resignation.\nPrioritise: what is ONLY in this person's head?\n\nPROACTIVE (no departure planned): Systematic; can be thorough\nAnnual knowledge review for HIGH-risk knowledge holders.\nFocus on the knowledge most likely to be lost if departure occurs.\nBuild knowledge articles over time, not all at once.\n\n### Phase 3: Generate Capture Plan\n\nFor each knowledge holder, capture plan includes:\n\nEMPLOYEE: [Name] | ROLE: [Role] | TENURE: [Years] | RISK: [H\u002FM\u002FL]\nKEY KNOWLEDGE AREAS (ranked by risk):\n\n1. [Area -- describe what makes this knowledge unique or hard to replace]\n2. [Area]\n3. [Area]\n\nCAPTURE METHOD:\n\n- Interview-based (recommended for complex tacit knowledge)\n- Document review (for knowledge that IS documented but needs curation)\n- Shadowing \u002F observation (for procedural or behavioural knowledge)\n- Pair working (for technical or skills transfer)\n\nSESSIONS RECOMMENDED:\n[N] sessions x [duration] = [total hours]\nSession 1: [Knowledge area] -- [Method] -- [Date]\nSession 2: [Knowledge area] -- [Method] -- [Date]\n\nOUTPUTS:\n[Document type] -- [Title] -- [Target completion]\n\n### Phase 4: Knowledge Interview Guide\n\nOPENING (5 minutes):\n\"The goal of this session is to make sure the knowledge and\ninsights you've built up over [N] years here don't disappear\nwhen you leave. There are no wrong answers -- we want what's\nin your head, not what's in the documents.\"\n\nCORE QUESTIONS (by knowledge area):\n\nFOR CLIENT \u002F STAKEHOLDER KNOWLEDGE:\n\n- \"Tell me about [client\u002Fstakeholder]. Who are the real decision-makers\n  -- not just the named contacts but the people whose opinion actually counts?\"\n- \"What has gone wrong in this relationship and how was it recovered?\n  What would you do differently?\"\n- \"What are the unwritten rules? Things that aren't in any document\n  but that the next person needs to know?\"\n- \"What does [client\u002Fstakeholder] actually care about most?\n  Not what the contract says -- what makes them feel it's working?\"\n\nFOR PROCESS \u002F METHODOLOGY KNOWLEDGE:\n\n- \"Our process says [X]. Where does reality differ from the documentation?\"\n- \"What are the early warning signs that something is going wrong?\n  The signals you've learned to watch for?\"\n- \"What decisions do you make yourself vs. escalate?\n  Walk me through a recent example.\"\n- \"If I followed our documented process exactly, what would I get wrong?\"\n\nFOR ORGANISATIONAL \u002F CONTEXT KNOWLEDGE:\n\n- \"What would you tell someone starting your role tomorrow\n  that is not in any document?\"\n- \"What has this organisation tried that didn't work,\n  and why? What should we not try again?\"\n- \"Who are the internal stakeholders I need to manage carefully?\n  What do I need to know about each of them?\"\n- \"What are you most worried we'll get wrong after you leave?\"\n- \"If you were staying, what would you do in the next 12 months\n  that we haven't done yet?\"\n\nCLOSING:\n\"Is there anything we haven't talked about that you think\nis important for the next person to know?\"\n\n### Phase 5: Knowledge Article Structure (output from sessions)\n\n```\nKNOWLEDGE ARTICLE: [Title]\n================================================================\nAuthor:    [Departing employee] | Captured by: [HR\u002Fmanager]\nDate:      [Date of capture] | Reviewed by: [HR] | Status: DRAFT\nCategory:  [Client \u002F Process \u002F Organisational \u002F Technical]\nAudience:  [Successor \u002F Team \u002F Whole organisation]\n\nTHE KNOWLEDGE\n[What to know -- the substance, in plain language]\n\nWHEN IT APPLIES\n[Context: when does this knowledge become relevant?]\n\nEXCEPTIONS AND EDGE CASES\n[When does the standard approach NOT apply?]\n\nRELATED CONTACTS\n[Who else holds related knowledge?]\n\nRELATED DOCUMENTS\n[What documentation exists that this supplements?]\n\nCONFIDENCE LEVEL\n[HIGH: this is definitely how it works\n MEDIUM: this is the expert's interpretation; verify with [name]\n LOW: this may be out of date; confirm with [name] before relying]\n================================================================\n```\n\n## OUTPUT FORMAT\n\n```\nTASK:          Knowledge Capture Plan -- [Employee Name]\nDOCUMENT TYPE: Knowledge Capture Plan\nJURISDICTION:  [Jurisdiction]\nCONFIGURATION: [hr.local.md status]\nSENSITIVITY:   CONFIDENTIAL\n\nKNOWLEDGE CAPTURE PLAN: [Name]\n================================================================\nRole: [Title] | Tenure: [Years] | Risk: [HIGH\u002FMEDIUM\u002FLOW]\n\nKEY KNOWLEDGE AREAS:\n  1. [Area -- what makes it unique]\n  2. [Area]\n\nCAPTURE METHOD: [Interview \u002F Document review \u002F Shadowing \u002F Pair working]\n\nSESSIONS:\n  Session 1: [Knowledge area] -- [Duration] -- [Date]\n  Session 2: [Knowledge area] -- [Duration] -- [Date]\n\nOUTPUTS:\n  [Document type] -- [Title] -- [Target date]\n\nINTERVIEW GUIDE:\n  [Questions by knowledge area -- client\u002Fprocess\u002Forganisational]\n================================================================\n```\n\n## NEVER DO THESE\n\n- NEVER treat the departing employee's account as the complete truth --\n  cross-reference with documentation and other stakeholders where possible\n- NEVER let knowledge capture become a blame session --\n  frame all capture as organisational learning, not performance review\n- NEVER classify knowledge as LOW RISK without checking whether\n  anyone else actually holds it\n- NEVER publish a knowledge article without a reviewer confirming\n  accuracy -- mark as DRAFT until reviewed\n- NEVER skip the \"what we should NOT try again\" question --\n  this is often the most valuable institutional knowledge captured\n\n## AUTHORITATIVE SOURCES\n\n- APQC (apqc.org) — Knowledge management best practices, maturity model, benchmarking data\n- Nonaka & Takeuchi, _The Knowledge-Creating Company_ (1995) — SECI model for tacit-to-explicit knowledge conversion\n- NASA Lessons Learned database (llis.nasa.gov) — Example of institutional knowledge capture at scale\n- KM World (kmworld.com) — Knowledge management industry research and case studies\n\nALL OUTPUTS REQUIRE REVIEW BY A QUALIFIED PROFESSIONAL BEFORE USE IN BUSINESS DECISIONS.\n",{"name":5,"license":14,"metadata":52,"description":56},{"author":53,"version":54,"plugin-commands":55},"Panaversity","1.0","\u002Fknowledge","Capture and structure institutional knowledge before it is lost. Activate for: institutional knowledge, knowledge capture, knowledge transfer, knowledge base article, knowledge management, preserve knowledge, what do they know, departing employee knowledge, exit knowledge, succession knowledge, tacit knowledge, undocumented knowledge, before they leave, knowledge interview, knowledge extraction, document what we know, knowledge at risk, knowledge map. NOT for: policy lookup or FAQ queries (use policy-lookup), onboarding plans (use onboarding), offboarding checklists (use offboard).\n","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-06-agentfactory-business-plugins-main-hr-operations-skills-knowledge-skill-d9795f35","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill knowledge",{"tool":69,"command":70},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill knowledge",{"tool":72,"command":73},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill knowledge","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-06-agentfactory-business-plugins-main-hr-operations-skills-knowledge-skill-d9795f35\u002FSKILL.md",true,[],[78,104,130,161,189,217],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":47},"01M6NN9PJS9NHWPDG4QP93BP8F","webmcpify","Make a web app agent-ready — propose a WebMCP tool manifest, integrate, verify in a real browser, heal; unrelated code stays untouched. Use for \"webmcpify\", \"add WebMCP\", or \"expose app actions to AI agents\".","MIT","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fwebmcpify\u002FSKILL.md",[],[80,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,29,103],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","use","ready","unrelated","app","scope","webmcp",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":47},"01M6NN6KZE5RBN6NGHN2WXV1RE","vardoger-analyze","Use when the user asks to personalize the GitHub Copilot CLI assistant, adapt Copilot to their style, use vardoger, or analyze their Copilot CLI conversation history. Reads the local session directory at `~\u002F.copilot\u002Fsession-state\u002F`, extracts recurring preferences and conventions, and writes a fenced personalization block into `~\u002F.copilot\u002Fcopilot-instructions.md`. Runs entirely on the user's machine via the local `vardoger` CLI (`pipx install vardoger`); no network calls and no uploads. Triggers: 'personalize my copilot', 'analyze my copilot history', 'tailor copilot to me', 'run vardoger', 'update my copilot instructions from history', 'make copilot learn my style'.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fvardoger-analyze\u002FSKILL.md",[],[111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,30,129],"vardoger analyze","analyze","directory","cli","github copilot","copilot","run","update","learn","network","my style","install","conversation","me","local","github copilot cli","pipx","my","copilot instructions",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":142,"publishedAt":47},"01M6NN3CZGQP3XAJ04BM1NNYGT","transloadit-media-processing","Process media files (video, audio, images, documents) using Transloadit. Use when asked to encode video to HLS\u002FMP4, generate thumbnails, resize or watermark images, extract audio, concatenate clips, add subtitles, OCR documents, or run any media processing pipeline. Covers 86+ processing robots for file transformation at scale.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftransloadit-media-processing\u002FSKILL.md",[136,139],{"categoryNo":137,"categoryName":138,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":140,"categoryName":141,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[143,144,145,146,147,148,149,150,151,152,153,154,155,98,156,157,158,159,29,160],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":170,"publishedAt":47},"01M6NN28E92F9GH4WFYQ2H1Y15","terraform-azurerm-set-diff-analyzer","Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive diffs (order-only changes in Set-type attributes) and actual resource changes. Use when reviewing terraform plan output for Azure resources like Application Gateway, Load Balancer, Firewall, Front Door, NSG, and other resources with Set-type attributes that cause spurious diffs due to internal ordering changes.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fterraform-azurerm-set-diff-analyzer\u002FSKILL.md",[167],{"categoryNo":168,"categoryName":169,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[171,172,173,174,175,176,177,178,179,98,180,181,182,183,184,185,186,187,188,29],"terraform","SET","terraform azurerm set diff analyzer","diff","analyzer","diffs","azure","gateway","firewall","only","resource changes","provider","resources","load balancer","attributes","front","load","balancer",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":202,"publishedAt":47},"01M6NN1QMH2TDYWTH3XY3N5XPV","technical-job-search","Use this skill when a software engineer asks for help with job search tasks: parsing or analyzing a job description, tailoring a CV\u002Fresume, writing a cover letter, evaluating a job offer, or drafting a post-interview follow-up email. Do not activate for general career advice unrelated to an active job search action.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-job-search\u002FSKILL.md",[195,198,201],{"categoryNo":196,"categoryName":197,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":199,"categoryName":200,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},[203,204,205,206,207,208,209,210,112,43,98,211,212,213,39,28,214,215,29,216],"search","Job Search","technical job search","technical","writing","tasks","email","parsing","up","engineer","general","task","cv","letter",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":223,"publishedAt":47},"01M6NMZFA67XYS1GS09WT42235","steno-mode","Shorthand-first response compression that cuts ~40% of response tokens while preserving technical precision and exact literals. Use when the user says \"steno mode\", \"shorthand mode\", \"compressed responses\", \"token reduction\", \"brief structured output\", or invokes \u002Fsteno. Supports four compression levels: lite, brief, court, machine. Do not trigger for requests needing polished prose such as onboarding\u002Ftutorial content, stakeholder or customer-facing copy, or teaching-focused explanations.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fsteno-mode\u002FSKILL.md",[],[224,225,226,227,228,206,229,98,28,230,231,232,233,234,235,236,237,238,29,239],"steno mode","mode","customer","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]