Using Docs Kit
lobehub/lobe-ui
Set up and author a documentation site with @lobehub/docs-kit (the lobedocs CLI, React Router + Vite static docs used by ui.lobehub.com).
Updates the White Paper theme to the latest stable Ruby and Jekyll releases, resolves compatibility issues, verifies builds, maintains the changelog, and bumps the theme version.
Install Update Jekyll Theme
$ npx skills add vinitkumar/white-paper --skill update-jekyll-theme -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vinitkumar/white-paper update-jekyll-theme --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/vinitkumar/white-paper.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/update-jekyll-theme .claude/skills/update-jekyll-theme && 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 "update-jekyll-theme" agent skill from https://github.com/vinitkumar/white-paper/tree/gh-pages/.agents/skills/update-jekyll-theme into .claude/skills/update-jekyll-theme/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-jekyll-theme", 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/vinitkumar/white-paper/tree/gh-pages/.agents/skills/update-jekyll-themeType 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 vinitkumar/white-paper --skill update-jekyll-theme -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vinitkumar/white-paper update-jekyll-theme --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vinitkumar/white-paper.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/update-jekyll-theme .agents/skills/update-jekyll-theme && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "update-jekyll-theme" agent skill from https://github.com/vinitkumar/white-paper/tree/gh-pages/.agents/skills/update-jekyll-theme into .agents/skills/update-jekyll-theme/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-jekyll-theme", 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 vinitkumar/white-paper --skill update-jekyll-theme -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vinitkumar/white-paper update-jekyll-theme --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vinitkumar/white-paper.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/update-jekyll-theme .cursor/skills/update-jekyll-theme && 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 "update-jekyll-theme" agent skill from https://github.com/vinitkumar/white-paper/tree/gh-pages/.agents/skills/update-jekyll-theme into .cursor/skills/update-jekyll-theme/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-jekyll-theme", 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/vinitkumar/white-paper.git --path .agents/skills/update-jekyll-theme--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 vinitkumar/white-paper --skill update-jekyll-theme -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vinitkumar/white-paper update-jekyll-theme --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vinitkumar/white-paper.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/update-jekyll-theme .gemini/skills/update-jekyll-theme && 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 "update-jekyll-theme" agent skill from https://github.com/vinitkumar/white-paper/tree/gh-pages/.agents/skills/update-jekyll-theme into .gemini/skills/update-jekyll-theme/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-jekyll-theme", 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 vinitkumar/white-paper update-jekyll-themeInstalls 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 vinitkumar/white-paper --skill update-jekyll-theme -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vinitkumar/white-paper.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/update-jekyll-theme .github/skills/update-jekyll-theme && 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 "update-jekyll-theme" agent skill from https://github.com/vinitkumar/white-paper/tree/gh-pages/.agents/skills/update-jekyll-theme into .github/skills/update-jekyll-theme/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-jekyll-theme", 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 vinitkumar/white-paper --skill update-jekyll-theme -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vinitkumar/white-paper update-jekyll-theme --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vinitkumar/white-paper.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/update-jekyll-theme .opencode/skills/update-jekyll-theme && 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 "update-jekyll-theme" agent skill from https://github.com/vinitkumar/white-paper/tree/gh-pages/.agents/skills/update-jekyll-theme into .opencode/skills/update-jekyll-theme/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-jekyll-theme", 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
update-jekyll-theme- GitHub stars
- 228
- Token cost
- ~826 tokens
- SKILL.md length
- 391 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
Updates the White Paper theme to the latest stable Ruby and Jekyll releases, resolves compatibility issues, verifies builds, maintains the changelog, and bumps the theme version.
- Works in 12 steps: Inspect git status, the latest version… → Leave unrelated user changes untouched.… → Resolve the latest stable Ruby and… → …
- Asked to modernize
- SKILL.md covers Sources, Workflow, Release safety and Report
- Calls git and bundle
What it does
Update Jekyll Theme is an agent skill from vinitkumar/white-paper. Updates the White Paper theme to the latest stable Ruby and Jekyll releases, resolves compatibility issues, verifies builds, maintains the changelog, and bumps the theme version. Use when asked to modernize, upgrade, or release this Jekyll theme, or invoke with /skill:update-jekyll-theme.
Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering Static sites and blogs and Report writing. It works with Ruby. The repository describes itself as: Simple, elegant and clean jekyll theme. The licence is MIT.
When your agent uses it
- Asked to modernize
- Release this Jekyll theme
- Invoke with /skill:update-jekyll-theme
Example prompts
- “Use the update-jekyll-theme skill to update the White Paper theme to the latest stable Ruby and Jekyll releases, resolves compatibility issues…”
- “/update-jekyll-theme”
Workflow steps
12 steps, taken from the first numbered list in SKILL.md.
- Inspect git status, the latest version tag, Gemfile, Ruby-version files, lockfiles, CI, README.md, _config.yml, and CHANGELOG.md.
- Leave unrelated user changes untouched. Stop and report any overlap that cannot be preserved safely.
- Resolve the latest stable Ruby and Jekyll versions from the official sources above. Exclude previews, release candidates, and nightlies.
- Check the selected Ruby, Jekyll, Bundler, plugins, and native gems for compatibility before editing.
- Add or update .ruby-version. Update Gemfile with explicit, justified compatibility constraints and remove obsolete direct dependencies…
- Generate or update Gemfile.lock with the selected Ruby and Bundler. Do not hand-edit dependency resolutions.
- Update CI, development instructions, configuration, and theme files affected by the upgrade. Preserve theme behavior and public…
- Run the frontend build, dependency checks, bundle exec jekyll build, and relevant tests. Fix upgrade-caused warnings and failures. Never…
- Determine the next semantic version from the latest reachable vX.Y.Z tag
- Treat raising the minimum Ruby or Jekyll version beyond the prior supported range as a breaking change. Explain the selected bump.
- Use VERSION as the canonical theme version, creating it if absent. Synchronize the README version and any theme-package metadata. Do not…
- Create or update CHANGELOG.md using Keep a Changelog headings. Add a dated section for the new version with only user-relevant changes…
What it can do on your machine
Read from SKILL.md and the folder at commit df269dd. 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
Shell commands in SKILL.md call:
gitbundle
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
jekyllrb.comruby-lang.orgrubygems.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Update Jekyll Theme loads about 826 tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 391 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from vinitkumar/white-paper at commit df269dd, republished under its MIT licence (© vinitkumar). 391 words, ~826 tokens.
Download SKILL.mdSave it as
.claude/skills/update-jekyll-theme/SKILL.md (or your agent's skills folder).- name
- update-jekyll-theme
- description
- Updates the White Paper theme to the latest stable Ruby and Jekyll releases, resolves compatibility issues, verifies builds, maintains the changelog, and bumps the theme version. Use when asked to modernize, upgrade, or release this Jekyll theme, or invoke with /skill:update-jekyll-theme.
Update Jekyll Theme
Upgrade the current White Paper repository completely. Do not stop after changing version constraints.
Sources
Use current stable releases from official sources; do not rely on remembered versions:
- Ruby: https://www.ruby-lang.org/en/downloads/
- Jekyll: https://jekyllrb.com/
- Jekyll documentation: https://jekyllrb.com/docs/
- Theme documentation: https://jekyllrb.com/docs/themes/
- RubyGems metadata: https://rubygems.org/gems/jekyll
Workflow
- Inspect
git status, the latest version tag,Gemfile, Ruby-version files, lockfiles, CI,README.md,_config.yml, andCHANGELOG.md. - Leave unrelated user changes untouched. Stop and report any overlap that cannot be preserved safely.
- Resolve the latest stable Ruby and Jekyll versions from the official sources above. Exclude previews, release candidates, and nightlies.
- Check the selected Ruby, Jekyll, Bundler, plugins, and native gems for compatibility before editing.
- Add or update
.ruby-version. UpdateGemfilewith explicit, justified compatibility constraints and remove obsolete direct dependencies only when proven unnecessary. - Generate or update
Gemfile.lockwith the selected Ruby and Bundler. Do not hand-edit dependency resolutions. - Update CI, development instructions, configuration, and theme files affected by the upgrade. Preserve theme behavior and public configuration unless compatibility requires a change.
- Run the frontend build, dependency checks,
bundle exec jekyll build, and relevant tests. Fix upgrade-caused warnings and failures. Never claim success for commands that did not run. - Determine the next semantic version from the latest reachable
vX.Y.Ztag:- major: breaking configuration, output, API, or supported-runtime change
- minor: backward-compatible capability
- patch: backward-compatible fix or dependency refresh
- Treat raising the minimum Ruby or Jekyll version beyond the prior supported range as a breaking change. Explain the selected bump.
- Use
VERSIONas the canonical theme version, creating it if absent. Synchronize the README version and any theme-package metadata. Do not change unrelated tool-package versions unless they represent the theme release. - Create or update
CHANGELOG.mdusing Keep a Changelog headings. Add a dated section for the new version with only user-relevant changes since the previous version tag. Include migration notes for breaking changes. - Re-run all verification after version and changelog edits.
Show full SKILL.md (64 more words)Show less
Release safety
Prepare the release but do not commit, tag, push, publish, or deploy unless the user explicitly requests it. Do not weaken dependency constraints or skip failures merely to make the build pass.
Report
State the old and new Ruby, Jekyll, Bundler, and theme versions; compatibility changes; files changed; commands run; and any unresolved warnings. Provide the exact suggested tag without creating it.
© vinitkumar, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/update-jekyll-theme of vinitkumar/white-paper.
Open the folder on GitHubat commit df269dd
Compare with similar skills
Update Jekyll Theme 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 |
|---|---|---|---|---|---|---|
| Update Jekyll Theme this skillvinitkumar/white-paper | 228 | — | ~826 | Automated safety check: Pass | MIT | |
| Using Docs Kitlobehub/lobe-ui | 2.2k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Upgrade Hugocurtiscde/hugo-theme-massively | 169 | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Port Upstreamgjtorikian/tailwind_merge | 148 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Astro Adversary Bluewithastro/astro | 63k | — | ~782 | Automated safety check: Pass | Custom licence | |
| Astro Adversary Purplewithastro/astro | 63k | — | ~1.4k | Automated safety check: Pass | Custom licence |
Similar skills
Upgrade Hugo
curtiscde/hugo-theme-massively
Upgrade the theme to the latest Hugo release - read release notes for deprecations, test with real binaries, fix templates/config, bump version pins, open a PR.
Port Upstream
gjtorikian/tailwind_merge
Check GitHub notifications for upstream dcastil/tailwind-merge pull requests and port merged ones into this Ruby gem (branch, translated code, tests, commit, PR).
- Official
Astro Adversary Blue
withastro/astro
Independently implement and validate an alternative solution for an Astro pull request.
- Official
Astro Adversary Purple
withastro/astro
Qualify and compare red and blue solutions for an Astro pull request using Astro-specific merge and tie-break criteria.
Benchmark
jjjkkkjjj/Matft
Procedure for benchmarking Matft's PerformanceTests against Numpy and reporting the results (and, when asked, updating the speed comparison table on the docs site, website/docs/performance.md).
Related
Works with
Categories
Questions about Update Jekyll Theme
What does Update Jekyll Theme do?
Updates the White Paper theme to the latest stable Ruby and Jekyll releases, resolves compatibility issues, verifies builds, maintains the changelog, and bumps the theme version. Update Jekyll Theme is an agent skill from vinitkumar/white-paper. Updates the White Paper theme to the latest stable Ruby and Jekyll releases, resolves compatibility issues, verifies builds, maintains the changelog, and bumps the theme version.
When should I use Update Jekyll Theme?
Update Jekyll Theme fits situations like: asked to modernize; release this Jekyll theme; invoke with /skill:update-jekyll-theme.
How do I install Update Jekyll Theme in Claude Code?
Run `npx skills add vinitkumar/white-paper --skill update-jekyll-theme -a claude-code`. Or copy the skill folder (.agents/skills/update-jekyll-theme in vinitkumar/white-paper) into .claude/skills/update-jekyll-theme in your project. Claude Code loads it when a task matches its description.
How do I install Update Jekyll Theme in Codex?
Run `npx skills add vinitkumar/white-paper --skill update-jekyll-theme -a codex`. Or copy the skill folder (.agents/skills/update-jekyll-theme in vinitkumar/white-paper) into .agents/skills/update-jekyll-theme in your project. Codex loads it when a task matches its description.
Can I use Update Jekyll Theme 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 vinitkumar/white-paper --skill update-jekyll-theme -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/update-jekyll-theme, .gemini/skills/update-jekyll-theme, .github/skills/update-jekyll-theme and .opencode/skills/update-jekyll-theme in your project.
What does Update Jekyll Theme need to run?
Going by SKILL.md and its folder, Update Jekyll Theme needs the command-line tools its instructions call (git and bundle).
Does Update Jekyll Theme access the network?
SKILL.md names 3 domains. As links in the text: jekyllrb.com, ruby-lang.org and rubygems.org. This is read from the text; nothing was executed.
Is Update Jekyll Theme 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. Review the folder before installing.
What licence does Update Jekyll Theme use?
Update Jekyll Theme 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 Update Jekyll Theme use?
About 826 tokens (SKILL.md is roughly 3.3k 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 Update Jekyll Theme?
Skills that share tags, products or a category with Update Jekyll Theme: Using Docs Kit (lobehub/lobe-ui, 2.2k stars), Upgrade Hugo (curtiscde/hugo-theme-massively, 169 stars), Port Upstream (gjtorikian/tailwind_merge, 148 stars) and Astro Adversary Blue (withastro/astro, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Update Jekyll Theme?
vinitkumar (a GitHub user) maintains it in vinitkumar/white-paper, which has 228 GitHub stars. The repository was last updated on September 21, 2026.
Source: vinitkumar/white-paper on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.