[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NVZGRMPZ0PQC0ZP9GQFG77":3,"skill-same:01M6NVZGRMPZ0PQC0ZP9GQFG77":66},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M6NVZGRMPZ0PQC0ZP9GQFG77","github-issue-creator",null,"Turn error logs, screenshots, voice notes, and rough bug reports into crisp, developer-ready GitHub issues with repro steps, impact, and evidence.","mattonweb\u002Fai-assistant-foundry","mattonweb","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2309734?v=4","01M6NQYCY846TKYN2ZCRS71WQ7","Matt Johnson","01M6NQYD2NPAQEFVD8TW9W0SVX",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fdevops-cicd\u002Fsickn33\u002Fgithub-issue-creator\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"github issue creator","creator","github issue","github","issue","reports","voice notes","unknown","with","crisp","error","impact","community","bug","repro","ready","evidence","logs","issues","notes","2026-11-10 10:12:30",false,"---\nname: github-issue-creator\ndescription: \"Turn error logs, screenshots, voice notes, and rough bug reports into crisp, developer-ready GitHub issues with repro steps, impact, and evidence.\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# GitHub Issue Creator\n\nTransform messy input (error logs, voice notes, screenshots) into clean, actionable GitHub issues.\n\n## Output Template\n\n```markdown\n\n## Summary\n[One-line description of the issue]\n\n## Environment\n- **Product\u002FService**:\n- **Region\u002FVersion**:\n- **Browser\u002FOS**: (if relevant)\n\n## Reproduction Steps\n1. [Step]\n2. [Step]\n3. [Step]\n\n## Expected Behavior\n[What should happen]\n\n## Actual Behavior\n[What actually happens]\n\n## Error Details\n```\n[Error message\u002Fcode if applicable]\n```\n\n## Visual Evidence\n[Reference to attached screenshots\u002FGIFs]\n\n## Impact\n[Severity: Critical\u002FHigh\u002FMedium\u002FLow + brief explanation]\n\n## Additional Context\n[Any other relevant details]\n```\n\n## Output Location\n\n**Create issues as markdown files** in `\u002Fissues\u002F` directory at the repo root. Use naming convention: `YYYY-MM-DD-short-description.md`\n\n## Guidelines\n\n**Be crisp**: No fluff. Every word should add value.\n\n**Extract structure from chaos**: Voice dictation and raw notes often contain the facts buried in casual language. Pull them out.\n\n**Infer missing context**: If user mentions \"same project\" or \"the dashboard\", use context from conversation or memory to fill in specifics.\n\n**Placeholder sensitive data**: Use `[PROJECT_NAME]`, `[USER_ID]`, etc. for anything that might be sensitive.\n\n**Match severity to impact**:\n- Critical: Service down, data loss, security issue\n- High: Major feature broken, no workaround\n- Medium: Feature impaired, workaround exists\n- Low: Minor inconvenience, cosmetic\n\n**Image\u002FGIF handling**: Reference attachments inline. Format: `!Description`\n\n## Examples\n\n**Input (voice dictation)**:\n> so I was trying to deploy the agent and it just failed silently no error nothing the workflow ran but then poof gone from the list had to refresh and try again three times\n\n**Output**:\n```markdown\n\n## Summary\nAgent deployment fails silently - no error displayed, agent disappears from list\n\n## Environment\n- **Product\u002FService**: Azure AI Foundry\n- **Region\u002FVersion**: westus2\n\n## Reproduction Steps\n1. Navigate to agent deployment\n2. Configure and deploy agent\n3. Observe workflow completes\n4. Check agent list\n\n## Expected Behavior\nAgent appears in list with deployment status, errors shown if deployment fails\n\n## Actual Behavior\nAgent disappears from list. No error message. Requires page refresh and retry.\n\n## Impact\n**High** - Blocks agent deployment workflow, no feedback on failure cause\n\n## Additional Context\nRequired 3 retry attempts before successful deployment\n```\n\n---\n\n**Input (error paste)**:\n> Error: PERMISSION_DENIED when publishing to Teams channel. Code: 403. Was working yesterday.\n\n**Output**:\n```markdown\n\n## Summary\n403 PERMISSION_DENIED error when publishing to Teams channel\n\n## Environment\n- **Product\u002FService**: Copilot Studio → Teams integration\n- **Region\u002FVersion**: [REGION]\n\n## Reproduction Steps\n1. Configure agent for Teams channel\n2. Attempt to publish\n\n## Expected Behavior\nAgent publishes successfully to Teams channel\n\n## Actual Behavior\nReturns `PERMISSION_DENIED` with code 403\n\n## Error Details\n```\nError: PERMISSION_DENIED\nCode: 403\n```\n\n## Impact\n**High** - Blocks Teams integration, regression from previous working state\n\n## Additional Context\nWas working yesterday - possible permission\u002Fconfig change or service regression\n```\n\n## When to Use\nUse this skill when you have unstructured bug input such as pasted errors, support notes, screenshots, or voice dictation and need to turn it into a clean GitHub issue with a summary, reproduction steps, expected vs actual behavior, impact, and attachment references.\n","# GitHub Issue Creator\n\nTransform messy input (error logs, voice notes, screenshots) into clean, actionable GitHub issues.\n\n## Output Template\n\n```markdown\n\n## Summary\n[One-line description of the issue]\n\n## Environment\n- **Product\u002FService**:\n- **Region\u002FVersion**:\n- **Browser\u002FOS**: (if relevant)\n\n## Reproduction Steps\n1. [Step]\n2. [Step]\n3. [Step]\n\n## Expected Behavior\n[What should happen]\n\n## Actual Behavior\n[What actually happens]\n\n## Error Details\n```\n[Error message\u002Fcode if applicable]\n```\n\n## Visual Evidence\n[Reference to attached screenshots\u002FGIFs]\n\n## Impact\n[Severity: Critical\u002FHigh\u002FMedium\u002FLow + brief explanation]\n\n## Additional Context\n[Any other relevant details]\n```\n\n## Output Location\n\n**Create issues as markdown files** in `\u002Fissues\u002F` directory at the repo root. Use naming convention: `YYYY-MM-DD-short-description.md`\n\n## Guidelines\n\n**Be crisp**: No fluff. Every word should add value.\n\n**Extract structure from chaos**: Voice dictation and raw notes often contain the facts buried in casual language. Pull them out.\n\n**Infer missing context**: If user mentions \"same project\" or \"the dashboard\", use context from conversation or memory to fill in specifics.\n\n**Placeholder sensitive data**: Use `[PROJECT_NAME]`, `[USER_ID]`, etc. for anything that might be sensitive.\n\n**Match severity to impact**:\n- Critical: Service down, data loss, security issue\n- High: Major feature broken, no workaround\n- Medium: Feature impaired, workaround exists\n- Low: Minor inconvenience, cosmetic\n\n**Image\u002FGIF handling**: Reference attachments inline. Format: `!Description`\n\n## Examples\n\n**Input (voice dictation)**:\n> so I was trying to deploy the agent and it just failed silently no error nothing the workflow ran but then poof gone from the list had to refresh and try again three times\n\n**Output**:\n```markdown\n\n## Summary\nAgent deployment fails silently - no error displayed, agent disappears from list\n\n## Environment\n- **Product\u002FService**: Azure AI Foundry\n- **Region\u002FVersion**: westus2\n\n## Reproduction Steps\n1. Navigate to agent deployment\n2. Configure and deploy agent\n3. Observe workflow completes\n4. Check agent list\n\n## Expected Behavior\nAgent appears in list with deployment status, errors shown if deployment fails\n\n## Actual Behavior\nAgent disappears from list. No error message. Requires page refresh and retry.\n\n## Impact\n**High** - Blocks agent deployment workflow, no feedback on failure cause\n\n## Additional Context\nRequired 3 retry attempts before successful deployment\n```\n\n---\n\n**Input (error paste)**:\n> Error: PERMISSION_DENIED when publishing to Teams channel. Code: 403. Was working yesterday.\n\n**Output**:\n```markdown\n\n## Summary\n403 PERMISSION_DENIED error when publishing to Teams channel\n\n## Environment\n- **Product\u002FService**: Copilot Studio → Teams integration\n- **Region\u002FVersion**: [REGION]\n\n## Reproduction Steps\n1. Configure agent for Teams channel\n2. Attempt to publish\n\n## Expected Behavior\nAgent publishes successfully to Teams channel\n\n## Actual Behavior\nReturns `PERMISSION_DENIED` with code 403\n\n## Error Details\n```\nError: PERMISSION_DENIED\nCode: 403\n```\n\n## Impact\n**High** - Blocks Teams integration, regression from previous working state\n\n## Additional Context\nWas working yesterday - possible permission\u002Fconfig change or service regression\n```\n\n## When to Use\nUse this skill when you have unstructured bug input such as pasted errors, support notes, screenshots, or voice dictation and need to turn it into a clean GitHub issue with a summary, reproduction steps, expected vs actual behavior, impact, and attachment references.\n",{"name":5,"risk":26,"source":31,"date_added":44,"description":7},"2026-02-27","main","d8518247cb8ab8b2dac57a6be33543ffd23b97c5","devops-cicd\u002Fsickn33\u002Fgithub-issue-creator",0,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry","https:\u002F\u002Fgithub.com\u002Fmattonweb","2026-05-29 08:42:23",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add mattonweb\u002Fai-assistant-foundry --skill github-issue-creator",{"tool":58,"command":59},"bunx","bunx skills add mattonweb\u002Fai-assistant-foundry --skill github-issue-creator",{"tool":61,"command":62},"pnpm","pnpm dlx skills add mattonweb\u002Fai-assistant-foundry --skill github-issue-creator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fdevops-cicd\u002Fsickn33\u002Fgithub-issue-creator\u002FSKILL.md",true,[],[67,102,116,134,154,180],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":83,"publishedAt":39},"01M6P02DENRHN6KVGYC55FKASJ","writing-clearly-and-concisely","Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002FSKILL.md",[73,78],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[84,85,86,87,88,89,90,29,91,92,24,93,94,95,96,97,98,99,100,101],"writing clearly and concisely","writing","concisely","text","for","more","timeless","professional","prose","use","read","Rules","commit messages","messages","error messages","ui","documentation","commit",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":39},"01M6P0286HZ8RWMFCCPC8HF7SC","crafting-effective-readmes","Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fcrafting-effective-readmes\u002FSKILL.md",[],[109,110,85,111,112,93,113,114,115],"crafting effective readmes","README","templates","type","project","guidance","files",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":125,"publishedAt":39},"01M6P025A41BBTPWVTZ3GFQVG6","wiki-architect","You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Fwiki-architect\u002FSKILL.md",[122],{"categoryNo":123,"categoryName":124,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000038","人力资源",[126,127,128,26,129,130,131,132,31,133,100],"wiki","architect","wiki architect","you","documentation architect","guides","structured","onboarding",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":39},"01M6P01NSKPXP77NWB4K0PXRK5","readme","You are an expert technical writer creating comprehensive project documentation. Your goal is to write a README.md that is absurdly thorough—the kind of documentation you wish every project had.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Freadme\u002FSKILL.md",[],[110,141,142,143,129,144,22,113,145,146,45,147,148,149,150,151,100,152,153],"project documentation","tree","kind","expert","wish","writer","goal","write","technical writer","technical","https","write a readme","safe",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":39},"01M6P01GP0NEN8KT3A3SA6ZFVE","ubiquitous-language","Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions \"domain model\" or \"DDD\".","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattpocock\u002Fubiquitous-language\u002FSKILL.md",[],[161,162,93,163,164,165,166,167,168,169,170,171,172,173,174,175,176,177,178,179],"ubiquitous language","language","extract","user","glossary","model","terms","ddd","create","build","true","canonical","style","define","harden","domain model","domain","terminology","conversation",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":188,"publishedAt":39},"01M6P01BJBP9XP4TDRT7QD1ZVA","technical-writing-style","Enforce clear, direct writing in software development documents including OKRs, PRDs, tech specs, architecture decision records (ADRs), git commit messages, PR descriptions, READMEs, changelogs, runbooks, incident postmortems, API docs, and onboarding guides. Trigger whenever a user asks to write, edit, revise, or review any of these document types. Also trigger when the user says writing \"sounds like AI\", \"feels robotic\", \"needs polish\", or asks to \"make it sound more natural\" in the context of technical or professional prose. Do not trigger for fiction, poetry, creative writing, academic papers, or legal documents unless the user explicitly asks for a more natural tone.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattnebr\u002Ftechnical-writing-style\u002FSKILL.md",[186,187],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},[189,190,173,150,85,191,91,192,193,194,195,196,197,198,199,97,200,201,101,202],"writing style","technical writing style","technical writing","papers","types","runbooks","software development","incident","Poetry","decision","api","documents","architecture","review"]