[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77XGPBKK9FKA717C1B383M7":3,"skill-same:01M77XGPBKK9FKA717C1B383M7":50},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M77XGPBKK9FKA717C1B383M7","dashboard-builder",null,"Build monitoring dashboards that answer real operator questions for Grafana, SigNoz, and similar platforms. Use when turning metrics into a working dashboard instead of a vanity board.","503496348-ops\u002Fmischief-production","503496348-ops","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F266905914?v=4","01M77X5J7XQWWZGT8998HDGXQM","AtomCollide","01M77X5J8V78Y3NXMY6BBC75X9",2,"MIT","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fecc-dashboard-builder\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dashboard-builder\ndescription: Build monitoring dashboards that answer real operator questions for Grafana, SigNoz, and similar platforms. Use when turning metrics into a working dashboard instead of a vanity board.\nmetadata:\n  origin: HCP direct-port adaptation\nversion: \"1.0.0\"\n---\n\n# Dashboard Builder\n\nUse this when the task is to build a dashboard people can operate from.\n\nThe goal is not \"show every metric.\" The goal is to answer:\n\n- is it healthy?\n- where is the bottleneck?\n- what changed?\n- what action should someone take?\n\n## When to Use\n\n- \"Build a Kafka monitoring dashboard\"\n- \"Create a Grafana dashboard for Elasticsearch\"\n- \"Make a SigNoz dashboard for this service\"\n- \"Turn this metrics list into a real operational dashboard\"\n\n## Guardrails\n\n- do not start from visual layout; start from operator questions\n- do not include every available metric just because it exists\n- do not mix health, throughput, and resource panels without structure\n- do not ship panels without titles, units, and sane thresholds\n\n## Workflow\n\n### 1. Define the operating questions\n\nOrganize around:\n\n- health \u002F availability\n- latency \u002F performance\n- throughput \u002F volume\n- saturation \u002F resources\n- service-specific risk\n\n### 2. Study the target platform schema\n\nInspect existing dashboards first:\n\n- JSON structure\n- query language\n- variables\n- threshold styling\n- section layout\n\n### 3. Build the minimum useful board\n\nRecommended structure:\n\n1. overview\n2. performance\n3. resources\n4. service-specific section\n\n### 4. Cut vanity panels\n\nEvery panel should answer a real question. If it does not, remove it.\n\n## Example Panel Sets\n\n### Elasticsearch\n\n- cluster health\n- shard allocation\n- search latency\n- indexing rate\n- JVM heap \u002F GC\n\n### Kafka\n\n- broker count\n- under-replicated partitions\n- messages in \u002F out\n- consumer lag\n- disk and network pressure\n\n### API gateway \u002F ingress\n\n- request rate\n- p50 \u002F p95 \u002F p99 latency\n- error rate\n- upstream health\n- active connections\n\n## Quality Checklist\n\n- [ ] valid dashboard JSON\n- [ ] clear section grouping\n- [ ] titles and units are present\n- [ ] thresholds\u002Fstatus colors are meaningful\n- [ ] variables exist for common filters\n- [ ] default time range and refresh are sensible\n- [ ] no vanity panels with no operator value\n\n## Related Skills\n\n- `research-ops`\n- `backend-patterns`\n- `terminal-ops`\n","# Dashboard Builder\n\nUse this when the task is to build a dashboard people can operate from.\n\nThe goal is not \"show every metric.\" The goal is to answer:\n\n- is it healthy?\n- where is the bottleneck?\n- what changed?\n- what action should someone take?\n\n## When to Use\n\n- \"Build a Kafka monitoring dashboard\"\n- \"Create a Grafana dashboard for Elasticsearch\"\n- \"Make a SigNoz dashboard for this service\"\n- \"Turn this metrics list into a real operational dashboard\"\n\n## Guardrails\n\n- do not start from visual layout; start from operator questions\n- do not include every available metric just because it exists\n- do not mix health, throughput, and resource panels without structure\n- do not ship panels without titles, units, and sane thresholds\n\n## Workflow\n\n### 1. Define the operating questions\n\nOrganize around:\n\n- health \u002F availability\n- latency \u002F performance\n- throughput \u002F volume\n- saturation \u002F resources\n- service-specific risk\n\n### 2. Study the target platform schema\n\nInspect existing dashboards first:\n\n- JSON structure\n- query language\n- variables\n- threshold styling\n- section layout\n\n### 3. Build the minimum useful board\n\nRecommended structure:\n\n1. overview\n2. performance\n3. resources\n4. service-specific section\n\n### 4. Cut vanity panels\n\nEvery panel should answer a real question. If it does not, remove it.\n\n## Example Panel Sets\n\n### Elasticsearch\n\n- cluster health\n- shard allocation\n- search latency\n- indexing rate\n- JVM heap \u002F GC\n\n### Kafka\n\n- broker count\n- under-replicated partitions\n- messages in \u002F out\n- consumer lag\n- disk and network pressure\n\n### API gateway \u002F ingress\n\n- request rate\n- p50 \u002F p95 \u002F p99 latency\n- error rate\n- upstream health\n- active connections\n\n## Quality Checklist\n\n- [ ] valid dashboard JSON\n- [ ] clear section grouping\n- [ ] titles and units are present\n- [ ] thresholds\u002Fstatus colors are meaningful\n- [ ] variables exist for common filters\n- [ ] default time range and refresh are sensible\n- [ ] no vanity panels with no operator value\n\n## Related Skills\n\n- `research-ops`\n- `backend-patterns`\n- `terminal-ops`\n",{"name":5,"version":24,"metadata":25,"description":7},"1.0.0",{"origin":26},"HCP direct-port adaptation","main","c9103dbad48ef3005f163584d0f2abd4591217f6","skills\u002Fecc-dashboard-builder",1,"https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production","https:\u002F\u002Fgithub.com\u002F503496348-ops","https:\u002F\u002F503496348-ops.github.io\u002Fatomcollide-product-matrix\u002F#tree","元素碰撞-AtomCollide-AI 智能体实验室 测试人专属成长社群 正式招募\r\n我们的目标很纯粹：连接每一位测试工程师\u002FAI使用探索与爱好者，让你在这里既能扎实打磨技术硬实力，也能打通职业晋升的新通路，这是一个专注于AI领域的开源组","2026-07-30 00:35:42",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add 503496348-ops\u002Fmischief-production --skill dashboard-builder",{"tool":42,"command":43},"bunx","bunx skills add 503496348-ops\u002Fmischief-production --skill dashboard-builder",{"tool":45,"command":46},"pnpm","pnpm dlx skills add 503496348-ops\u002Fmischief-production --skill dashboard-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fecc-dashboard-builder\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M77YG7NPZHE751W9QGK3H9ED","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-writing-skills\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M77YG4HPYH0GJP974DZ6KCPQ","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-writing-plans\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M77YFZW1FZ1GVC5C89NPE5M8","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-verification-before-completion\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M77YFVPWANT5VE5GWBTKHPA2","using-智械工程","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-using-superpowers\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M77YFQJAW5PX3QYSBCD3B24S","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-using-git-worktrees\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M77YFMSTB70VX8W2QHNJWYB0","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-test-driven-development\u002FSKILL.md",[],[]]