[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MZ4Q00DBMWSNS7AD429RPE":3,"skill-same:01M6MZ4Q00DBMWSNS7AD429RPE":67},{"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":17,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":13,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M6MZ4Q00DBMWSNS7AD429RPE","reference",null,"Draft reference letters and verify employment. Activate for: reference letter, reference, employment reference, character reference, professional reference, write a reference, employment verification, confirm employment, verify employment, salary verification, dates of employment, job title verification, reference request, provide a reference, reference template, letter of recommendation, HR reference, factual reference. NOT for: performance reviews (use performance-review), offer letters (use draft-offer), job descriptions (use jd).","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-reference-skill-46af5da6\u002FSKILL.md",[],[5,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"professional","title","letter","request","for","employment","reference letter","reviews","recommendation","hr","review","draft","activate","use","write","template","verify","verification","performance","2026-11-10 10:12:30",false,"---\nname: reference\ndescription: >\n  Draft reference letters and verify employment. Activate for: reference\n  letter, reference, employment reference, character reference, professional\n  reference, write a reference, employment verification, confirm employment,\n  verify employment, salary verification, dates of employment, job title\n  verification, reference request, provide a reference, reference template,\n  letter of recommendation, HR reference, factual reference.\n  NOT for: performance reviews (use performance-review), offer letters\n  (use draft-offer), job descriptions (use jd).\nlicense: Apache-2.0\nmetadata:\n  author: Panaversity\n  version: \"1.0\"\n  plugin-commands: \"\u002Freference\"\n---\n\n## UNIVERSAL RULES (apply to every reference task)\n\n- NEVER provide a reference that is inconsistent with the employee's\n  documented performance record -- this creates legal and ethical risk\n- NEVER include salary information without the employee's explicit consent\n- NEVER provide a reference that you personally do not believe to be true\n  -- if you cannot provide a positive reference, provide factual only\n- NEVER send a reference without HR review, especially for former employees\n  who left on difficult terms\n- NEVER include information about disciplinary matters, health conditions,\n  or protected characteristics in any reference\n- ALWAYS include the \"REVIEW BEFORE SENDING\" warning in every output\n\n## BEFORE IMPLEMENTATION\n\n| Source            | Check                                                                                                                                      |\n| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| **Conversation**  | Employee name, reference type requested (factual\u002Fprofessional\u002Fverification), recipient and purpose if known                                |\n| **hr.local.md**   | Reference policy (factual only vs professional permitted), company letterhead information, HR signatory details, rehire eligibility policy |\n| **Prior outputs** | None — \u002Freference is typically invoked independently                                                                                       |\n\n## CLARIFICATION QUESTIONS\n\n**Required** (ask if not provided):\n\n- Who is the reference for? (employee name)\n- What type of reference is needed? (factual \u002F professional \u002F employment verification)\n\n**Optional** (ask if context suggests value):\n\n- Who is the recipient and what is the purpose? (job application \u002F mortgage \u002F visa \u002F rental)\n- Has the employee given written consent for this reference?\n- Is there specific information the recipient has requested?\n\n**If information is missing**: Default to factual reference (safest option). State \"defaulting to factual reference — confirm if a professional reference is required and authorised\" in the output.\n\n## MANDATORY OUTPUT HEADER\n\nEvery output must begin with:\n\n```\nTASK:          Reference Letter -- [Employee Name]\nDOCUMENT TYPE: [Factual Reference \u002F Professional Reference \u002F Employment Verification]\nJURISDICTION:  [From hr.local.md or user input]\nCONFIGURATION: [hr.local.md loaded \u002F best practices]\nSENSITIVITY:   CONFIDENTIAL\n```\n\n## REFERENCE LETTER WORKFLOW\n\n### Phase 1: Check Reference Policy\n\nALWAYS check before generating:\n\n- Does this organisation's policy permit opinion references,\n  or factual only? (Load from hr.local.md)\n- Has the employee given written consent for this reference?\n- Is the content consistent with the employee's documented performance?\n- Has the reference been reviewed by HR before sending?\n\n### Phase 2: Determine Reference Type\n\nTYPE 1: FACTUAL REFERENCE (most common corporate policy)\nContents: job title, dates of employment, whether eligible for rehire\nPolicy in many organisations: HR provides factual only;\nmanagers do not provide opinion references\nALWAYS CHECK: what is this organisation's reference policy\n(from hr.local.md) before generating any content\n\nTYPE 2: FULL PROFESSIONAL REFERENCE\nContents: factual + performance assessment + specific achievements\n\n- professional recommendation\n  Requirements: written authorisation from the employee;\n  confirmation this is within the signer's authority\n\nTYPE 3: EMPLOYMENT VERIFICATION LETTER\nContents: confirms current employment status, role, and salary\n(for mortgage, visa, or rental applications)\nContents: role title; employment type; start date; current salary;\nconfirmation employment is ongoing as of letter date\nNEVER include: future salary projections; pending bonuses unless confirmed\n\n### Phase 3: Verify Facts\n\nVerify all facts against HRIS before including:\n\n- Exact dates of employment (start date and end date or \"present\")\n- Exact job title (as it appears in the employment record)\n- Salary: only include if employee has explicitly requested and consented\n- Rehire eligibility: follow the organisation's policy and process\n\n### Phase 4: Generate Reference\n\nTONE:\nProfessional and neutral.\nIf providing a positive reference: specific and evidenced.\nIf unable to provide a positive reference: stick to factual only.\nNEVER: be dishonest or misleading about performance.\nNEVER: provide a reference you cannot stand behind.\n\nLEGAL RISK:\nTwo types of legal risk with references:\n\n1. Defamation: providing false negative information about an employee\n2. Misrepresentation: providing falsely positive information that\n   influences hiring decisions; if the new employer relies on this\n   and is harmed, liability may exist\n   In both cases: stick to what you know to be factually true.\n   When in doubt: factual reference only.\n\n## OUTPUT FORMAT\n\nTYPE 1 -- FACTUAL REFERENCE:\n\n```\nTASK:          Reference Letter -- [Employee Name]\nDOCUMENT TYPE: Factual Reference\nJURISDICTION:  [Jurisdiction]\nCONFIGURATION: [hr.local.md status]\nSENSITIVITY:   CONFIDENTIAL\n\n[Date]\n\nTo Whom It May Concern \u002F [Named recipient if known]\n\nRe: [Employee Full Name]\n\nThis letter confirms that [Full Name] was employed by [Company Name]\nas [Job Title] from [Start Date] to [End Date \u002F \"the present\"].\n\n[Their employment is ongoing as of the date of this letter. \u002F\n They left the organisation on [date].]\n\n[OPTIONAL -- only if organisation policy permits and it is true:\n [Name] is eligible for re-employment at [Company Name].]\n\nThis reference is provided in a factual capacity only. For further\ninformation, please contact [HR contact name, email].\n\nYours sincerely,\n[Name, Title -- HR only for factual references]\n\nWARNING: REVIEW BEFORE SENDING -- This reference must be reviewed by HR\nbefore sending. Verify all facts against HRIS. Remove this note\nbefore issuing.\n```\n\nTYPE 2 -- FULL PROFESSIONAL REFERENCE:\n\n```\nTASK:          Reference Letter -- [Employee Name]\nDOCUMENT TYPE: Professional Reference\nJURISDICTION:  [Jurisdiction]\nCONFIGURATION: [hr.local.md status]\nSENSITIVITY:   CONFIDENTIAL\n\n[Date]\n\n[Recipient name and address]\n\nDear [Name \u002F To Whom It May Concern],\n\nRe: Reference for [Employee Full Name]\n\n[Paragraph 1: Relationship -- how long; in what capacity]\n[Paragraph 2: Performance -- 2-3 specific achievements with evidence]\n[Paragraph 3: Character and ways of working -- specific and honest]\n[Paragraph 4: Recommendation -- genuine and proportionate]\n\nI am happy to discuss this reference further if helpful.\n\nYours sincerely,\n[Name, Title, Contact details]\n\nWARNING: REVIEW BEFORE SENDING -- This reference must be reviewed by HR\nbefore sending. Verify all facts against HRIS. Remove this note\nbefore issuing.\n```\n\nTYPE 3 -- EMPLOYMENT VERIFICATION:\n\n```\nTASK:          Employment Verification -- [Employee Name]\nDOCUMENT TYPE: Employment Verification\nJURISDICTION:  [Jurisdiction]\nCONFIGURATION: [hr.local.md status]\nSENSITIVITY:   CONFIDENTIAL\n\n[Date]\n\nTo Whom It May Concern,\n\nRe: Employment Verification -- [Employee Full Name]\n\nThis letter confirms that [Full Name] is currently employed by\n[Company Name] as [Job Title] on a [full-time\u002Fpart-time] basis.\n\nStart date: [Date]\nCurrent annual salary: [Amount -- only if employee has consented]\n\nThis employment is ongoing as of the date of this letter.\n\nFor further information, please contact [HR contact name, email].\n\nYours sincerely,\n[Name, Title]\n\nWARNING: REVIEW BEFORE SENDING -- This reference must be reviewed by HR\nbefore sending. Verify all facts against HRIS. Remove this note\nbefore issuing.\n```\n\n## NEVER DO THESE\n\n- NEVER provide a reference that is inconsistent with the employee's\n  documented performance record -- this creates legal and ethical risk\n- NEVER include salary information without the employee's explicit consent\n- NEVER provide a reference that you personally do not believe to be true\n  -- if you cannot provide a positive reference, provide factual only\n- NEVER send a reference without HR review, especially for former employees\n  who left on difficult terms\n- NEVER include information about disciplinary matters, health conditions,\n  or protected characteristics in any reference\n\n## AUTHORITATIVE SOURCES\n\n- ACAS (acas.org.uk) — Guidance on providing references (UK employment law perspective)\n- SHRM (shrm.org) — Reference checking toolkit, best practices for providing employment references\n- Spring v Guardian Assurance [1995] 2 AC 296 — UK case law establishing duty of care in employment references\n- CIPD (cipd.org) — Employment references guidance for HR practitioners\n\nALL OUTPUTS REQUIRE REVIEW BY A QUALIFIED PROFESSIONAL BEFORE USE IN BUSINESS DECISIONS.\n","## UNIVERSAL RULES (apply to every reference task)\n\n- NEVER provide a reference that is inconsistent with the employee's\n  documented performance record -- this creates legal and ethical risk\n- NEVER include salary information without the employee's explicit consent\n- NEVER provide a reference that you personally do not believe to be true\n  -- if you cannot provide a positive reference, provide factual only\n- NEVER send a reference without HR review, especially for former employees\n  who left on difficult terms\n- NEVER include information about disciplinary matters, health conditions,\n  or protected characteristics in any reference\n- ALWAYS include the \"REVIEW BEFORE SENDING\" warning in every output\n\n## BEFORE IMPLEMENTATION\n\n| Source            | Check                                                                                                                                      |\n| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| **Conversation**  | Employee name, reference type requested (factual\u002Fprofessional\u002Fverification), recipient and purpose if known                                |\n| **hr.local.md**   | Reference policy (factual only vs professional permitted), company letterhead information, HR signatory details, rehire eligibility policy |\n| **Prior outputs** | None — \u002Freference is typically invoked independently                                                                                       |\n\n## CLARIFICATION QUESTIONS\n\n**Required** (ask if not provided):\n\n- Who is the reference for? (employee name)\n- What type of reference is needed? (factual \u002F professional \u002F employment verification)\n\n**Optional** (ask if context suggests value):\n\n- Who is the recipient and what is the purpose? (job application \u002F mortgage \u002F visa \u002F rental)\n- Has the employee given written consent for this reference?\n- Is there specific information the recipient has requested?\n\n**If information is missing**: Default to factual reference (safest option). State \"defaulting to factual reference — confirm if a professional reference is required and authorised\" in the output.\n\n## MANDATORY OUTPUT HEADER\n\nEvery output must begin with:\n\n```\nTASK:          Reference Letter -- [Employee Name]\nDOCUMENT TYPE: [Factual Reference \u002F Professional Reference \u002F Employment Verification]\nJURISDICTION:  [From hr.local.md or user input]\nCONFIGURATION: [hr.local.md loaded \u002F best practices]\nSENSITIVITY:   CONFIDENTIAL\n```\n\n## REFERENCE LETTER WORKFLOW\n\n### Phase 1: Check Reference Policy\n\nALWAYS check before generating:\n\n- Does this organisation's policy permit opinion references,\n  or factual only? (Load from hr.local.md)\n- Has the employee given written consent for this reference?\n- Is the content consistent with the employee's documented performance?\n- Has the reference been reviewed by HR before sending?\n\n### Phase 2: Determine Reference Type\n\nTYPE 1: FACTUAL REFERENCE (most common corporate policy)\nContents: job title, dates of employment, whether eligible for rehire\nPolicy in many organisations: HR provides factual only;\nmanagers do not provide opinion references\nALWAYS CHECK: what is this organisation's reference policy\n(from hr.local.md) before generating any content\n\nTYPE 2: FULL PROFESSIONAL REFERENCE\nContents: factual + performance assessment + specific achievements\n\n- professional recommendation\n  Requirements: written authorisation from the employee;\n  confirmation this is within the signer's authority\n\nTYPE 3: EMPLOYMENT VERIFICATION LETTER\nContents: confirms current employment status, role, and salary\n(for mortgage, visa, or rental applications)\nContents: role title; employment type; start date; current salary;\nconfirmation employment is ongoing as of letter date\nNEVER include: future salary projections; pending bonuses unless confirmed\n\n### Phase 3: Verify Facts\n\nVerify all facts against HRIS before including:\n\n- Exact dates of employment (start date and end date or \"present\")\n- Exact job title (as it appears in the employment record)\n- Salary: only include if employee has explicitly requested and consented\n- Rehire eligibility: follow the organisation's policy and process\n\n### Phase 4: Generate Reference\n\nTONE:\nProfessional and neutral.\nIf providing a positive reference: specific and evidenced.\nIf unable to provide a positive reference: stick to factual only.\nNEVER: be dishonest or misleading about performance.\nNEVER: provide a reference you cannot stand behind.\n\nLEGAL RISK:\nTwo types of legal risk with references:\n\n1. Defamation: providing false negative information about an employee\n2. Misrepresentation: providing falsely positive information that\n   influences hiring decisions; if the new employer relies on this\n   and is harmed, liability may exist\n   In both cases: stick to what you know to be factually true.\n   When in doubt: factual reference only.\n\n## OUTPUT FORMAT\n\nTYPE 1 -- FACTUAL REFERENCE:\n\n```\nTASK:          Reference Letter -- [Employee Name]\nDOCUMENT TYPE: Factual Reference\nJURISDICTION:  [Jurisdiction]\nCONFIGURATION: [hr.local.md status]\nSENSITIVITY:   CONFIDENTIAL\n\n[Date]\n\nTo Whom It May Concern \u002F [Named recipient if known]\n\nRe: [Employee Full Name]\n\nThis letter confirms that [Full Name] was employed by [Company Name]\nas [Job Title] from [Start Date] to [End Date \u002F \"the present\"].\n\n[Their employment is ongoing as of the date of this letter. \u002F\n They left the organisation on [date].]\n\n[OPTIONAL -- only if organisation policy permits and it is true:\n [Name] is eligible for re-employment at [Company Name].]\n\nThis reference is provided in a factual capacity only. For further\ninformation, please contact [HR contact name, email].\n\nYours sincerely,\n[Name, Title -- HR only for factual references]\n\nWARNING: REVIEW BEFORE SENDING -- This reference must be reviewed by HR\nbefore sending. Verify all facts against HRIS. Remove this note\nbefore issuing.\n```\n\nTYPE 2 -- FULL PROFESSIONAL REFERENCE:\n\n```\nTASK:          Reference Letter -- [Employee Name]\nDOCUMENT TYPE: Professional Reference\nJURISDICTION:  [Jurisdiction]\nCONFIGURATION: [hr.local.md status]\nSENSITIVITY:   CONFIDENTIAL\n\n[Date]\n\n[Recipient name and address]\n\nDear [Name \u002F To Whom It May Concern],\n\nRe: Reference for [Employee Full Name]\n\n[Paragraph 1: Relationship -- how long; in what capacity]\n[Paragraph 2: Performance -- 2-3 specific achievements with evidence]\n[Paragraph 3: Character and ways of working -- specific and honest]\n[Paragraph 4: Recommendation -- genuine and proportionate]\n\nI am happy to discuss this reference further if helpful.\n\nYours sincerely,\n[Name, Title, Contact details]\n\nWARNING: REVIEW BEFORE SENDING -- This reference must be reviewed by HR\nbefore sending. Verify all facts against HRIS. Remove this note\nbefore issuing.\n```\n\nTYPE 3 -- EMPLOYMENT VERIFICATION:\n\n```\nTASK:          Employment Verification -- [Employee Name]\nDOCUMENT TYPE: Employment Verification\nJURISDICTION:  [Jurisdiction]\nCONFIGURATION: [hr.local.md status]\nSENSITIVITY:   CONFIDENTIAL\n\n[Date]\n\nTo Whom It May Concern,\n\nRe: Employment Verification -- [Employee Full Name]\n\nThis letter confirms that [Full Name] is currently employed by\n[Company Name] as [Job Title] on a [full-time\u002Fpart-time] basis.\n\nStart date: [Date]\nCurrent annual salary: [Amount -- only if employee has consented]\n\nThis employment is ongoing as of the date of this letter.\n\nFor further information, please contact [HR contact name, email].\n\nYours sincerely,\n[Name, Title]\n\nWARNING: REVIEW BEFORE SENDING -- This reference must be reviewed by HR\nbefore sending. Verify all facts against HRIS. Remove this note\nbefore issuing.\n```\n\n## NEVER DO THESE\n\n- NEVER provide a reference that is inconsistent with the employee's\n  documented performance record -- this creates legal and ethical risk\n- NEVER include salary information without the employee's explicit consent\n- NEVER provide a reference that you personally do not believe to be true\n  -- if you cannot provide a positive reference, provide factual only\n- NEVER send a reference without HR review, especially for former employees\n  who left on difficult terms\n- NEVER include information about disciplinary matters, health conditions,\n  or protected characteristics in any reference\n\n## AUTHORITATIVE SOURCES\n\n- ACAS (acas.org.uk) — Guidance on providing references (UK employment law perspective)\n- SHRM (shrm.org) — Reference checking toolkit, best practices for providing employment references\n- Spring v Guardian Assurance [1995] 2 AC 296 — UK case law establishing duty of care in employment references\n- CIPD (cipd.org) — Employment references guidance for HR practitioners\n\nALL OUTPUTS REQUIRE REVIEW BY A QUALIFIED PROFESSIONAL BEFORE USE IN BUSINESS DECISIONS.\n",{"name":5,"license":14,"metadata":42,"description":46},{"author":43,"version":44,"plugin-commands":45},"Panaversity","1.0","\u002Freference","Draft reference letters and verify employment. Activate for: reference letter, reference, employment reference, character reference, professional reference, write a reference, employment verification, confirm employment, verify employment, salary verification, dates of employment, job title verification, reference request, provide a reference, reference template, letter of recommendation, HR reference, factual reference. NOT for: performance reviews (use performance-review), offer letters (use draft-offer), job descriptions (use jd).\n","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-06-agentfactory-business-plugins-main-hr-operations-skills-reference-skill-46af5da6","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill reference",{"tool":59,"command":60},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill reference",{"tool":62,"command":63},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill reference","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-06-agentfactory-business-plugins-main-hr-operations-skills-reference-skill-46af5da6\u002FSKILL.md",true,[],[68,92,119,152,180,213],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":37},"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",[],[70,76,77,78,79,80,81,82,83,84,85,34,86,31,87,88,89,90,22,91],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","tool","ready","unrelated","app","scope","webmcp",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":37},"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",[],[99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118],"vardoger analyze","analyze","directory","cli","github copilot","copilot","run","update","learn","network","my style","install","conversation","me","local","github copilot cli","pipx","my","at","copilot instructions",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":133,"publishedAt":37},"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",[125,130],{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":131,"categoryName":132,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000023","Skill与智能体开发",[134,135,136,137,138,139,140,141,142,143,144,145,146,31,147,148,149,150,22,151],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":161,"publishedAt":37},"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",[158],{"categoryNo":159,"categoryName":160,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000011","运维与部署",[162,163,164,165,166,167,168,169,170,31,171,172,173,174,175,176,177,178,179,22],"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":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":197,"publishedAt":37},"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",[186,189,194],{"categoryNo":187,"categoryName":188,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":190,"categoryName":191,"taxonomyType":192,"taxonomyTypeDesc":193},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",{"categoryNo":195,"categoryName":196,"taxonomyType":192,"taxonomyTypeDesc":193},"01JBSEEDCAT000000000000038","人力资源",[198,199,200,201,202,203,204,205,100,206,31,207,208,209,30,210,211,212,22,20],"search","Job Search","technical job search","technical","writing","tasks","email","parsing","interview","up","engineer","general","do","task","cv",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":219,"publishedAt":37},"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",[],[220,221,222,223,224,201,225,31,210,226,227,228,229,230,231,232,233,234,22,235],"steno mode","mode","customer","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]