Mecatl Release Cutting
stacklok/mecatl
Cuts a tagged mecatl release by dispatching the release-PR workflow, merging the bot's pull request and verifying the tag, images, Helm chart, signed archives and Homebrew formula.
Add a self-hosted "Stargazers over time" chart to any GitHub repo's README.
Install Star History Chart
$ npx skills add davila7/claude-code-templates --skill star-history-chart -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install davila7/claude-code-templates star-history-chart --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-tool/components/skills/git/star-history-chart .claude/skills/star-history-chart && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "star-history-chart" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/git/star-history-chart into .claude/skills/star-history-chart/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "star-history-chart", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/git/star-history-chartType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add davila7/claude-code-templates --skill star-history-chart -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install davila7/claude-code-templates star-history-chart --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cli-tool/components/skills/git/star-history-chart .agents/skills/star-history-chart && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "star-history-chart" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/git/star-history-chart into .agents/skills/star-history-chart/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "star-history-chart", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add davila7/claude-code-templates --skill star-history-chart -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install davila7/claude-code-templates star-history-chart --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cli-tool/components/skills/git/star-history-chart .cursor/skills/star-history-chart && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "star-history-chart" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/git/star-history-chart into .cursor/skills/star-history-chart/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "star-history-chart", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/davila7/claude-code-templates.git --path cli-tool/components/skills/git/star-history-chart--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add davila7/claude-code-templates --skill star-history-chart -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install davila7/claude-code-templates star-history-chart --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cli-tool/components/skills/git/star-history-chart .gemini/skills/star-history-chart && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "star-history-chart" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/git/star-history-chart into .gemini/skills/star-history-chart/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "star-history-chart", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install davila7/claude-code-templates star-history-chartInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add davila7/claude-code-templates --skill star-history-chart -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .github/skills && cp -r skills-src/cli-tool/components/skills/git/star-history-chart .github/skills/star-history-chart && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "star-history-chart" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/git/star-history-chart into .github/skills/star-history-chart/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "star-history-chart", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add davila7/claude-code-templates --skill star-history-chart -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install davila7/claude-code-templates star-history-chart --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cli-tool/components/skills/git/star-history-chart .opencode/skills/star-history-chart && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "star-history-chart" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/git/star-history-chart into .opencode/skills/star-history-chart/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "star-history-chart", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
star-history-chart- GitHub stars
- 33k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 436 words
- Files
- 3 (incl. scripts, assets)
- Skills in repo
- 479
- Repo updated
- First seen
- Licence
- MIT
At a glance
Add a self-hosted "Stargazers over time" chart to any GitHub repo's README.
- Works in 5 steps: Copy the script and workflow into the repo → Generate the SVG once, locally → Add it to the README → …
- The star chart in a README is broken
- SKILL.md covers Why this exists, What this skill sets up, Workflow and Customization, plus 1 more section
- Runs Python scripts from its folder; calls git, gh and pip; reaches github.com; needs GITHUB_TOKEN
What it does
Star History Chart is an agent skill from davila7/claude-code-templates. 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/collaborators, 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 GITHUBTOKEN. Use when the star chart in a README is broken, shows "Requires authentication", or you want a star history that…
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts and assets (for example `assets/star-history.yml` and `scripts/generate_star_history.py`).
It sits in DevOps & Cloud, covering CI/CD, Technical documentation and Authentication. It works with GitHub and Git. The repository describes itself as: CLI tool for configuring and monitoring Claude Code. The licence is MIT.
When your agent uses it
- The star chart in a README is broken
- Shows Requires authentication
- You want a star history that never breaks
Example prompts
- “Stargazers over time”
- “s README. GitHub now restricts the stargazers endpoint to a repo”
- “Requires authentication”
- “/star-history-chart”
Requirements
- Python 3
- A credential in GITHUB_TOKEN
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit c0ca7da. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
gitghpip
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
GITHUB_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Star History Chart loads about 1.1k tokens when it runs. Until then it costs about 138 tokens; SKILL.md has 436 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from davila7/claude-code-templates at commit c0ca7da, republished under its MIT licence (© davila7). 436 words, ~1,093 tokens.
Download SKILL.mdSave it as
.claude/skills/star-history-chart/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- star-history-chart
- description
- 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/collaborators, 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.
Star History Chart (self-hosted, never breaks)
Add a "Stargazers over time" chart that renders from a static SVG committed to the repo and refreshes itself weekly — no external chart service, no broken images.
Why this exists
GitHub now restricts the /stargazers endpoint to a repository's own admins and
collaborators. Unauthenticated requests return {"message":"Requires authentication"}, which breaks every third-party live-chart service
(star-history.com free tier, starchart.cc, etc.) for all repos. The only
reliable fix is to generate the chart yourself with an authenticated token and
commit a static image. Inside GitHub Actions, the repo's own GITHUB_TOKEN can
read its own stargazers, so the whole thing runs with zero secrets to configure.
What this skill sets up
scripts/generate_star_history.py— fetches stargazers (authenticated), renders a clean, light/dark-adaptive SVG..github/workflows/star-history.yml— weekly cron + manual trigger that regenerates and commitsdocs/star-history.svg.- A README section pointing at the local SVG.
Workflow
Step 1: Copy the script and workflow into the repo
mkdir -p scripts .github/workflows docs
cp skills/git/star-history-chart/scripts/generate_star_history.py scripts/generate_star_history.py
cp skills/git/star-history-chart/assets/star-history.yml .github/workflows/star-history.ymlThe script needs the
requestspackage:pip install requests. It resolves the repo fromSTAR_HISTORY_REPO, thenGITHUB_REPOSITORY(set automatically in Actions), then theorigingit remote — so no edits are required for it to work in a different repo.
Step 2: Generate the SVG once, locally
Use a token that can read the repo's stargazers (as owner/collaborator). The GitHub CLI provides one:
GITHUB_TOKEN=$(gh auth token) python scripts/generate_star_history.pyThis writes docs/star-history.svg. For a repo with many thousands of stars the
first run paginates the whole stargazer list and can take a couple of minutes.
Verify it rendered (optional, macOS): qlmanage -t -s 800 -o . docs/star-history.svg
Show full SKILL.md (182 more words)Show less
Step 3: Add it to the README
Add or replace the star chart section. Point the image at the local SVG. Set the link target to wherever you want clicks to go (the repo, a docs page, or your own site):
## Stargazers over time
[](https://github.com/OWNER/REPO/stargazers)If replacing a broken star-history.com / starchart.cc embed, swap only the
image URL to docs/star-history.svg and keep or update the link target.
Step 4: Commit
git add scripts/generate_star_history.py .github/workflows/star-history.yml docs/star-history.svg README.md
git commit -m "feat(readme): self-hosted stargazers chart with weekly auto-refresh"
git pushStep 5: (Optional) Trigger the auto-refresh now
The workflow runs every Monday at 04:00 UTC. To refresh immediately without waiting: GitHub → Actions → "Update Star History" → Run workflow.
Customization
- Output path — set
STAR_HISTORY_OUTPUT(defaultdocs/star-history.svg). - Different repo — set
STAR_HISTORY_REPO=owner/name. - Colors / size — edit the
.line,.area,.dotCSS andWIDTH/HEIGHTconstants near the top ofgenerate_star_history.py. The chart is theme-aware via aprefers-color-scheme: darkblock, so it looks right in both GitHub light and dark modes. - Refresh cadence — edit the
cronexpression in the workflow.
Notes
- No secrets to add: the workflow uses the automatic
GITHUB_TOKEN. - Private repos work too, as long as the token can read the repo.
- The script uses only
requestsplus the Python standard library.
© davila7, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (scripts, assets) in cli-tool/components/skills/git/star-history-chart of davila7/claude-code-templates.
- SKILL.md
- assets/star-history.yml
- scripts/generate_star_history.py
Open the folder on GitHubat commit c0ca7da
Compare with similar skills
Star History Chart next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Star History Chart this skilldavila7/claude-code-templates | 33k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Mecatl Release Cuttingstacklok/mecatl | 254 | — | ~3.9k | Automated safety check: Pass | Apache-2.0 | |
| OpenWork Release Processdifferent-ai/openwork | 24k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| ccLoad Release Publishercaidaoli/ccLoad | 419 | — | ~887 | Automated safety check: Pass | MIT | |
| ClickUp CLI Release Processkrodak/clickup-cli | 123 | — | ~906 | Automated safety check: Warn | MIT | |
| Authoring GitHub Workflowsdotnet/skills | 5.6k | 1 repos | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
OpenWork Release Process
different-ai/openwork
Cuts an OpenWork desktop release through a tag-driven GitHub Actions workflow that makes no commits, with pre-tag checks on open fix PRs and verification afterward.
ccLoad Release Publisher
caidaoli/ccLoad
Publishes a ccLoad Beta or explicit stable release through a version-tag workflow, including commit, push, CI wait, GitHub Release and container image checks.
ClickUp CLI Release Process
krodak/clickup-cli
Walks through releasing a new version of clickup-cli: pre-release checks, version bump, tagging, CI watch, release notes and the Homebrew update.
- Official
Authoring GitHub Workflows
dotnet/skills
Author and review GitHub Actions workflow YAML safely so syntactically-valid YAML can't ship a workflow that GitHub Actions refuses to run.
- Official
Admin
grafana/skills
Manage Grafana Cloud accounts — organizations, stacks, RBAC roles and assignments, SSO/SAML/OAuth/GitHub auth, service accounts for CI/CD, user invites, team membership, and API-driven provisioning.
More from davila7/claude-code-templates
All 479 skills in this repoPerplexity Web Search
davila7/claude-code-templates
Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.
Neuropixels Data Analysis
davila7/claude-code-templates
Analyzes Neuropixels recordings from SpikeGLX or Open Ephys through preprocessing, drift correction, Kilosort4 spike sorting, quality metrics and curation.
Scientific Venue Templates
davila7/claude-code-templates
Supplies LaTeX templates and formatting rules for journals, conferences, posters, and grant proposals, then can check a draft against them.
Brand Voice Content Creator
davila7/claude-code-templates
Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.
CAPA Officer
davila7/claude-code-templates
Guides corrective and preventive action (CAPA) work in a quality management system, from initiation and root cause analysis through effectiveness verification.
Fda Consultant Specialist
davila7/claude-code-templates
Senior FDA consultant and specialist for medical device companies including HIPAA compliance and requirement management.
Related
Categories
Questions about Star History Chart
What does Star History Chart do?
Add a self-hosted "Stargazers over time" chart to any GitHub repo's README. Star History Chart is an agent skill from davila7/claude-code-templates. Add a self-hosted "Stargazers over time" chart to any GitHub repo's README.
When should I use Star History Chart?
Star History Chart fits situations like: the star chart in a README is broken; shows Requires authentication; you want a star history that never breaks.
How do I install Star History Chart in Claude Code?
Run `npx skills add davila7/claude-code-templates --skill star-history-chart -a claude-code`. Or copy the skill folder (cli-tool/components/skills/git/star-history-chart in davila7/claude-code-templates) into .claude/skills/star-history-chart in your project. Claude Code loads it when a task matches its description.
How do I install Star History Chart in Codex?
Run `npx skills add davila7/claude-code-templates --skill star-history-chart -a codex`. Or copy the skill folder (cli-tool/components/skills/git/star-history-chart in davila7/claude-code-templates) into .agents/skills/star-history-chart in your project. Codex loads it when a task matches its description.
Can I use Star History Chart in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davila7/claude-code-templates --skill star-history-chart -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/star-history-chart, .gemini/skills/star-history-chart, .github/skills/star-history-chart and .opencode/skills/star-history-chart in your project.
What does Star History Chart need to run?
Going by SKILL.md and its folder, Star History Chart needs Python for the scripts in its folder, the command-line tools its instructions call (git, gh and pip) and credentials named GITHUB_TOKEN. Our summary lists: Python 3; A credential in GITHUB_TOKEN.
Does Star History Chart access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Star History Chart safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Star History Chart use?
Star History Chart is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Star History Chart use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Star History Chart?
Skills that share tags, products or a category with Star History Chart: Mecatl Release Cutting (stacklok/mecatl, 254 stars), OpenWork Release Process (different-ai/openwork, 24k stars), ccLoad Release Publisher (caidaoli/ccLoad, 419 stars) and ClickUp CLI Release Process (krodak/clickup-cli, 123 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Star History Chart?
davila7 (a GitHub user) maintains it in davila7/claude-code-templates, which has 32,512 GitHub stars. The repository holds 479 skills in this directory. The repository was last updated on October 10, 2026.
Source: davila7/claude-code-templates on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.