blender-kiln
Claude Code plugin that turns a text brief or a photo into a production-ready 3D asset through Blender: rebuilt by script, textured from CC0 scans, graded against the real object, optimized to GLB/FBX
A small set of Claude Code skills: handoff, PR-comment handling, next-steps, README tidying, and TL;DR.
Translation pending
SkillsShellGitHub @SlikonSelf-installOwner unconfirmed
Paste into Claude or ChatGPT for installation instructions suited to your environment.
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Installable projects can be verified without a deployment domain. Use GitHub sign-in for a personal repository, or the repository verification file above for an organization repository.
Ask about other verification options
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗A small set of agent skills for everyday engineering work. Each skill is a folder under skills/ with a single SKILL.md. The format is cross-agent — these install into Claude Code, Cursor, Codex, Gemini CLI, GitHub Copilot, OpenCode, Zed, and 70+ other agents via the skills CLI.
| Skill | What it does |
|---|---|
teach-codebase | Build a mental model of an unfamiliar repo: architecture, subsystems, and where to look when changing something. Saved at .teach/codebase.md. |
teach-pr | Explain what a PR or branch actually does before you review it — mental model, traced execution path, what to question. Saved at .teach/. |
create-pr | Open or update a PR with a concise, human-first overview at the top, plus explicit notes and screenshots when UI or image size/quality changes. |
handoff | Compact the conversation into a handoff doc for the next agent. Saved at .handoffs/ so it survives a restart. |
respond-to-pr-comments | Work through a PR's review comments: fix the valid ones, reply to the rest explaining why not. Takes a PR url or number. |
next-steps | Read the latest handoff and lay out the next steps. |
readme-check | Make sure the project has a README that's short, complete, and free of fluff. |
tldr | Compress a wall of text into a tight summary. |
bro | Restate the last message in plain human language, with no jargon. |
teach-pr reads .teach/codebase.md when it exists and explains the change as a delta against it, so running teach-codebase once per repo makes every later teach-pr sharper. Both record the commit they were generated at, so a re-run updates what actually moved instead of regenerating from scratch. They're working notes, not docs — worth adding .teach/ to your .gitignore.
Needs Node (for npx) and git. respond-to-pr-comments also needs the gh CLI; teach-pr uses gh when a PR exists but falls back to a plain branch diff.
skills CLI (recommended, any agent)# Interactive — pick which skills and which agents
npx skills add Slikon/agent-skills
# Everything, globally, into Claude Code, no prompts
npx skills add Slikon/agent-skills -g -a claude-code -y
# Other agents, or several at once
npx skills add Slikon/agent-skills -a cursor -a codex
# Just one skill
npx skills add Slikon/agent-skills --skill tldr
Update later with npx skills update.
Clone and run the installer, which symlinks each skill into ~/.claude/skills/:
git clone https://github.com/Slikon/agent-skills.git
cd agent-skills
./install.sh # into ~/.claude/skills
CLAUDE_SKILLS_DIR=/path/to/project/.claude/skills ./install.sh # into one project
Restart your agent afterward so it picks up the new skills.
Type any skill by name:
/teach-codebase # or: /teach-codebase auth
/teach-pr # or: /teach-pr https://github.com/you/repo/pull/42
/create-pr
/handoff wiring up the payments webhook
/respond-to-pr-comments https://github.com/you/repo/pull/42
/next-steps
/readme-check
/tldr
/bro
Every skill except handoff and bro also carries a description, so the agent can fire it on its own from natural phrasing — "that's too long, give me the short version" fires tldr, "what's next?" fires next-steps. Those two are typed-only by design.