Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
A skill your agent uses when creating or editing Common Lisp source files (.lisp/.asd) — setting up packages, declaring function types, choosing iteration/control-flow/condition constructs, or…
Install Writing Common Lisp
$ npx skills add ultralisp/ultralisp --skill writing-common-lisp -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ultralisp/ultralisp writing-common-lisp --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/ultralisp/ultralisp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/writing-common-lisp .claude/skills/writing-common-lisp && 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 "writing-common-lisp" agent skill from https://github.com/ultralisp/ultralisp/tree/master/.agents/skills/writing-common-lisp into .claude/skills/writing-common-lisp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-common-lisp", 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/ultralisp/ultralisp/tree/master/.agents/skills/writing-common-lispType 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 ultralisp/ultralisp --skill writing-common-lisp -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ultralisp/ultralisp writing-common-lisp --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ultralisp/ultralisp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/writing-common-lisp .agents/skills/writing-common-lisp && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "writing-common-lisp" agent skill from https://github.com/ultralisp/ultralisp/tree/master/.agents/skills/writing-common-lisp into .agents/skills/writing-common-lisp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-common-lisp", 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 ultralisp/ultralisp --skill writing-common-lisp -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ultralisp/ultralisp writing-common-lisp --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ultralisp/ultralisp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/writing-common-lisp .cursor/skills/writing-common-lisp && 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 "writing-common-lisp" agent skill from https://github.com/ultralisp/ultralisp/tree/master/.agents/skills/writing-common-lisp into .cursor/skills/writing-common-lisp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-common-lisp", 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/ultralisp/ultralisp.git --path .agents/skills/writing-common-lisp--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 ultralisp/ultralisp --skill writing-common-lisp -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ultralisp/ultralisp writing-common-lisp --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ultralisp/ultralisp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/writing-common-lisp .gemini/skills/writing-common-lisp && 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 "writing-common-lisp" agent skill from https://github.com/ultralisp/ultralisp/tree/master/.agents/skills/writing-common-lisp into .gemini/skills/writing-common-lisp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-common-lisp", 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 ultralisp/ultralisp writing-common-lispInstalls 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 ultralisp/ultralisp --skill writing-common-lisp -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ultralisp/ultralisp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/writing-common-lisp .github/skills/writing-common-lisp && 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 "writing-common-lisp" agent skill from https://github.com/ultralisp/ultralisp/tree/master/.agents/skills/writing-common-lisp into .github/skills/writing-common-lisp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-common-lisp", 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 ultralisp/ultralisp --skill writing-common-lisp -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ultralisp/ultralisp writing-common-lisp --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ultralisp/ultralisp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/writing-common-lisp .opencode/skills/writing-common-lisp && 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 "writing-common-lisp" agent skill from https://github.com/ultralisp/ultralisp/tree/master/.agents/skills/writing-common-lisp into .opencode/skills/writing-common-lisp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-common-lisp", 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
writing-common-lisp- GitHub stars
- 258
- Token cost
- ~1k tokens
- SKILL.md length
- 417 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- None found
At a glance
A skill your agent uses when creating or editing Common Lisp source files (.lisp/.asd) — setting up packages, declaring function types, choosing iteration/control-flow/condition constructs, or…
- Editing Common Lisp source files (.lisp/.asd) — setting up packages
- SKILL.md covers Overview, When to Use, Package definition… and File layout, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Declaring function types
What it does
Writing Common Lisp is an agent skill from ultralisp/ultralisp. Use when creating or editing Common Lisp source files (.lisp/.asd) — setting up packages, declaring function types, choosing iteration/control-flow/condition constructs, or applying naming and formatting conventions in a Common Lisp project.
Its SKILL.md is about 1k 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 Development. The repository describes itself as: The software behind a Ultralisp.org Common Lisp repository.
When your agent uses it
- Editing Common Lisp source files (.lisp/.asd) — setting up packages
- Declaring function types
- Choosing iteration/control-flow/condition constructs
- Applying naming and formatting conventions in a Common Lisp project
Example prompts
- “/writing-common-lisp”
What it can do on your machine
Read from SKILL.md and the folder at commit 3439788. 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 (its code samples are lisp).
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
Writing Common Lisp loads about 1k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 417 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 417 words (~1,048 tokens).
“Conventions for new .lisp/.asd source in package-inferred ASDF systems: package definition, type declarations, control flow, conditions, and formatting. Apply across all CL projects in this workspace.”
- name
- writing-common-lisp
Files
Just SKILL.md in .agents/skills/writing-common-lisp of ultralisp/ultralisp.
Open the folder on GitHubat commit 3439788
Compare with similar skills
Writing Common Lisp 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 |
|---|---|---|---|---|---|---|
| Writing Common Lisp this skillultralisp/ultralisp | 258 | — | ~1k | Automated safety check: Pass | None | |
| Vercel Composition Patternssupabase/supabase | 111k | 58 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
More from ultralisp/ultralisp
All 14 skills in this repoDispatching Parallel Agents
ultralisp/ultralisp
A skill your agent uses when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Systematic Debugging
ultralisp/ultralisp
A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Deep Research
ultralisp/ultralisp
A skill your agent uses when the user needs multi-source research with citation tracking, evidence persistence, and structured report generation.
Atomic Spec Orchestrator
ultralisp/ultralisp
AI-агент — эксперт-оркестратор разработки по методологии Atomic Spec.
Avoiding Common Lisp Pitfalls
ultralisp/ultralisp
A skill your agent uses when writing new or large Common Lisp code where subtle library or language gotchas are likely — event-emitter argument order, parenthesis imbalance in a big file, or a…
Clearing Asdf Fasl Cache
ultralisp/ultralisp
A skill your agent uses when ASDF fasl cache is stale and build tools (build-docs, qlot exec sbcl, etc.) do not pick up source changes — typically after modifying docstrings, adding defgeneric…
Related
Categories
Questions about Writing Common Lisp
What does Writing Common Lisp do?
A skill your agent uses when creating or editing Common Lisp source files (.lisp/.asd) — setting up packages, declaring function types, choosing iteration/control-flow/condition constructs, or…. Writing Common Lisp is an agent skill from ultralisp/ultralisp.asd) — setting up packages, declaring function types, choosing iteration/control-flow/condition constructs, or applying naming and formatting conventions in a Common Lisp project.
When should I use Writing Common Lisp?
Writing Common Lisp fits situations like: editing Common Lisp source files (.lisp/.asd) — setting up packages; declaring function types; choosing iteration/control-flow/condition constructs; applying naming and formatting conventions in a Common Lisp project.
How do I install Writing Common Lisp in Claude Code?
Run `npx skills add ultralisp/ultralisp --skill writing-common-lisp -a claude-code`. Or copy the skill folder (.agents/skills/writing-common-lisp in ultralisp/ultralisp) into .claude/skills/writing-common-lisp in your project. Claude Code loads it when a task matches its description.
How do I install Writing Common Lisp in Codex?
Run `npx skills add ultralisp/ultralisp --skill writing-common-lisp -a codex`. Or copy the skill folder (.agents/skills/writing-common-lisp in ultralisp/ultralisp) into .agents/skills/writing-common-lisp in your project. Codex loads it when a task matches its description.
Can I use Writing Common Lisp 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 ultralisp/ultralisp --skill writing-common-lisp -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-common-lisp, .gemini/skills/writing-common-lisp, .github/skills/writing-common-lisp and .opencode/skills/writing-common-lisp in your project.
What does Writing Common Lisp need to run?
SKILL.md names no scripts, command-line tools or credentials: Writing Common Lisp is instructions for the agent only.
Does Writing Common Lisp 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 Writing Common Lisp 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 Writing Common Lisp use?
No licence was found for Writing Common Lisp or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Writing Common Lisp use?
About 1k tokens (SKILL.md is roughly 4.2k 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 Writing Common Lisp?
Skills that share tags, products or a category with Writing Common Lisp: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Writing Common Lisp?
ultralisp (a GitHub organization) maintains it in ultralisp/ultralisp, which has 258 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 13, 2026.
Source: ultralisp/ultralisp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.