KubeSphere Multi-Tenant Management
kubesphere/kubesphere
Creates and queries KubeSphere users, workspaces and projects and assigns built-in roles, defaulting to least privilege and never deleting anything.
Test changes in a dedicated Emacs session. An agent skill from jinnovation/kele.el.
Install Emacs Testing
$ npx skills add jinnovation/kele.el --skill emacs-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jinnovation/kele.el emacs-testing --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/jinnovation/kele.el.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/emacs-testing .claude/skills/emacs-testing && 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 "emacs-testing" agent skill from https://github.com/jinnovation/kele.el/tree/main/.claude/skills/emacs-testing into .claude/skills/emacs-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emacs-testing", 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/jinnovation/kele.el/tree/main/.claude/skills/emacs-testingType 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 jinnovation/kele.el --skill emacs-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jinnovation/kele.el emacs-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jinnovation/kele.el.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/emacs-testing .agents/skills/emacs-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "emacs-testing" agent skill from https://github.com/jinnovation/kele.el/tree/main/.claude/skills/emacs-testing into .agents/skills/emacs-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emacs-testing", 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 jinnovation/kele.el --skill emacs-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jinnovation/kele.el emacs-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jinnovation/kele.el.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/emacs-testing .cursor/skills/emacs-testing && 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 "emacs-testing" agent skill from https://github.com/jinnovation/kele.el/tree/main/.claude/skills/emacs-testing into .cursor/skills/emacs-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emacs-testing", 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/jinnovation/kele.el.git --path .claude/skills/emacs-testing--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 jinnovation/kele.el --skill emacs-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jinnovation/kele.el emacs-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jinnovation/kele.el.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/emacs-testing .gemini/skills/emacs-testing && 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 "emacs-testing" agent skill from https://github.com/jinnovation/kele.el/tree/main/.claude/skills/emacs-testing into .gemini/skills/emacs-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emacs-testing", 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 jinnovation/kele.el emacs-testingInstalls 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 jinnovation/kele.el --skill emacs-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jinnovation/kele.el.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/emacs-testing .github/skills/emacs-testing && 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 "emacs-testing" agent skill from https://github.com/jinnovation/kele.el/tree/main/.claude/skills/emacs-testing into .github/skills/emacs-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emacs-testing", 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 jinnovation/kele.el --skill emacs-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jinnovation/kele.el emacs-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jinnovation/kele.el.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/emacs-testing .opencode/skills/emacs-testing && 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 "emacs-testing" agent skill from https://github.com/jinnovation/kele.el/tree/main/.claude/skills/emacs-testing into .opencode/skills/emacs-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emacs-testing", 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
emacs-testing- GitHub stars
- 108
- Token cost
- ~134 tokens
- SKILL.md length
- 66 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Test changes in a dedicated Emacs session. An agent skill from jinnovation/kele.el.
- DevOps & Cloud work in your project
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Emacs Testing is an agent skill from jinnovation/kele.el. Test changes in a dedicated Emacs session. Good for validating behavior and UI results.
Its SKILL.md is about 130 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 DevOps & Cloud. It works with Kubernetes. The repository describes itself as: 🥤 Spritzy Kubernetes cluster management for Emacs. The licence is Apache-2.0.
When your agent uses it
- DevOps & Cloud work in your project
Example prompts
- “/emacs-testing”
What it can do on your machine
Read from SKILL.md and the folder at commit d67d028. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Emacs Testing loads about 134 tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 66 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 jinnovation/kele.el at commit d67d028, republished under its Apache-2.0 licence (© jinnovation). 66 words, ~134 tokens.
Download SKILL.mdSave it as
.claude/skills/emacs-testing/SKILL.md (or your agent's skills folder).- name
- emacs-testing
- description
- Test changes in a dedicated Emacs session. Good for validating behavior and UI results.
Before starting, you MUST ask me if you have permission to test in the existing Emacs server. If
not, start a new Emacs daemon server: emacs --daemon=kele-testing.
Send commands to the Emacs with: emacsclient --eval. If I did not give permission to run in the
existing server, use emacsclient -s kele-testing --eval.
If you created a separate daemon server, terminate it once you are done testing.
© jinnovation, Apache-2.0. 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 .claude/skills/emacs-testing of jinnovation/kele.el.
Open the folder on GitHubat commit d67d028
Compare with similar skills
Emacs Testing 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 |
|---|---|---|---|---|---|---|
| Emacs Testing this skilljinnovation/kele.el | 108 | — | ~134 | Automated safety check: Pass | Apache-2.0 | |
| KubeSphere Multi-Tenant Managementkubesphere/kubesphere | 17k | 1 repos | ~3.1k | Automated safety check: Pass | Custom licence | |
| Azure Diagnosticsmicrosoft/azure-skills | 1.5k | 1 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| Sim Helmsimstudioai/sim | 30k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Helm Chart ScaffoldingCybereason-Public/owLSM | 280 | 13 repos | ~381 | Automated safety check: Pass | GPL-2.0 |
Similar skills
- Official
Azure Diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage.
Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
Sim Helm
simstudioai/sim
Install, upgrade, and operate the Sim Helm chart on Kubernetes.
Helm Chart Scaffolding
Cybereason-Public/owLSM
Comprehensive guidance for creating, organizing, and managing Helm charts for packaging and deploying Kubernetes applications.
Kubeshark KFL2 Filter Reference
kubeshark/kubeshark
Syntax reference for KFL2, the CEL-based display filter language used to search Kubernetes network traffic captured by Kubeshark, loaded before any filter is written.
More from jinnovation/kele.el
K8s Openapi
jinnovation/kele.el
Reference the Kubernetes API. An agent skill from jinnovation/kele.el.
Related
Works with
Categories
Questions about Emacs Testing
What does Emacs Testing do?
Test changes in a dedicated Emacs session. An agent skill from jinnovation/kele.el. el. Test changes in a dedicated Emacs session.
When should I use Emacs Testing?
Emacs Testing fits situations like: devOps & Cloud work in your project.
How do I install Emacs Testing in Claude Code?
Run `npx skills add jinnovation/kele.el --skill emacs-testing -a claude-code`. Or copy the skill folder (.claude/skills/emacs-testing in jinnovation/kele.el) into .claude/skills/emacs-testing in your project. Claude Code loads it when a task matches its description.
How do I install Emacs Testing in Codex?
Run `npx skills add jinnovation/kele.el --skill emacs-testing -a codex`. Or copy the skill folder (.claude/skills/emacs-testing in jinnovation/kele.el) into .agents/skills/emacs-testing in your project. Codex loads it when a task matches its description.
Can I use Emacs Testing 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 jinnovation/kele.el --skill emacs-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/emacs-testing, .gemini/skills/emacs-testing, .github/skills/emacs-testing and .opencode/skills/emacs-testing in your project.
What does Emacs Testing need to run?
SKILL.md names no scripts, command-line tools or credentials: Emacs Testing is instructions for the agent only.
Does Emacs Testing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Emacs Testing 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 Emacs Testing use?
Emacs Testing is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Emacs Testing use?
About 134 tokens (SKILL.md is roughly 536 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 Emacs Testing?
Skills that share tags, products or a category with Emacs Testing: KubeSphere Multi-Tenant Management (kubesphere/kubesphere, 17k stars), Azure Diagnostics (microsoft/azure-skills, 1.5k stars), Kubeshark Installer (kubeshark/kubeshark, 12k stars) and Sim Helm (simstudioai/sim, 30k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Emacs Testing?
jinnovation (a GitHub user) maintains it in jinnovation/kele.el, which has 108 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on March 9, 2026.
Source: jinnovation/kele.el on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.