Skip to main content

skill-installer

Discover and install Amplifier-compatible skills from a local folder or Git repository into the requested project, personal directory, or bundle.

ソース情報

リポジトリ
microsoft/amplifier-bundle-work
ソースの最終更新活動
2026年9月20日 22:41
検出された SKILL.md の言語
英語
スター
0
フォーク
0

インストール方法

デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。

ソースファイルを確認

インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。

SKILL.md を表示中

SKILL.md
ソースの指示 · 読み取り専用プレビュー
name
skill-installer
description
Discover and install Amplifier-compatible skills from a local folder or Git repository into the requested project, personal directory, or bundle.
compatibility
Amplifier filesystem tools and load_skill; Git and network access for remote sources.
user-invocable
true
# Skill Installer Resolve the requested repository/path and revision. Use existing authorized Git credentials, never embedded tokens. Inspect the skill package, license, scripts, resource links, and dependencies before installation. Do not execute source scripts or preprocessing merely to list skills. If a foreign skill needs tool, runtime, or host translation, use `adapt-skill` when available or report those requirements before calling it usable. Use `.amplifier/skills` for a requested project install, `~/.amplifier/skills` for a personal install, or the exact bundle directory the user selected. Refuse silent collisions. Copy the whole permitted package while excluding repository metadata, credentials, generated caches, and dependency directories. Reject symlinks escaping the package and keep originals intact. Use `.agents/skills` when the user requests a shared cross-client install. Work discovers both conventions; project skills precede user skills, and native paths win within a scope. Check the actual winning path from `load_skill` after install. Check resource closure before copying an individual skill. Work's Office skills share `../_shared` helpers, so install the collection through its behavior or include that sibling directory without overwriting an existing different version. A lone `SKILL.md` or leaf directory is not the complete package in this case. For Git sources, follow the requested branch and record the tested revision in validation evidence. Do not pin bundle or module source declarations. Register through the host's real skill-source configuration when that is preferable to copying. Namespaced bundle sources are resolved through Foundation; relative `./skills` is unsafe when the host starts elsewhere. Refresh discovery through the supported tool or a fresh session, then call `load_skill` for every installed name and verify resources. Report the destination, revision, invocation, dependencies, and validation. Do not claim that skill installation also installed its external services.
GitHubで見る