agentsclimarketplace
Sign in

Klaussy update

Skill steph-dove/klaussy-agents/skills/klaussy-update

Use when the user wants to refresh klaussy-generated boilerplate (per-agent conventions, skills, settings, hooks) across every scaffolded agent after upgrading klaussy itself. Re-runs the scaffold against the latest templates so this repo picks up new skills, prompt revisions, and convention rules.From its SKILL.md

Install
npx -y skills add steph-dove/klaussy-agents --skill klaussy-update

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 13 stars13 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.0 KB, 667 tokens by cl100k_base, as published. Nobody here has run it

Klaussy update

Refresh this repository's klaussy-generated boilerplate to match the latest klaussy version, for every agent klaussy previously scaffolded (Claude Code, Gemini CLI, Cursor, Codex, GitHub Copilot, Google Antigravity, Cline, Aider).

Steps

  1. Upgrade klaussy first. Run pipx upgrade klaussy (or pip install --user --upgrade klaussy if klaussy wasn't installed via pipx). Verify the new version with klaussy --version. Note the version for the report at the end.

  2. Read the existing version marker. cat .claude/skills/.klaussy-version captures the version that last generated the skills. If the new klaussy version is the same as the marker, klaussy will skip — surface that to the user and confirm they want to proceed anyway (rare; usually only useful if you've also bumped klaussy-repo-conventions and want to re-run the path-scoped CLAUDE.md emission).

  3. Detect the base branch the same way klaussy-init does (git branch --list dev develop main master | head -1).

  4. Run klaussy init --force. The --force flag overrides the version-skip check and rewrites all generated files with the new templates:

    klaussy init --force --base-branch <detected> $ARGUMENTS

  5. Diff the result. Run git diff over the generated files for every scaffolded agent — Claude (CLAUDE.md, .claude/) plus any of GEMINI.md/.gemini/, AGENTS.md (Codex/Antigravity), .cursor/, .github/copilot-instructions.md/.github/skills/, .clinerules/, CONVENTIONS.md (Aider) that exist — and summarize the substantive changes for the user:

    • New skills added or removed
    • Prompt body changes in <repo>-plan / <repo>-review / etc.
    • New / changed rule files (e.g. under .claude/rules/)
    • Settings or hook changes This is the user's chance to review before committing the refresh.

  6. Report. Tell the user the old marker version → new version, what materially changed in the generated content, and remind them to commit.

When NOT to use

  • The repo isn't klaussified yet — use the klaussy-init skill instead (running klaussy init --force on a clean repo works but the skill auto-detect is cleaner).
  • The user only wants to update one specific surface (just skills, just hooks, just settings) — they can run klaussy skills, klaussy hooks, or klaussy settings directly without init --force.
  • The user pinned an older klaussy version intentionally and doesn't want to upgrade — skip step 1 and re-run klaussy init --force against the existing version, but flag that this is unusual.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most project setup skills give in 667 tokens

Counted across 1,553 of the 3,091 authors here whose files we hold, read 2026-09-06

  • Write the configuration filein 36 of 1553
  • Create the directory structurein 35 of 1553, across 33 files
  • Verify the setupin 31 of 1553, across 28 files
  • Run the setup scriptin 30 of 1553, across 29 files
  • Pre-determine the required sample sizein 29 of 1553, across 12 files
  • Check if the configuration already existsin 29 of 1553
  • Document every testin 26 of 1553, across 10 files
  • Start with a hypothesisin 26 of 1553, across 11 files
  • Ask one question at a timein 22 of 1553
  • Test a single variable per testin 21 of 1553, across 9 files
  • Read product marketing context before asking questionsin 19 of 1553, across 8 files
  • Do not peek and stop earlyin 18 of 1553, across 7 files

Said here and by no other author read

  • Upgrade klaussy first
  • Read the existing version marker
  • Run klaussy init with force
  • Diff the result

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.