usetheokit

Theokit Skills — Development skill for Claude Code

Development community

How to install Theokit Skills

This entry records only its repository, not the path inside it, so there is no exact command to give. Open usetheokit/theokit-skills and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Theokit Skills does

Claude Code plugin that teaches the assistant the real @theokit/sdk API surface — Agent.create, Tool.create with Zod, streaming SDKMessage events, MCP servers, subagents, cron and the error hierarchy — so it writes correct SDK code instead of plausible code. npx @theokit/skill. Apache-2.0.

Alternatives in Development

MCP Python SDK — Python SDK for building MCP servers 22.3k ★
AgentHandover — What if OpenClaw, Claude Code, Codex etc. knew how to do your work without you saying it 600 ★
Convex Cron Jobs 354 ★

README

@theokit/skills

Agent skills for the TheoKit ecosystem, and the machinery that puts them where your AI coding tool will read them — Claude Code, OpenAI Codex, Gemini CLI, GitHub Copilot, Zed, Devin Desktop, on Windows, macOS and Linux.

Read this first: the corpus is empty

`skills/` contains nothing. Commit `9c2e340` deleted all 32 hand-written skills, and the replacement is being built. **Running `npx @theokit/skills` today installs zero skills.** The installer works; it has nothing to install.

`@theokit/skills@0.9.2` is on npm and still carries the old corpus. Nothing here has been published since, and nothing should be until the corpus returns — a release from this tree would ship an installer with an empty payload.

Why the corpus was deleted rather than fixed

The skills were written by hand, and nothing in the process could tell correct code from plausible code. Two cases are on record in `CHANGELOG.md`: one skill taught `await using`, which needs Node 24, in a package declaring `>=22.12.0`; another imported `zod` without naming the major, in a package depending on `zod@^4`. Both examples read well. Neither worked.

The replacement generates skills instead of writing them, and splits the work by what each part can actually prove:

Part	Produces	Why that part
`theokit-examples` and its CI	the example code, verbatim	it is the only thing that executes it
the `.d.ts` of the pinned package version	the public API surface	it is what you publish
an LLM	the prose: what, when, why, pitfalls	it is where types and tests are silent

No line of code and no API signature in a generated skill is written by a model. Code is copied byte-for-byte out of an example that CI ran, comments included — an example's doc comments record what a signature cannot, and paraphrasing them would lose the only content no model could reproduce.

The full design is in [`docs/superpower