skl (@skl)
Public skills
- skl/canvas-design — Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
- skl/brand-guidelines — Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
- skl/karpathy-guidelines — Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
- skl/skill-creator — Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
- skl/frontend-design — Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
- skl/skl — Use the skl CLI to publish, install, and manage reusable Agent Skills across
AI coding agents (Claude, Copilot, Cursor, Gemini, Junie, Kiro, plus the
cross-agent .agents/skills standard used by Codex, Zed, Goose, Amp, OpenCode,
Roo, pi, and Grok) — "the Agent Skills manager." Trigger whenever the user
wants to install/add/remove/publish/save/share or "set up" Agent Skills
(packaged skills in folders like .claude/skills, .cursor/skills,
.agents/skills), or check installed-skill health — even if they never type
`skl`.
Typical intents:
- land/install the skills a skl.json manifest lists (e.g. after cloning a repo)
- add/remove a named skill (often user/skill-name) + update the manifest and
each agent's skills folder
- install a skill for the whole machine (user-level, `-g`) instead of one project
- publish/push a local skill folder so others can grab it, or save it privately
- install a skill straight from a GitHub repo URL
- log in to useskl.com or a skl server to publish/fetch
- scan a project for out-of-date or modified skills
Not for writing a skill's content (use skill-creator) or unrelated package
managers (npm/pip/etc.).
- skl/claude-api — Reference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration.
TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens).
SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).