[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ENPT1RAMWPA5HWSFV433W0":3,"skill-same:01M7ENPT1RAMWPA5HWSFV433W0":58},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7ENPT1RAMWPA5HWSFV433W0","star-history-chart",null,"Add a self-hosted \"Stargazers over time\" chart to any GitHub repo's README. GitHub now restricts the stargazers endpoint to a repo's own admins\u002Fcollaborators, so third-party live services (star-history free tier, starchart.cc) return \"Requires authentication\" for everyone. This generates a static, theme-aware SVG in-repo and auto-refreshes it weekly with a GitHub Action using the repo's own GITHUB_TOKEN. Use when the star chart in a README is broken, shows \"Requires authentication\", or you want a star history that never breaks.","marnixGeerkens\u002Frocketlauncher-claude-code","marnixGeerkens","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F143275741?v=4","01M7EJY825SFPHDDZNFDAJHCA9","Marnix Geerkens","01M7EJY82TBA6ABXJ62JWR9B9F",0,"MIT","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fgit\u002Fstar-history-chart\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: star-history-chart\ndescription: Add a self-hosted \"Stargazers over time\" chart to any GitHub repo's README. GitHub now restricts the stargazers endpoint to a repo's own admins\u002Fcollaborators, so third-party live services (star-history free tier, starchart.cc) return \"Requires authentication\" for everyone. This generates a static, theme-aware SVG in-repo and auto-refreshes it weekly with a GitHub Action using the repo's own GITHUB_TOKEN. Use when the star chart in a README is broken, shows \"Requires authentication\", or you want a star history that never breaks.\n---\n\n# Star History Chart (self-hosted, never breaks)\n\nAdd a \"Stargazers over time\" chart that renders from a static SVG committed to\nthe repo and refreshes itself weekly — no external chart service, no broken\nimages.\n\n## Why this exists\n\nGitHub now restricts the `\u002Fstargazers` endpoint to a repository's own admins and\ncollaborators. Unauthenticated requests return `{\"message\":\"Requires\nauthentication\"}`, which breaks every third-party live-chart service\n(star-history.com free tier, starchart.cc, etc.) for **all** repos. The only\nreliable fix is to generate the chart yourself with an authenticated token and\ncommit a static image. Inside GitHub Actions, the repo's own `GITHUB_TOKEN` can\nread its own stargazers, so the whole thing runs with zero secrets to configure.\n\n## What this skill sets up\n\n1. `scripts\u002Fgenerate_star_history.py` — fetches stargazers (authenticated),\n   renders a clean, light\u002Fdark-adaptive SVG.\n2. `.github\u002Fworkflows\u002Fstar-history.yml` — weekly cron + manual trigger that\n   regenerates and commits `docs\u002Fstar-history.svg`.\n3. A README section pointing at the local SVG.\n\n## Workflow\n\n### Step 1: Copy the script and workflow into the repo\n\n```bash\nmkdir -p scripts .github\u002Fworkflows docs\ncp skills\u002Fgit\u002Fstar-history-chart\u002Fscripts\u002Fgenerate_star_history.py scripts\u002Fgenerate_star_history.py\ncp skills\u002Fgit\u002Fstar-history-chart\u002Fassets\u002Fstar-history.yml .github\u002Fworkflows\u002Fstar-history.yml\n```\n\n> The script needs the `requests` package: `pip install requests`.\n> It resolves the repo from `STAR_HISTORY_REPO`, then `GITHUB_REPOSITORY`\n> (set automatically in Actions), then the `origin` git remote — so no edits\n> are required for it to work in a different repo.\n\n### Step 2: Generate the SVG once, locally\n\nUse a token that can read the repo's stargazers (as owner\u002Fcollaborator). The\nGitHub CLI provides one:\n\n```bash\nGITHUB_TOKEN=$(gh auth token) python scripts\u002Fgenerate_star_history.py\n```\n\nThis writes `docs\u002Fstar-history.svg`. For a repo with many thousands of stars the\nfirst run paginates the whole stargazer list and can take a couple of minutes.\n\nVerify it rendered (optional, macOS): `qlmanage -t -s 800 -o . docs\u002Fstar-history.svg`\n\n### Step 3: Add it to the README\n\nAdd or replace the star chart section. Point the image at the **local** SVG.\nSet the link target to wherever you want clicks to go (the repo, a docs page, or\nyour own site):\n\n```markdown\n## Stargazers over time\n[![Stargazers over time](docs\u002Fstar-history.svg)](https:\u002F\u002Fgithub.com\u002FOWNER\u002FREPO\u002Fstargazers)\n```\n\nIf replacing a broken `star-history.com` \u002F `starchart.cc` embed, swap only the\nimage URL to `docs\u002Fstar-history.svg` and keep or update the link target.\n\n### Step 4: Commit\n\n```bash\ngit add scripts\u002Fgenerate_star_history.py .github\u002Fworkflows\u002Fstar-history.yml docs\u002Fstar-history.svg README.md\ngit commit -m \"feat(readme): self-hosted stargazers chart with weekly auto-refresh\"\ngit push\n```\n\n### Step 5: (Optional) Trigger the auto-refresh now\n\nThe workflow runs every Monday at 04:00 UTC. To refresh immediately without\nwaiting: **GitHub → Actions → \"Update Star History\" → Run workflow**.\n\n## Customization\n\n- **Output path** — set `STAR_HISTORY_OUTPUT` (default `docs\u002Fstar-history.svg`).\n- **Different repo** — set `STAR_HISTORY_REPO=owner\u002Fname`.\n- **Colors \u002F size** — edit the `.line`, `.area`, `.dot` CSS and `WIDTH`\u002F`HEIGHT`\n  constants near the top of `generate_star_history.py`. The chart is\n  theme-aware via a `prefers-color-scheme: dark` block, so it looks right in\n  both GitHub light and dark modes.\n- **Refresh cadence** — edit the `cron` expression in the workflow.\n\n## Notes\n\n- No secrets to add: the workflow uses the automatic `GITHUB_TOKEN`.\n- Private repos work too, as long as the token can read the repo.\n- The script uses only `requests` plus the Python standard library.\n","# Star History Chart (self-hosted, never breaks)\n\nAdd a \"Stargazers over time\" chart that renders from a static SVG committed to\nthe repo and refreshes itself weekly — no external chart service, no broken\nimages.\n\n## Why this exists\n\nGitHub now restricts the `\u002Fstargazers` endpoint to a repository's own admins and\ncollaborators. Unauthenticated requests return `{\"message\":\"Requires\nauthentication\"}`, which breaks every third-party live-chart service\n(star-history.com free tier, starchart.cc, etc.) for **all** repos. The only\nreliable fix is to generate the chart yourself with an authenticated token and\ncommit a static image. Inside GitHub Actions, the repo's own `GITHUB_TOKEN` can\nread its own stargazers, so the whole thing runs with zero secrets to configure.\n\n## What this skill sets up\n\n1. `scripts\u002Fgenerate_star_history.py` — fetches stargazers (authenticated),\n   renders a clean, light\u002Fdark-adaptive SVG.\n2. `.github\u002Fworkflows\u002Fstar-history.yml` — weekly cron + manual trigger that\n   regenerates and commits `docs\u002Fstar-history.svg`.\n3. A README section pointing at the local SVG.\n\n## Workflow\n\n### Step 1: Copy the script and workflow into the repo\n\n```bash\nmkdir -p scripts .github\u002Fworkflows docs\ncp skills\u002Fgit\u002Fstar-history-chart\u002Fscripts\u002Fgenerate_star_history.py scripts\u002Fgenerate_star_history.py\ncp skills\u002Fgit\u002Fstar-history-chart\u002Fassets\u002Fstar-history.yml .github\u002Fworkflows\u002Fstar-history.yml\n```\n\n> The script needs the `requests` package: `pip install requests`.\n> It resolves the repo from `STAR_HISTORY_REPO`, then `GITHUB_REPOSITORY`\n> (set automatically in Actions), then the `origin` git remote — so no edits\n> are required for it to work in a different repo.\n\n### Step 2: Generate the SVG once, locally\n\nUse a token that can read the repo's stargazers (as owner\u002Fcollaborator). The\nGitHub CLI provides one:\n\n```bash\nGITHUB_TOKEN=$(gh auth token) python scripts\u002Fgenerate_star_history.py\n```\n\nThis writes `docs\u002Fstar-history.svg`. For a repo with many thousands of stars the\nfirst run paginates the whole stargazer list and can take a couple of minutes.\n\nVerify it rendered (optional, macOS): `qlmanage -t -s 800 -o . docs\u002Fstar-history.svg`\n\n### Step 3: Add it to the README\n\nAdd or replace the star chart section. Point the image at the **local** SVG.\nSet the link target to wherever you want clicks to go (the repo, a docs page, or\nyour own site):\n\n```markdown\n## Stargazers over time\n[![Stargazers over time](docs\u002Fstar-history.svg)](https:\u002F\u002Fgithub.com\u002FOWNER\u002FREPO\u002Fstargazers)\n```\n\nIf replacing a broken `star-history.com` \u002F `starchart.cc` embed, swap only the\nimage URL to `docs\u002Fstar-history.svg` and keep or update the link target.\n\n### Step 4: Commit\n\n```bash\ngit add scripts\u002Fgenerate_star_history.py .github\u002Fworkflows\u002Fstar-history.yml docs\u002Fstar-history.svg README.md\ngit commit -m \"feat(readme): self-hosted stargazers chart with weekly auto-refresh\"\ngit push\n```\n\n### Step 5: (Optional) Trigger the auto-refresh now\n\nThe workflow runs every Monday at 04:00 UTC. To refresh immediately without\nwaiting: **GitHub → Actions → \"Update Star History\" → Run workflow**.\n\n## Customization\n\n- **Output path** — set `STAR_HISTORY_OUTPUT` (default `docs\u002Fstar-history.svg`).\n- **Different repo** — set `STAR_HISTORY_REPO=owner\u002Fname`.\n- **Colors \u002F size** — edit the `.line`, `.area`, `.dot` CSS and `WIDTH`\u002F`HEIGHT`\n  constants near the top of `generate_star_history.py`. The chart is\n  theme-aware via a `prefers-color-scheme: dark` block, so it looks right in\n  both GitHub light and dark modes.\n- **Refresh cadence** — edit the `cron` expression in the workflow.\n\n## Notes\n\n- No secrets to add: the workflow uses the automatic `GITHUB_TOKEN`.\n- Private repos work too, as long as the token can read the repo.\n- The script uses only `requests` plus the Python standard library.\n",{"name":5,"description":7},"main","4e647b68aabe849e143b6950971c380f7adccdef","components\u002Fskills\u002Fgit\u002Fstar-history-chart","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code","https:\u002F\u002Frocketlauncher.ai\u002Fclaude-code","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens","CEO of Rocketlauncher.ai\r\n\r\nObsessed with AI\r\n\r\njoin  https:\u002F\u002Fwww.skool.com\u002Frocketlauncher-university\r\n👉🏻 it's free ","2026-10-13 00:52:14",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add marnixGeerkens\u002Frocketlauncher-claude-code --skill star-history-chart",{"tool":38,"command":39},"bunx","bunx skills add marnixGeerkens\u002Frocketlauncher-claude-code --skill star-history-chart",{"tool":41,"command":42},"pnpm","pnpm dlx skills add marnixGeerkens\u002Frocketlauncher-claude-code --skill star-history-chart","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fgit\u002Fstar-history-chart\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"assets\u002Fstar-history.yml","ASSET","资产文件",1696,"https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fgit\u002Fstar-history-chart\u002Fassets\u002Fstar-history.yml",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"scripts\u002Fgenerate_star_history.py","SCRIPT","脚本",7838,"https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fgit\u002Fstar-history-chart\u002Fscripts\u002Fgenerate_star_history.py",[59,66,75,82,89,96],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7EQFDF4T3K89WMFVFQVT3C8","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":71,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7EQFA5XQ0811Q4Q0WCFASZG","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7EQF4J6C2WKQWD9E2RQC6MJ","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7EQF1AT655CYYZBEQ8V6Z9D","trigger-dev","Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7EQEY9ENH0G2EJ1WD6C1CE8","slack-automation","Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fslack-automation\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7EQESHEKPTE0QPW9R6XV5K2","rote","Compile a proven agent skill (a SKILL.md plus references) into a deterministic pipeline that runs without an LLM in the loop, then serve it back to Claude as an MCP tool. Use when: rote, compile this skill, turn this skill into a workflow, make this skill deterministic, make this skill cheaper or faster, harden this skill for production, run this skill as a background job.","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Frote\u002FSKILL.md",[],[]]