[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M755ZMW16WTTZAP9F4WNKAM6":3,"skill-same:01M755ZMW16WTTZAP9F4WNKAM6":48},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M755ZMW16WTTZAP9F4WNKAM6","draft-reply",null,"Use when a triaged inquiry needs an on-brand customer reply drafted.","RiggdAI\u002Funiqent","RiggdAI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82457542?v=4","01M755YEGG7892WA29CMNREQ8P","Riggd","01M755YEHK8N0QR3438XAD52TG",15,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FRiggdAI\u002Funiqent\u002Fblob\u002Fmain\u002Fexamples\u002Fsupport-concierge\u002Fskills\u002Fdraft-reply\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: draft-reply\ndescription: Use when a triaged inquiry needs an on-brand customer reply drafted.\n---\n\n# Draft Reply\n\n1. Start by acknowledging the customer's specific situation in one sentence — name the problem, not just the emotion.\n2. Consult the [[knowledge-base]] for the relevant policy or answer before writing anything. Cite the policy section if it helps the customer understand.\n3. State clearly what will happen next and by when. Do not over-promise: if a timeline is uncertain, say so.\n4. Match the customer's language (as determined by triage). Keep the reply concise — two to four short paragraphs maximum.\n5. Close with a single, specific next-step offer (e.g. \"Reply here if you'd like me to start the return\" rather than a generic \"Let me know if I can help\").\n6. Never include internal ticket IDs, employee names, or internal tooling names in the reply.\n","# Draft Reply\n\n1. Start by acknowledging the customer's specific situation in one sentence — name the problem, not just the emotion.\n2. Consult the [[knowledge-base]] for the relevant policy or answer before writing anything. Cite the policy section if it helps the customer understand.\n3. State clearly what will happen next and by when. Do not over-promise: if a timeline is uncertain, say so.\n4. Match the customer's language (as determined by triage). Keep the reply concise — two to four short paragraphs maximum.\n5. Close with a single, specific next-step offer (e.g. \"Reply here if you'd like me to start the return\" rather than a generic \"Let me know if I can help\").\n6. Never include internal ticket IDs, employee names, or internal tooling names in the reply.\n",{"name":5,"description":7},"main","64663429d4fc6dd5465e46543aa1c7e5e0a62e4a","examples\u002Fsupport-concierge\u002Fskills\u002Fdraft-reply",0,"https:\u002F\u002Fgithub.com\u002FRiggdAI\u002Funiqent","https:\u002F\u002Funiqent.ai","https:\u002F\u002Fgithub.com\u002FRiggdAI","https:\u002F\u002Friggd.ai","AI-powered process automation that builds custom operational AI solutions for small-to-medium enterprises","2026-10-17 17:42:23",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add RiggdAI\u002Funiqent --skill draft-reply",{"tool":40,"command":41},"bunx","bunx skills add RiggdAI\u002Funiqent --skill draft-reply",{"tool":43,"command":44},"pnpm","pnpm dlx skills add RiggdAI\u002Funiqent --skill draft-reply","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRiggdAI\u002Funiqent\u002Fblob\u002Fmain\u002Fexamples\u002Fsupport-concierge\u002Fskills\u002Fdraft-reply\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M755ZSRHFH3MWC21RWRHKDHD","triage-inquiry","Use when a new customer message arrives and needs to be classified before any reply is drafted.","https:\u002F\u002Fgithub.com\u002FRiggdAI\u002Funiqent\u002Fblob\u002Fmain\u002Fexamples\u002Fsupport-concierge\u002Fskills\u002Ftriage-inquiry\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M755ZR6V6YGJQCH9HBRJ2NWG","escalation-policy","Use when a ticket must be handed to a human agent instead of resolved by the AI.","https:\u002F\u002Fgithub.com\u002FRiggdAI\u002Funiqent\u002Fblob\u002Fmain\u002Fexamples\u002Fsupport-concierge\u002Fskills\u002Fescalation-policy\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M755ZHQA3GSVBGVA7KE83JWP","summarize","Use when asked to research a topic or summarize sources — fetch primary sources, quote precisely, cite every claim, and flag uncertainty.","https:\u002F\u002Fgithub.com\u002FRiggdAI\u002Funiqent\u002Fblob\u002Fmain\u002Fexamples\u002Fresearch-analyst\u002Fskills\u002Fsummarize\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M755ZE7SQ4RCJVKYT6E4VJFQ","shortlist","Rank screened candidates into a top-5 shortlist with evidence-based reasons and flagged gaps converted to interview questions.","https:\u002F\u002Fgithub.com\u002FRiggdAI\u002Funiqent\u002Fblob\u002Fmain\u002Fexamples\u002Frecruiter-screen\u002Fskills\u002Fshortlist\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M755ZC7CBMC8D81PX17WSNER","screen-cv","Screen a CV against a role brief, scoring evidence on each must-have and nice-to-have while ignoring bias signals.","https:\u002F\u002Fgithub.com\u002FRiggdAI\u002Funiqent\u002Fblob\u002Fmain\u002Fexamples\u002Frecruiter-screen\u002Fskills\u002Fscreen-cv\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M755Z9ZJY67EVPJ5CDRKTS37","interview-kit","Draft a structured interview kit for shortlisted candidates — questions per competency, evidence sought, and what a strong answer looks like.","https:\u002F\u002Fgithub.com\u002FRiggdAI\u002Funiqent\u002Fblob\u002Fmain\u002Fexamples\u002Frecruiter-screen\u002Fskills\u002Finterview-kit\u002FSKILL.md",[],[]]