一键在 Manus 中运行任何 Skill

开始使用

plugin-overlay-bundling

星标266

分支42

更新时间2026年4月25日 15:16

Pattern for keeping published plugin templates stable while layering source-owned helper files and skill content.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

sbroenne

sbroenne/mcp-server-excel

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Context

Use this when plugin artifacts are built by copying validated templates from a published/distribution repo, but the source repo still needs to own release-coupled helper files or skill content.

Pattern

Keep the validated published plugin structure as the base copy input.
Add a source-owned overlay directory (for example .github/plugins/<plugin-name>/) for files that should be authored in the source repo:
- plugin README updates
- install helpers
- wrapper scripts
In the build script, apply the overlay after copying the template, then inject version metadata.
Prefer keeping published plugins lightweight; ship binaries through the main release artifacts unless the marketplace repo can safely host them.
Update the release workflow and source-side sync gate to watch both the build script and the overlay directory.
If the published marketplace repo is mid-migration, make the automation prefer the canonical marketplace manifest path/schema (.github/plugin/marketplace.json, metadata.version) but tolerate the legacy path/schema (marketplace.json, version) until the published repo is updated.

Why

Preserves the “copy validated templates” discipline without forcing the published repo to be the only authoring surface.
Avoids pushing oversized release binaries into the published marketplace repo.
Keeps plugin-specific helper scripts versioned in the source repo, where product/release changes are made.
Lets source automation become more spec-compliant without forcing an all-at-once published-repo migration.

Example

scripts/Build-Plugins.ps1 copies ../mcp-server-excel-plugins/plugins/excel-cli, applies .github/plugins/excel-cli/, and refreshes the skill content without adding release binaries.
publish-plugins.yml can publish the plugin bundle directly after Build-Plugins.ps1 because the standalone CLI remains distributed through GitHub Releases and NuGet.

同仓库更多 Skills

同仓库

skill-name

sbroenne/mcp-server-excel

{what this skill teaches agents}

2026-07-09332

excel-cli

sbroenne/mcp-server-excel

Excel CLI automation skill for Windows workbooks. Use when a coding agent needs token-efficient, scriptable, or unattended Excel automation via excelcli commands. Best for CI/CD, scheduled jobs, batch processing, PowerShell workflows, and bulk workbook edits. Supports Power Query, DAX, PivotTables, Tables, Ranges, Charts, VBA, Data Models, screenshots, and formatting. Triggers: excelcli, Excel CLI, command line, batch, script, automation, CI/CD, scheduled, PowerShell, unattended, coding agent, workbook processing.

2026-07-08332

excel-mcp

sbroenne/mcp-server-excel

Excel MCP Server skill for Windows workbook automation. Use when an assistant needs rich MCP tools to create, inspect, modify, format, or analyze Excel files. Supports Power Query (M), Data Model/DAX, PivotTables, Tables, Ranges, Charts, Slicers, formatting, screenshots, VBA macros, connections, and calculation mode. Triggers: Excel, spreadsheet, workbook, xlsx, xlsm, Power Query, DAX, PivotTable, chart, dashboard, VBA, MCP.

2026-07-08332

skill-name

sbroenne/mcp-server-excel

{what this skill teaches agents}

2026-04-29332

plugin-build-smoke-regression

sbroenne/mcp-server-excel

Catch packaging-script regressions by asserting the real script exit path and current overlay surface.

2026-04-27332

dependabot-tooling-downgrade

sbroenne/mcp-server-excel

Use a validated tooling downgrade when Dependabot flags an unpatchable transitive vulnerability in build-only dependencies.

2026-04-26332

name	plugin-overlay-bundling
description	Pattern for keeping published plugin templates stable while layering source-owned helper files and skill content.

Context

Use this when plugin artifacts are built by copying validated templates from a published/distribution repo, but the source repo still needs to own release-coupled helper files or skill content.

Pattern

Keep the validated published plugin structure as the base copy input.
Add a source-owned overlay directory (for example .github/plugins/<plugin-name>/) for files that should be authored in the source repo:
- plugin README updates
- install helpers
- wrapper scripts
In the build script, apply the overlay after copying the template, then inject version metadata.
Prefer keeping published plugins lightweight; ship binaries through the main release artifacts unless the marketplace repo can safely host them.
Update the release workflow and source-side sync gate to watch both the build script and the overlay directory.
If the published marketplace repo is mid-migration, make the automation prefer the canonical marketplace manifest path/schema (.github/plugin/marketplace.json, metadata.version) but tolerate the legacy path/schema (marketplace.json, version) until the published repo is updated.

Why

Preserves the “copy validated templates” discipline without forcing the published repo to be the only authoring surface.
Avoids pushing oversized release binaries into the published marketplace repo.
Keeps plugin-specific helper scripts versioned in the source repo, where product/release changes are made.
Lets source automation become more spec-compliant without forcing an all-at-once published-repo migration.

Example

scripts/Build-Plugins.ps1 copies ../mcp-server-excel-plugins/plugins/excel-cli, applies .github/plugins/excel-cli/, and refreshes the skill content without adding release binaries.
publish-plugins.yml can publish the plugin bundle directly after Build-Plugins.ps1 because the standalone CLI remains distributed through GitHub Releases and NuGet.