메뉴
Manage skills with the devookim-skills CLI. Use when listing, installing, updating, or removing DevooKim/my-agents skills, or when vendoring an external skill and merging upstream changes into a locally modified copy.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/DevooKim/my-agents --skill devookim-skills명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
| name | devookim-skills |
| description | Manage skills with the devookim-skills CLI. Use when listing, installing, updating, or removing DevooKim/my-agents skills, or when vendoring an external skill and merging upstream changes into a locally modified copy. |
The current CLI release is 0.3.0, matching cli/package.json. Invoke every
command as bunx devookim-skills@0.3.0 .... When the CLI version changes, update
this pinned version and cli/package.json in the same release. A bare package
name and @latest are not valid for operational commands because Bun/npm
resolution or cache state can select a different CLI release.
bunx devookim-skills@0.3.0 find when the skill name is unknown.add, update, or remove.-y to
force the non-interactive path when no name is available.-g only when the user wants a user-level installation.add --local to test the current my-agents checkout before it is pushed.my-agents checkout, use -g; project-scoped installation there would collide with the vendoring skills-lock.json.--repo, then DEVOOKIM_SKILLS_REPO, then the current directory's ancestors.vendor add to copy the complete skill directory into skills/vendor/<name>/ and record its exact upstream commit in skills-lock.json.vendor check before vendor update when the user requests a review without changes.vendor update to 3-way merge the locked upstream base, the local copy, and the new upstream version.vendor continue; the lockfile remains unchanged until this succeeds.Treat skills/vendor/<name>/ and its skills-lock.json entry as one change. Preserve local modifications during upstream updates and inspect the resulting diff before reporting completion.