Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
A skill your agent uses when encoding or decoding JSON, building dictionary/map data, or choosing between hash-tables, alists, and plists in Common Lisp — especially with YASON or serapeum:dict, or…
Install Handling JSON In Common Lisp
$ npx skills add ultralisp/ultralisp --skill handling-json-in-common-lisp -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ultralisp/ultralisp handling-json-in-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/handling-json-in-common-lisp .claude/skills/handling-json-in-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 "handling-json-in-common-lisp" agent skill from https://github.com/ultralisp/ultralisp/tree/master/.agents/skills/handling-json-in-common-lisp into .claude/skills/handling-json-in-common-lisp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "handling-json-in-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/handling-json-in-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 handling-json-in-common-lisp -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ultralisp/ultralisp handling-json-in-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/handling-json-in-common-lisp .agents/skills/handling-json-in-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 "handling-json-in-common-lisp" agent skill from https://github.com/ultralisp/ultralisp/tree/master/.agents/skills/handling-json-in-common-lisp into .agents/skills/handling-json-in-common-lisp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "handling-json-in-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 handling-json-in-common-lisp -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ultralisp/ultralisp handling-json-in-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/handling-json-in-common-lisp .cursor/skills/handling-json-in-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 "handling-json-in-common-lisp" agent skill from https://github.com/ultralisp/ultralisp/tree/master/.agents/skills/handling-json-in-common-lisp into .cursor/skills/handling-json-in-common-lisp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "handling-json-in-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/handling-json-in-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 handling-json-in-common-lisp -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ultralisp/ultralisp handling-json-in-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/handling-json-in-common-lisp .gemini/skills/handling-json-in-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 "handling-json-in-common-lisp" agent skill from https://github.com/ultralisp/ultralisp/tree/master/.agents/skills/handling-json-in-common-lisp into .gemini/skills/handling-json-in-common-lisp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "handling-json-in-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 handling-json-in-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 handling-json-in-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/handling-json-in-common-lisp .github/skills/handling-json-in-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 "handling-json-in-common-lisp" agent skill from https://github.com/ultralisp/ultralisp/tree/master/.agents/skills/handling-json-in-common-lisp into .github/skills/handling-json-in-common-lisp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "handling-json-in-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 handling-json-in-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 handling-json-in-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/handling-json-in-common-lisp .opencode/skills/handling-json-in-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 "handling-json-in-common-lisp" agent skill from https://github.com/ultralisp/ultralisp/tree/master/.agents/skills/handling-json-in-common-lisp into .opencode/skills/handling-json-in-common-lisp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "handling-json-in-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
handling-json-in-common-lisp- GitHub stars
- 258
- Token cost
- ~813 tokens
- SKILL.md length
- 287 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- None found
At a glance
A skill your agent uses when encoding or decoding JSON, building dictionary/map data, or choosing between hash-tables, alists, and plists in Common Lisp — especially with YASON or serapeum:dict, or…
- Building dictionary/map data
- SKILL.md covers Overview, When to Use, Build objects with serapeum:dict and Read with gethash, not assoc, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Choosing between hash-tables
What it does
Handling JSON In Common Lisp is an agent skill from ultralisp/ultralisp. Use when encoding or decoding JSON, building dictionary/map data, or choosing between hash-tables, alists, and plists in Common Lisp — especially with YASON or serapeum:dict, or when a JSON null check via (null ...) returns the wrong answer.
Its SKILL.md is about 810 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
- Building dictionary/map data
- Choosing between hash-tables
- Plists in Common Lisp — especially with YASON
- A JSON null check via (null ...) returns the wrong answer
Example prompts
- “/handling-json-in-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
Handling JSON In Common Lisp loads about 813 tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 287 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 287 words (~813 tokens).
“JSON objects map to hash-tables with string keys, not alists or plists. Build them with serapeum:dict; read with gethash. JSON null is the keyword :null, not CL nil.”
- name
- handling-json-in-common-lisp
Files
Just SKILL.md in .agents/skills/handling-json-in-common-lisp of ultralisp/ultralisp.
Open the folder on GitHubat commit 3439788
Compare with similar skills
Handling JSON In 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 |
|---|---|---|---|---|---|---|
| Handling JSON In Common Lisp this skillultralisp/ultralisp | 258 | — | ~813 | 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 | 4 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 Handling JSON In Common Lisp
What does Handling JSON In Common Lisp do?
A skill your agent uses when encoding or decoding JSON, building dictionary/map data, or choosing between hash-tables, alists, and plists in Common Lisp — especially with YASON or serapeum:dict, or…. Handling JSON In Common Lisp is an agent skill from ultralisp/ultralisp.) returns the wrong answer.
When should I use Handling JSON In Common Lisp?
Handling JSON In Common Lisp fits situations like: building dictionary/map data; choosing between hash-tables; plists in Common Lisp — especially with YASON; A JSON null check via (null ...) returns the wrong answer.
How do I install Handling JSON In Common Lisp in Claude Code?
Run `npx skills add ultralisp/ultralisp --skill handling-json-in-common-lisp -a claude-code`. Or copy the skill folder (.agents/skills/handling-json-in-common-lisp in ultralisp/ultralisp) into .claude/skills/handling-json-in-common-lisp in your project. Claude Code loads it when a task matches its description.
How do I install Handling JSON In Common Lisp in Codex?
Run `npx skills add ultralisp/ultralisp --skill handling-json-in-common-lisp -a codex`. Or copy the skill folder (.agents/skills/handling-json-in-common-lisp in ultralisp/ultralisp) into .agents/skills/handling-json-in-common-lisp in your project. Codex loads it when a task matches its description.
Can I use Handling JSON In 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 handling-json-in-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/handling-json-in-common-lisp, .gemini/skills/handling-json-in-common-lisp, .github/skills/handling-json-in-common-lisp and .opencode/skills/handling-json-in-common-lisp in your project.
What does Handling JSON In Common Lisp need to run?
SKILL.md names no scripts, command-line tools or credentials: Handling JSON In Common Lisp is instructions for the agent only.
Does Handling JSON In 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 Handling JSON In 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 Handling JSON In Common Lisp use?
No licence was found for Handling JSON In Common Lisp or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Handling JSON In Common Lisp use?
About 813 tokens (SKILL.md is roughly 3.3k 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 Handling JSON In Common Lisp?
Skills that share tags, products or a category with Handling JSON In 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 Handling JSON In 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.