Compile Knowledge
sickn33/agentic-awesome-skills
Compile durable, non-obvious findings into an interlinked markdown knowledge store — atomic files, [[wiki-links]], a maintained index — so an agent gets smarter across sessions instead of relearning…
Validate byte compilation for a specified Emacs Lisp file in this repository.
MITAuto-check passed
Install Elisp Compile
$ npx skills add dgillis/emacs-codex-ide --skill elisp-compile -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dgillis/emacs-codex-ide elisp-compile --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/dgillis/emacs-codex-ide.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/elisp-compile .claude/skills/elisp-compile && 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 "elisp-compile" agent skill from https://github.com/dgillis/emacs-codex-ide/tree/main/.agents/skills/elisp-compile into .claude/skills/elisp-compile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "elisp-compile", 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/dgillis/emacs-codex-ide/tree/main/.agents/skills/elisp-compileType 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 dgillis/emacs-codex-ide --skill elisp-compile -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dgillis/emacs-codex-ide elisp-compile --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dgillis/emacs-codex-ide.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/elisp-compile .agents/skills/elisp-compile && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "elisp-compile" agent skill from https://github.com/dgillis/emacs-codex-ide/tree/main/.agents/skills/elisp-compile into .agents/skills/elisp-compile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "elisp-compile", 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 dgillis/emacs-codex-ide --skill elisp-compile -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dgillis/emacs-codex-ide elisp-compile --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dgillis/emacs-codex-ide.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/elisp-compile .cursor/skills/elisp-compile && 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 "elisp-compile" agent skill from https://github.com/dgillis/emacs-codex-ide/tree/main/.agents/skills/elisp-compile into .cursor/skills/elisp-compile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "elisp-compile", 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/dgillis/emacs-codex-ide.git --path .agents/skills/elisp-compile--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 dgillis/emacs-codex-ide --skill elisp-compile -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dgillis/emacs-codex-ide elisp-compile --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dgillis/emacs-codex-ide.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/elisp-compile .gemini/skills/elisp-compile && 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 "elisp-compile" agent skill from https://github.com/dgillis/emacs-codex-ide/tree/main/.agents/skills/elisp-compile into .gemini/skills/elisp-compile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "elisp-compile", 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 dgillis/emacs-codex-ide elisp-compileInstalls 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 dgillis/emacs-codex-ide --skill elisp-compile -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dgillis/emacs-codex-ide.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/elisp-compile .github/skills/elisp-compile && 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 "elisp-compile" agent skill from https://github.com/dgillis/emacs-codex-ide/tree/main/.agents/skills/elisp-compile into .github/skills/elisp-compile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "elisp-compile", 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 dgillis/emacs-codex-ide --skill elisp-compile -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dgillis/emacs-codex-ide elisp-compile --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dgillis/emacs-codex-ide.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/elisp-compile .opencode/skills/elisp-compile && 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 "elisp-compile" agent skill from https://github.com/dgillis/emacs-codex-ide/tree/main/.agents/skills/elisp-compile into .opencode/skills/elisp-compile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "elisp-compile", 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
elisp-compile- GitHub stars
- 108
- Token cost
- ~265 tokens
- SKILL.md length
- 115 words
- Files
- 2
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
Validate byte compilation for a specified Emacs Lisp file in this repository.
- Works in 4 steps: Pass exactly one .el file path to… → The command runs emacs -Q --batch --eval… → If compilation succeeds, it deletes the… → …
- An agent needs a focused compile check for one .el file
- SKILL.md covers Workflow and Notes
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Elisp Compile is an agent skill from dgillis/emacs-codex-ide. Validate byte compilation for a specified Emacs Lisp file in this repository. Use this skill when an agent needs a focused compile check for one .el file; on success it removes the generated .elc artifact.
Its SKILL.md is about 270 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
The repository describes itself as: Codex IDE integration for Emacs. The licence is MIT.
When your agent uses it
- An agent needs a focused compile check for one .el file
- On success it removes the generated .elc artifact
Example prompts
- “/elisp-compile”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Pass exactly one .el file path to ./bin/elisp-compile.sh.
- The command runs emacs -Q --batch --eval "(setq load-prefer-newer t)" -L . -f batch-byte-compile FILE.
- If compilation succeeds, it deletes the generated .elc file before exiting.
- If compilation fails, it leaves the .elc artifact state unchanged and returns the compiler error.
What it can do on your machine
Read from SKILL.md and the folder at commit 5eba84d. 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
Elisp Compile loads about 265 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 115 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 dgillis/emacs-codex-ide at commit 5eba84d, republished under its MIT licence (© dgillis). 115 words, ~265 tokens.
Download SKILL.mdSave it as
.claude/skills/elisp-compile/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- elisp-compile
- description
- Validate byte compilation for a specified Emacs Lisp file in this repository. Use this skill when an agent needs a focused compile check for one `.el` file; on success it removes the generated `.elc` artifact.
Elisp Compile
Use this skill to run a single-file batch byte-compile check and leave the worktree clean afterward.
Workflow
- Pass exactly one
.elfile path to./bin/elisp-compile.sh. - The command runs
emacs -Q --batch --eval "(setq load-prefer-newer t)" -L . -f batch-byte-compile FILE. - If compilation succeeds, it deletes the generated
.elcfile before exiting. - If compilation fails, it leaves the
.elcartifact state unchanged and returns the compiler error.
Notes
- Use the explicit repo-root path above; do not reinterpret it relative to
SKILL.md. - The command resolves repo-relative paths against the repository root.
- This is for targeted validation, not full-suite testing.
- Use the cleanup skill directly when
.elcartifacts already exist from other commands.
© dgillis, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/elisp-compile of dgillis/emacs-codex-ide.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 5eba84d
Compare with similar skills
Elisp Compile 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 |
|---|---|---|---|---|---|---|
| Elisp Compile this skilldgillis/emacs-codex-ide | 108 | — | ~265 | Automated safety check: Pass | MIT | |
| Compile Knowledgesickn33/agentic-awesome-skills | 47k | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Compileratopile/atopile | 4k | — | ~1k | Automated safety check: Pass | MIT | |
| Emacs Channel for NanoClawnanocoai/nanoclaw | 31k | — | ~2.7k | Automated safety check: Notes | MIT | |
| Paddle Design CompilerPaddlePaddle/Paddle | 24k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| Compileccplugins/awesome-claude-code-plugins | 970 | — | ~1.3k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Compiler
atopile/atopile
How the atopile compiler builds and links TypeGraphs from .ato (ANTLR front-end → AST → TypeGraph → Linker → DeferredExecutor), plus the key invariants and test entrypoints.
Emacs Channel for NanoClaw
nanocoai/nanoclaw
Lets you chat with NanoClaw from Emacs through a local HTTP bridge, with a chat buffer and org-mode commands that put replies inline.
Paddle Design Compiler
PaddlePaddle/Paddle
A skill your agent uses when working with Paddle 3.0 compiler full pipeline: SOT (Symbolic Opcode Translator) for bytecode-level dy2st graph capture, PIR (Paddle IR) for SSA-based intermediate…
Compile
ccplugins/awesome-claude-code-plugins
Compile an Anthropic-style skill — a directory with a SKILL.md and optional references/ — into a deterministic, runnable workflow via the rote CLI.
Compile Latex
brycewang-stanford/Auto-Empirical-Research-Skills
Compile a LaTeX manuscript with pdflatex (3 passes + bibtex).
More from dgillis/emacs-codex-ide
Clean Up Elc
dgillis/emacs-codex-ide
Delete byte-compiled .elc files produced during validation in this repository.
Elisp Reload
dgillis/emacs-codex-ide
Reload one or more Emacs Lisp files from this repository into the running Emacs session with emacsclient --eval.
Run Tests
dgillis/emacs-codex-ide
Run the codex-ide test suite from this repository. An agent skill from dgillis/emacs-codex-ide.
Questions about Elisp Compile
What does Elisp Compile do?
Validate byte compilation for a specified Emacs Lisp file in this repository. Elisp Compile is an agent skill from dgillis/emacs-codex-ide. Validate byte compilation for a specified Emacs Lisp file in this repository.
When should I use Elisp Compile?
Elisp Compile fits situations like: an agent needs a focused compile check for one .el file; on success it removes the generated .elc artifact.
How do I install Elisp Compile in Claude Code?
Run `npx skills add dgillis/emacs-codex-ide --skill elisp-compile -a claude-code`. Or copy the skill folder (.agents/skills/elisp-compile in dgillis/emacs-codex-ide) into .claude/skills/elisp-compile in your project. Claude Code loads it when a task matches its description.
How do I install Elisp Compile in Codex?
Run `npx skills add dgillis/emacs-codex-ide --skill elisp-compile -a codex`. Or copy the skill folder (.agents/skills/elisp-compile in dgillis/emacs-codex-ide) into .agents/skills/elisp-compile in your project. Codex loads it when a task matches its description.
Can I use Elisp Compile 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 dgillis/emacs-codex-ide --skill elisp-compile -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/elisp-compile, .gemini/skills/elisp-compile, .github/skills/elisp-compile and .opencode/skills/elisp-compile in your project.
What does Elisp Compile need to run?
SKILL.md names no scripts, command-line tools or credentials: Elisp Compile is instructions for the agent only.
Does Elisp Compile 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 Elisp Compile 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 Elisp Compile use?
Elisp Compile is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Elisp Compile use?
About 265 tokens (SKILL.md is roughly 1.1k 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 Elisp Compile?
Skills that share tags, products or a category with Elisp Compile: Compile Knowledge (sickn33/agentic-awesome-skills, 47k stars), Compiler (atopile/atopile, 4k stars), Emacs Channel for NanoClaw (nanocoai/nanoclaw, 31k stars) and Paddle Design Compiler (PaddlePaddle/Paddle, 24k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Elisp Compile?
dgillis (a GitHub user) maintains it in dgillis/emacs-codex-ide, which has 108 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on July 30, 2026.
Source: dgillis/emacs-codex-ide on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.