메뉴
Install a skill from a GitHub URL or local path. Copies SKILL.md (and references/scripts) into the project's .opencode/skills/ directory and creates the companion command. Use when user wants to add an existing skill to their project.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | install-skill |
| description | Install a skill from a GitHub URL or local path. Copies SKILL.md (and references/scripts) into the project's .opencode/skills/ directory and creates the companion command. Use when user wants to add an existing skill to their project. |
Install an existing skill into the current project from a GitHub repo or local path.
The user provides one of:
https://github.com/user/repo/tree/main/path/to/skill~/other-project/.opencode/skills/my-skill/~/.config/opencode/skills/ to copy into the projectIf unclear, ask the user where the skill lives.
From GitHub:
# Clone the repo (shallow) to a temp directory, copy the skill files
TMPDIR=$(mktemp -d)
gh repo clone <user/repo> "$TMPDIR" -- --depth 1
cp -r "$TMPDIR/<path-to-skill-dir>" .opencode/skills/<name>/
rm -rf "$TMPDIR"
From local path:
cp -r <source-path>/ .opencode/skills/<name>/
From global skills:
cp -r ~/.config/opencode/skills/<name>/ .opencode/skills/<name>/
Check the copied skill has valid structure:
SKILL.md exists with valid YAML frontmatter (name + description)name field matches directory namereferences/ or scripts/ are presentIf frontmatter is missing or invalid, fix it before proceeding.
If a companion command file wasn't included in the source, create .opencode/commands/<name>.md:
---
description: <from skill's description field>
---
<One-line summary.>
First, invoke the skill tool to load the <name> skill:
` ` `skill({ name: '<name>' })` ` `
Then follow the skill instructions.
<user-request>
$ARGUMENTS
</user-request>
git add .opencode/skills/<name>/ .opencode/commands/<name>.md
git commit -m "add <name> skill"
Tell the user:
/<name>.opencode/ and committed to gitSurvey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.
Create a custom skill for this project. Determines skill type, writes SKILL.md (and optional references/scripts) to .opencode/skills/<name>/, commits and pushes. Load FIRST before writing any skill.
Import a bitmap image (PNG/JPEG/GIF) from a URL into a Figma file as a frame. Use whenever an image needs to land in Figma — AI mockups, photos, renders, artwork, screenshots. Bypasses use_figma sandbox limits that block the obvious paths (fetch, atob, createImageAsync, REST upload). If you skip this skill and try the obvious paths, you will lose 30+ minutes. Triggers on: import image to Figma, add image to Figma, put image in Figma, Figma image import, bitmap to Figma.
Generate images, videos, and music using AI models (Imagen, Flux, Veo, Runway, Kling, Sora, Suno, ElevenLabs, etc.). Use when user asks to create, generate, edit, upscale, or produce any visual or audio media.
Creates and maintains Figma Code Connect template files that map Figma components to code snippets. Use when the user mentions Code Connect, Figma component mapping, design-to-code translation, or asks to create/update .figma.js files.
Build or update a professional-grade design system in Figma from a codebase. Use when the user wants to create variables/tokens, build component libraries, set up theming (light/dark modes), document foundations, or reconcile gaps between code and Figma. This skill teaches WHAT to build and in WHAT ORDER — it complements the `figma-use` skill which teaches HOW to call the Plugin API. Both skills should be loaded together.