[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D5CAY4RX6HWRBDMKC36PJY":3,"skill-same:01M7D5CAY4RX6HWRBDMKC36PJY":79},{"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":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":65,"install":66,"resources":78},"01M7D5CAY4RX6HWRBDMKC36PJY","github-dashboard",null,"GitHub repository analytics dashboard — stars, forks, contributors,\nissues, pull requests, recent activity, and top contributors. Use when\nthe brief asks for a GitHub repo dashboard, open-source growth report,\nrepository health page, or GitHub analytics view.","feimacode\u002Fopen-design-agent-kit","feimacode","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F264390570?v=4","01M7D3HQSP5EP4Z4JECTSQ7EBD","Feima Code","01M7D3HQT72Q4EVQJP89MR9WP1",1129,"MIT","https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fcontent\u002Fassets\u002Fopen-design\u002Fdesign-templates\u002Fgithub-dashboard\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: github-dashboard\ndescription: |\n  GitHub repository analytics dashboard — stars, forks, contributors,\n  issues, pull requests, recent activity, and top contributors. Use when\n  the brief asks for a GitHub repo dashboard, open-source growth report,\n  repository health page, or GitHub analytics view.\ntriggers:\n  - \"github dashboard\"\n  - \"repo dashboard\"\n  - \"repository dashboard\"\n  - \"github analytics\"\n  - \"open source dashboard\"\n  - \"github growth\"\n  - \"仓库看板\"\n  - \"GitHub 看板\"\nod:\n  mode: prototype\n  platform: desktop\n  scenario: operation\n  preview:\n    type: html\n    entry: index.html\n  design_system:\n    requires: true\n    sections: [color, typography, layout, components]\n  outputs:\n    primary: index.html\n    secondary:\n      - template.html\n      - data.json\n      - artifact.json\n      - provenance.json\n  capabilities_required:\n    - shell\n    - file_write\n  example_prompt: \"Build a GitHub dashboard for nexu-io\u002Fopen-design — stars, forks, contributors, issues, PRs, recent activity, and top contributors.\"\n---\n\n# GitHub Dashboard Skill\n\nCreate a single-screen GitHub repository analytics dashboard in the FlowAI \u002F Soft Paper Workspace visual style: warm off-white canvas, white rounded panels, a fixed left sidebar, compact KPI cards, pastel pills, dense tables, and low-contrast hairlines.\n\n## Resource map\n\n```\ngithub-dashboard\u002F\n├── SKILL.md\n├── example.html                         ← rendered reference dashboard\n└── references\u002F\n    ├── template.html                    ← live-artifact-compatible HTML template\n    ├── example-data.json                ← normalized public GitHub data shape\n    ├── artifact-example.json            ← minimal live-artifact create input\n    └── provenance-example.json          ← safe source\u002Fprovenance example\n```\n\n## When to use this skill\n\nUse this when the user asks for a dashboard or report about a single GitHub repository, for example:\n\n- repository growth dashboard\n- open-source project health report\n- GitHub stars \u002F forks \u002F contributors analytics\n- issue and pull-request activity page\n- maintainer \u002F contributor dashboard\n\nIf the user asks for refreshability, source auditability, or scheduled updates, produce the live-artifact source set (`template.html`, `data.json`, `artifact.json`, `provenance.json`) and follow the `live-artifact` contract. If they only need a visual artifact, produce a self-contained `index.html`.\n\n## Workflow\n\n1. **Resolve repository scope**\n   - Parse `owner\u002Frepo` from the brief.\n   - This v1 skill is scoped to one repository. If multiple repositories are requested, ask the user to pick the primary repository or create one dashboard per repository.\n   - If the repo is missing, ask one concise question for the GitHub URL or `owner\u002Frepo`.\n\n2. **Collect public GitHub data**\n   - Prefer GitHub CLI\u002FAPI for public repository data when available.\n   - Current stars\u002Fforks\u002Fwatchers\u002Fopen issue count: `GET \u002Frepos\u002F{owner}\u002F{repo}` (`stargazers_count`, `forks_count`, `watchers_count`, `open_issues_count`).\n   - Contributors: paginate `GET \u002Frepos\u002F{owner}\u002F{repo}\u002Fcontributors?per_page=100&page=N`, sort by `contributions` descending, and take the top N used by the dashboard. If only page 1 is available, label totals as first-page estimates.\n   - Issues: use GitHub Search API (`repo:{owner}\u002F{repo} is:issue`) for total counts, or paginate `GET \u002Frepos\u002F{owner}\u002F{repo}\u002Fissues?state=all` and filter out items with a `pull_request` field.\n   - Pull requests: use GitHub Search API (`repo:{owner}\u002F{repo} is:pr`) for total counts, or paginate `GET \u002Frepos\u002F{owner}\u002F{repo}\u002Fpulls?state=all` and count pages via the `Link` header.\n   - Recent activity: combine the newest issues and pull requests, normalize them into display-ready rows, and cap the preview list at 5–10 items.\n   - Growth\u002Fdelta metrics: GitHub REST does not expose complete historical star\u002Ffork deltas. Use GraphQL, stargazer event snapshots, the Events API where available, or explicitly mark deltas as estimated\u002Fsynthetic in `provenance.json`.\n   - Do not store auth tokens, raw HTTP envelopes, cookies, rate-limit headers, or private metadata.\n\n3. **Normalize into dashboard data**\n   - Required `repository`: `name`, `fullName`, `url`, `description`, `language`, `license`, `created`, `lastUpdated`.\n   - Required `metrics`: stars, forks, contributors, issues, pull requests. Store display-ready totals plus small deltas or growth notes.\n   - Required `contributors`: top 5–8 contributors with `login`, `avatar`, and `contributions`.\n   - Required `recentActivity`: display-ready rows with `title`, `typeText`, `typeClass`, `label`, `labelClass`, `author`, `authorAvatar`, and `updated`. Do not rely on template conditionals for issue\u002FPR switching.\n   - Chart data can be synthetic only when GitHub does not expose the exact history; document the transformation in provenance.\n\n4. **Apply the visual system**\n   - Use the active `DESIGN.md` tokens when present.\n   - If no design system is provided, use the Soft Paper defaults reflected in `references\u002Ftemplate.html`: `#F2F2F0` canvas, white cards, `#ECECEA` borders, `#0A0A0A` ink, Geist\u002FInter typography, 256px sidebar, 48px topbar, and 16px card radius.\n   - Keep color small and semantic: green for healthy metrics, amber for warning, blue for feature\u002FPR labels, red only for defects or risk.\n\n5. **Lay out the page**\n   - Shell: 256px sidebar + main panel, both white, rounded 16px, 1px hairline border.\n   - Topbar: repo context on the left, refresh\u002Fexport\u002Faction affordances on the right.\n   - Header: repository name, description, and date\u002Fsettings\u002Factions row.\n   - KPI strip: 5 compact cards for stars, forks, contributors, issues, PRs.\n   - Main grid: 2fr\u002F1fr split with a growth chart or activity table on the left and top contributors\u002Fhealth cards on the right.\n   - Footer: provenance\u002Flast-updated note in small muted text.\n\n6. **Write the artifact**\n   - For a static artifact, write one self-contained `index.html` with inline CSS and no external JS libraries.\n   - For a live artifact, write `template.html`, `data.json`, `artifact.json`, and `provenance.json`; `index.html` is derived by the daemon.\n   - Tag major regions with stable `data-od-id` values: `sidebar`, `topbar`, `repo-header`, `kpi-strip`, `growth-chart`, `contributors`, `activity`, `provenance`.\n\n## Visual rules\n\n- Light mode only.\n- 256px fixed sidebar on desktop; stack on narrow screens.\n- 4 or 5 KPI cards in the first row.\n- Use tabular lining numerals for all counts.\n- Avatars are circular, 28–32px in tables and contributor lists.\n- Tables use 13px body text, 11px uppercase column labels, 1px row dividers.\n- Cards use hairline borders and a barely visible shadow at most: `0 1px 2px rgba(10,10,10,.04), 0 1px 1px rgba(10,10,10,.02)`.\n- Do not use gradients except tiny workflow\u002Frepo icon placeholders.\n- Do not make the page look like GitHub itself. This is a custom operational dashboard, not a GitHub UI clone.\n\n## Self-check\n\n- Every metric has a source or a provenance note.\n- No private data or credentials are persisted.\n- Data labels are specific to the repository, not placeholders.\n- The screen still reads clearly at 50% zoom.\n- The dashboard uses at most one solid black primary action per area.\n- Status labels and issue\u002FPR chips are pastel pills, not saturated badges.\n","# GitHub Dashboard Skill\n\nCreate a single-screen GitHub repository analytics dashboard in the FlowAI \u002F Soft Paper Workspace visual style: warm off-white canvas, white rounded panels, a fixed left sidebar, compact KPI cards, pastel pills, dense tables, and low-contrast hairlines.\n\n## Resource map\n\n```\ngithub-dashboard\u002F\n├── SKILL.md\n├── example.html                         ← rendered reference dashboard\n└── references\u002F\n    ├── template.html                    ← live-artifact-compatible HTML template\n    ├── example-data.json                ← normalized public GitHub data shape\n    ├── artifact-example.json            ← minimal live-artifact create input\n    └── provenance-example.json          ← safe source\u002Fprovenance example\n```\n\n## When to use this skill\n\nUse this when the user asks for a dashboard or report about a single GitHub repository, for example:\n\n- repository growth dashboard\n- open-source project health report\n- GitHub stars \u002F forks \u002F contributors analytics\n- issue and pull-request activity page\n- maintainer \u002F contributor dashboard\n\nIf the user asks for refreshability, source auditability, or scheduled updates, produce the live-artifact source set (`template.html`, `data.json`, `artifact.json`, `provenance.json`) and follow the `live-artifact` contract. If they only need a visual artifact, produce a self-contained `index.html`.\n\n## Workflow\n\n1. **Resolve repository scope**\n   - Parse `owner\u002Frepo` from the brief.\n   - This v1 skill is scoped to one repository. If multiple repositories are requested, ask the user to pick the primary repository or create one dashboard per repository.\n   - If the repo is missing, ask one concise question for the GitHub URL or `owner\u002Frepo`.\n\n2. **Collect public GitHub data**\n   - Prefer GitHub CLI\u002FAPI for public repository data when available.\n   - Current stars\u002Fforks\u002Fwatchers\u002Fopen issue count: `GET \u002Frepos\u002F{owner}\u002F{repo}` (`stargazers_count`, `forks_count`, `watchers_count`, `open_issues_count`).\n   - Contributors: paginate `GET \u002Frepos\u002F{owner}\u002F{repo}\u002Fcontributors?per_page=100&page=N`, sort by `contributions` descending, and take the top N used by the dashboard. If only page 1 is available, label totals as first-page estimates.\n   - Issues: use GitHub Search API (`repo:{owner}\u002F{repo} is:issue`) for total counts, or paginate `GET \u002Frepos\u002F{owner}\u002F{repo}\u002Fissues?state=all` and filter out items with a `pull_request` field.\n   - Pull requests: use GitHub Search API (`repo:{owner}\u002F{repo} is:pr`) for total counts, or paginate `GET \u002Frepos\u002F{owner}\u002F{repo}\u002Fpulls?state=all` and count pages via the `Link` header.\n   - Recent activity: combine the newest issues and pull requests, normalize them into display-ready rows, and cap the preview list at 5–10 items.\n   - Growth\u002Fdelta metrics: GitHub REST does not expose complete historical star\u002Ffork deltas. Use GraphQL, stargazer event snapshots, the Events API where available, or explicitly mark deltas as estimated\u002Fsynthetic in `provenance.json`.\n   - Do not store auth tokens, raw HTTP envelopes, cookies, rate-limit headers, or private metadata.\n\n3. **Normalize into dashboard data**\n   - Required `repository`: `name`, `fullName`, `url`, `description`, `language`, `license`, `created`, `lastUpdated`.\n   - Required `metrics`: stars, forks, contributors, issues, pull requests. Store display-ready totals plus small deltas or growth notes.\n   - Required `contributors`: top 5–8 contributors with `login`, `avatar`, and `contributions`.\n   - Required `recentActivity`: display-ready rows with `title`, `typeText`, `typeClass`, `label`, `labelClass`, `author`, `authorAvatar`, and `updated`. Do not rely on template conditionals for issue\u002FPR switching.\n   - Chart data can be synthetic only when GitHub does not expose the exact history; document the transformation in provenance.\n\n4. **Apply the visual system**\n   - Use the active `DESIGN.md` tokens when present.\n   - If no design system is provided, use the Soft Paper defaults reflected in `references\u002Ftemplate.html`: `#F2F2F0` canvas, white cards, `#ECECEA` borders, `#0A0A0A` ink, Geist\u002FInter typography, 256px sidebar, 48px topbar, and 16px card radius.\n   - Keep color small and semantic: green for healthy metrics, amber for warning, blue for feature\u002FPR labels, red only for defects or risk.\n\n5. **Lay out the page**\n   - Shell: 256px sidebar + main panel, both white, rounded 16px, 1px hairline border.\n   - Topbar: repo context on the left, refresh\u002Fexport\u002Faction affordances on the right.\n   - Header: repository name, description, and date\u002Fsettings\u002Factions row.\n   - KPI strip: 5 compact cards for stars, forks, contributors, issues, PRs.\n   - Main grid: 2fr\u002F1fr split with a growth chart or activity table on the left and top contributors\u002Fhealth cards on the right.\n   - Footer: provenance\u002Flast-updated note in small muted text.\n\n6. **Write the artifact**\n   - For a static artifact, write one self-contained `index.html` with inline CSS and no external JS libraries.\n   - For a live artifact, write `template.html`, `data.json`, `artifact.json`, and `provenance.json`; `index.html` is derived by the daemon.\n   - Tag major regions with stable `data-od-id` values: `sidebar`, `topbar`, `repo-header`, `kpi-strip`, `growth-chart`, `contributors`, `activity`, `provenance`.\n\n## Visual rules\n\n- Light mode only.\n- 256px fixed sidebar on desktop; stack on narrow screens.\n- 4 or 5 KPI cards in the first row.\n- Use tabular lining numerals for all counts.\n- Avatars are circular, 28–32px in tables and contributor lists.\n- Tables use 13px body text, 11px uppercase column labels, 1px row dividers.\n- Cards use hairline borders and a barely visible shadow at most: `0 1px 2px rgba(10,10,10,.04), 0 1px 1px rgba(10,10,10,.02)`.\n- Do not use gradients except tiny workflow\u002Frepo icon placeholders.\n- Do not make the page look like GitHub itself. This is a custom operational dashboard, not a GitHub UI clone.\n\n## Self-check\n\n- Every metric has a source or a provenance note.\n- No private data or credentials are persisted.\n- Data labels are specific to the repository, not placeholders.\n- The screen still reads clearly at 50% zoom.\n- The dashboard uses at most one solid black primary action per area.\n- Status labels and issue\u002FPR chips are pastel pills, not saturated badges.\n",{"od":24,"name":5,"triggers":48,"description":57},{"mode":25,"outputs":26,"preview":33,"platform":35,"scenario":36,"design_system":37,"example_prompt":44,"capabilities_required":45},"prototype",{"primary":27,"secondary":28},"index.html",[29,30,31,32],"template.html","data.json","artifact.json","provenance.json",{"type":34,"entry":27},"html","desktop","operation",{"requires":38,"sections":39},true,[40,41,42,43],"color","typography","layout","components","Build a GitHub dashboard for nexu-io\u002Fopen-design — stars, forks, contributors, issues, PRs, recent activity, and top contributors.",[46,47],"shell","file_write",[49,50,51,52,53,54,55,56],"github dashboard","repo dashboard","repository dashboard","github analytics","open source dashboard","github growth","仓库看板","GitHub 看板","GitHub repository analytics dashboard — stars, forks, contributors,\nissues, pull requests, recent activity, and top contributors. Use when\nthe brief asks for a GitHub repo dashboard, open-source growth report,\nrepository health page, or GitHub analytics view.\n","main","e38061066b92c298798dbddc1decbae8c026464f","packages\u002Fcontent\u002Fassets\u002Fopen-design\u002Fdesign-templates\u002Fgithub-dashboard",104,"https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit","https:\u002F\u002Fmarketplace.visualstudio.com\u002Fitems?itemName=feima.open-design-agent-kit","https:\u002F\u002Fgithub.com\u002Ffeimacode","2026-11-14 17:32:48",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":38},[68,71,74],{"tool":69,"command":70},"npx","npx skills add feimacode\u002Fopen-design-agent-kit --skill github-dashboard",{"tool":72,"command":73},"bunx","bunx skills add feimacode\u002Fopen-design-agent-kit --skill github-dashboard",{"tool":75,"command":76},"pnpm","pnpm dlx skills add feimacode\u002Fopen-design-agent-kit --skill github-dashboard","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fcontent\u002Fassets\u002Fopen-design\u002Fdesign-templates\u002Fgithub-dashboard\u002FSKILL.md",[],[80,87,94,101,108,115],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7DDR9C4RR6E8F46YBJ8MW64","youtube-clipper","YouTube clip generation and editing with automated workflows — pull source video, slice highlights, add captions, and export.","https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Fyoutube-clipper\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7DDR57XHXAFBGKX3SYTGSJB","writing-guidelines","Review docs\u002Fprose for Writing Guidelines compliance. Use when asked to \"review my docs\", \"check writing style\", \"audit prose\", \"review docs voice and tone\", or \"check this page against the writing handbook\".","https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Fwriting-guidelines\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7DDR2RM4F3FM5642JZBGJSF","wpds","WordPress Design System. Apply WordPress's official design tokens, typography, and component patterns to themes and sites.","https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Fwpds\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7DDQX3G9QDCBV5GGZGQ1NZN","weread-year-in-review-video-template","WeRead-inspired HyperFrames video template for vertical annual reading reports,\npersonal reading dashboards, book-note recaps, and shareable year-in-review\nstories. Use when users want a 9:16 HTML-to-MP4 reading report with warm paper\ntexture, editorial Chinese typography, book-page metaphors, data highlights,\nand deterministic motion.","https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Fweread-year-in-review-video-template\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M7DDQRGJEHQST6TXDH6ZAV5G","web-design-guidelines","Review UI code for Web Interface Guidelines compliance by the Vercel engineering team. Covers layout, typography, color, motion, and accessibility for product UI.","https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M7DDQKADVPZW1Z1HTVKXY542","web-clone","网站复刻 \u002F 克隆方法论。USE WHEN 用户说 复刻网站、克隆网站、clone website、抄个站、仿站、 照着这个站做一个、reproduce site、还原某个网页效果、把这个站搬下来改成我的、 复刻某个交互\u002FWebGL\u002FCanvas\u002FThree.js 效果。提供「先拿真源码 → 判路径 → 逆向拆解 → 搭工程 → 替换内容」的可移植决策树，覆盖静态站 \u002F React-Vue-Next 内容站 \u002F WebGL-Canvas 重前端站三大分支，并强制核对任何 AI 二手分析里的可执行代码。","https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Fweb-clone\u002FSKILL.md",[],[]]