[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BZJTY9NMXE1Q9P0532T8SA":3,"skill-same:01M6BZJTY9NMXE1Q9P0532T8SA":70},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":28,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M6BZJTY9NMXE1Q9P0532T8SA","create-readme",null,"Write and maintain project READMEs. Use when asked to create, write, improve, update, change, or edit a README or README.md file.","kevinpita\u002Fnixos-config","kevinpita","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F69063372?v=4","01M6BZJR13Z5W16BAEMFMYVMM9","Kevin Pita","01M6BZJR54MJV1NKJFPQT0FQYJ",1,"MIT","https:\u002F\u002Fgithub.com\u002Fkevinpita\u002Fnixos-config\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fcreate-readme\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fkevinpita\u002Fnixos-config\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fcreate-readme\u002FSKILL.md",[],[20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"create","create readme","README","when","github","tree","project","maintain","main","use","edit","write","improve","file","https","update","copilot","change","2026-11-10 10:12:30",false,"---\nname: create-readme\ndescription: Write and maintain project READMEs. Use when asked to create, write, improve, update, change, or edit a README or README.md file.\nlicense: MIT\nmetadata:\n  source: https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Ftree\u002Fmain\u002Fskills\u002Fcreate-readme\n  upstream-blob: 686e10d517b319520049a485c87cffea23ee6b9f\n---\n\n## Role\n\nYou're a senior expert software engineer with extensive experience in open source projects. You always make sure the README files you write are appealing, informative, and easy to read.\n\n## Task\n\n1. Review the project and workspace before creating a comprehensive and well-structured README.md. For improvements or changes, read the existing README and the project files relevant to the request. Keep edits within the requested scope and preserve accurate existing content rather than replacing the whole README by default.\n1. Take inspiration from these readme files for the structure, tone and content:\n   - https:\u002F\u002Fraw.githubusercontent.com\u002FAzure-Samples\u002Fserverless-chat-langchainjs\u002Frefs\u002Fheads\u002Fmain\u002FREADME.md\n   - https:\u002F\u002Fraw.githubusercontent.com\u002FAzure-Samples\u002Fserverless-recipes-javascript\u002Frefs\u002Fheads\u002Fmain\u002FREADME.md\n   - https:\u002F\u002Fraw.githubusercontent.com\u002Fsinedied\u002Frun-on-output\u002Frefs\u002Fheads\u002Fmain\u002FREADME.md\n   - https:\u002F\u002Fraw.githubusercontent.com\u002Fsinedied\u002Fsmoke\u002Frefs\u002Fheads\u002Fmain\u002FREADME.md\n1. Do not overuse emojis, and keep the readme concise and to the point.\n1. Do not include sections like \"LICENSE\", \"CONTRIBUTING\", \"CHANGELOG\", etc. There are dedicated files for those sections.\n1. Use GFM (GitHub Flavored Markdown) for formatting, and GitHub admonition syntax (https:\u002F\u002Fgithub.com\u002Forgs\u002Fcommunity\u002Fdiscussions\u002F16925) where appropriate.\n1. If you find a logo or icon for the project, use it in the readme's header.\n\nAdapted from GitHub's awesome-copilot `create-readme` skill. Local changes expand invocation to README edits and preserve the requested edit scope. See `LICENSE` for the upstream license.\n","## Role\n\nYou're a senior expert software engineer with extensive experience in open source projects. You always make sure the README files you write are appealing, informative, and easy to read.\n\n## Task\n\n1. Review the project and workspace before creating a comprehensive and well-structured README.md. For improvements or changes, read the existing README and the project files relevant to the request. Keep edits within the requested scope and preserve accurate existing content rather than replacing the whole README by default.\n1. Take inspiration from these readme files for the structure, tone and content:\n   - https:\u002F\u002Fraw.githubusercontent.com\u002FAzure-Samples\u002Fserverless-chat-langchainjs\u002Frefs\u002Fheads\u002Fmain\u002FREADME.md\n   - https:\u002F\u002Fraw.githubusercontent.com\u002FAzure-Samples\u002Fserverless-recipes-javascript\u002Frefs\u002Fheads\u002Fmain\u002FREADME.md\n   - https:\u002F\u002Fraw.githubusercontent.com\u002Fsinedied\u002Frun-on-output\u002Frefs\u002Fheads\u002Fmain\u002FREADME.md\n   - https:\u002F\u002Fraw.githubusercontent.com\u002Fsinedied\u002Fsmoke\u002Frefs\u002Fheads\u002Fmain\u002FREADME.md\n1. Do not overuse emojis, and keep the readme concise and to the point.\n1. Do not include sections like \"LICENSE\", \"CONTRIBUTING\", \"CHANGELOG\", etc. There are dedicated files for those sections.\n1. Use GFM (GitHub Flavored Markdown) for formatting, and GitHub admonition syntax (https:\u002F\u002Fgithub.com\u002Forgs\u002Fcommunity\u002Fdiscussions\u002F16925) where appropriate.\n1. If you find a logo or icon for the project, use it in the readme's header.\n\nAdapted from GitHub's awesome-copilot `create-readme` skill. Local changes expand invocation to README edits and preserve the requested edit scope. See `LICENSE` for the upstream license.\n",{"name":5,"license":15,"metadata":43,"description":7},{"source":44,"upstream-blob":45},"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Ftree\u002Fmain\u002Fskills\u002Fcreate-readme","686e10d517b319520049a485c87cffea23ee6b9f","ea91a9985d02d42cd380e5533808907c8d944234","agents\u002Fskills\u002Fcreate-readme",0,"https:\u002F\u002Fgithub.com\u002Fkevinpita\u002Fnixos-config","https:\u002F\u002Fgithub.com\u002Fkevinpita","2026-11-13 23:15:30",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add kevinpita\u002Fnixos-config --skill create-readme",{"tool":58,"command":59},"bunx","bunx skills add kevinpita\u002Fnixos-config --skill create-readme",{"tool":61,"command":62},"pnpm","pnpm dlx skills add kevinpita\u002Fnixos-config --skill create-readme","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkevinpita\u002Fnixos-config\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fcreate-readme\u002FSKILL.md",true,[66],{"path":67,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":16},"LICENSE","许可证",1060,[71,102],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":38},"01M6BZKMB3C59C2GBKEAY9KS3R","security-audit","Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full\u002Fcomprehensive\u002Fend-to-end reviews, or requested report artifacts.","https:\u002F\u002Fgithub.com\u002Fkevinpita\u002Fnixos-config\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fsecurity-audit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fkevinpita\u002Fnixos-config\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fsecurity-audit\u002FSKILL.md",[],[79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,29,99,100,101],"security audit","audit","security","for","libraries","test","research","services","cli","run","workflow","artifacts","vulnerability","review","complete","end","security guidance","codebase audit","tests","only","reviews","Tools","full",{"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":106,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":123,"publishedAt":38},"01M6BZK10ADWF0YP8CCJBDCXZ1","grafana-oss","Configure Grafana OSS — provisions dashboards from YAML, sets up data sources (Prometheus \u002F Loki \u002F Tempo \u002F Pyroscope), writes dashboard JSON with template variables, builds panel queries, assigns built-in roles (Viewer \u002F Editor \u002F Admin \u002F GrafanaAdmin), mints service-account tokens, edits grafana.ini server config, creates annotations, installs plugins via provisioning, and validates each step with a health-check curl. Use when building dashboards, configuring data sources, setting up provisioning YAML, picking a panel type, writing template variables, managing users and roles, configuring SMTP\u002FOAuth in grafana.ini, creating annotations via API, troubleshooting why a provisioned dashboard isn't showing up, or running Grafana OSS locally — even when the user says \"set up a Prometheus data source\", \"provision dashboards from git\", \"make a service account\", or \"configure SSO in OSS\" without saying \"Grafana OSS\".","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkevinpita\u002Fnixos-config\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fgrafana-oss\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fkevinpita\u002Fnixos-config\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fgrafana-oss\u002FSKILL.md",[110,115,118],{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":116,"categoryName":117,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":119,"categoryName":120,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,23,150,151,152],"grafana","grafana oss","oss","git","dashboard","SET","prometheus","sso","building dashboards","writing","OAuth","configure","api","check","health","server","admin","config","curl","template","editor","json","why","loki","sources","up","Variables","health-check","data sources"]