DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run the WikiSkill loop with Claude Code as the agent with Wikiskill

Pin a workspace to the Claude backend and evolve skills using Claude Code runs.

Who it is forA developer who already uses Claude Code and wants the same evolution loop on that agent instead of Hermes.

The problemTeams that standardize on Claude Code want skill evolution in the tool they already use, not a second agent stack.

The outcomeA workspace pinned to the claude backend, with evolution runs using Claude Code and an isolated CLAUDE_CONFIG_DIR.

What you need first

  • Python 3.10 or newer
  • Hermes Agent installed as the reference backend, or another supported agent CLI (Claude Code, Codex or GitHub Copilot CLI)
  • A configured default model for the agent, for example through OpenRouter using --model and --provider
  • Enough API budget for several iterations (the README cites about $0.09 per iteration on one free-tier run)

Steps

  1. Run pip install wikiskill to install the package.
  2. Run claude auth login once to sign in to Claude Code.
  3. Run wikiskill init demo --backend claude to create a workspace pinned to Claude Code.
  4. Run wikiskill evolve --iters 3 to run the loop on the pinned backend.
  5. Run wikiskill status to confirm the scores and the backend used.

Prompt for your agent

Using the ashutoshsinghpr7/wikiskill repo, run `wikiskill init demo --backend claude`, then `wikiskill evolve --iters 2`. Report the baseline and final validation scores and the backend in workspaces/demo/workspace.json. Verify that the workspace file names the claude backend before the evolve run starts.

Caveat. The README says the claude backend needs `claude auth login` once, so the run will not start without a signed-in Claude Code install.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page