运维测试
- 作者仓库星标 1,012
- 叉子 98
- 作者更新于 2026年4月16日 02:05
- 作者仓库 dotnet-skills
- 领域
- 效率工具
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @Aaronontheweb · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: marketplace-publishing
description: Workflow for publishing skills and agents to the dotnet-skills Claude Code marketplace. Covers a…
category: 效率工具
runtime: 无特殊运行时
---
# marketplace-publishing 输出预览
## PART A: 任务判断
- 适用问题:日常重复事务、资料整理、邮件或工作流提效。
- 输入要求:目标材料、限制条件、期望输出和验收方式。
- 证据边界:围绕“Repository Structure / Adding a New Skill / Step 1: Choose a Category”读取原文规则,不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断:确认你的需求是否属于日常重复事务、资料整理、邮件或工作流提效,并标出输入、限制和预期结果。
- **02** 执行计划:优先按“Repository Structure / Adding a New Skill / Step 1: Choose a Category”拆成步骤,说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果:给出可复制的命令、文件改动、检查清单或内容草稿,并说明如何继续迭代。
- **04** 风险边界:结合 读取文件、写入/修改文件、主要在本地完成、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件;主要在本地完成;通常不需要额外 API Key。
- 先小样例验证,再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 原文出现了 `/agents`、`/plugin` 这类斜杠命令;如果你的 Agent 支持命令触发,优先用命令开场,再补充目标和边界。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是:读取文件、写入/修改文件。
先用一个小任务确认它会围绕“Repository Structure / Adding a New Skill / Step 1: Choose a Category”工作;涉及文件或命令时,先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作;如果输出泛泛而谈,就补充输入、边界和验收标准后重跑。
---
name: marketplace-publishing
description: Workflow for publishing skills and agents to the dotnet-skills Claude Code marketplace. Covers a…
category: 效率工具
source: Aaronontheweb/dotnet-skills
---
# marketplace-publishing
## 什么时候使用
- marketplace-publishing 是效率工具方向的技能,把日常重复操作(整理、汇总、定时任务)交给 Agent 处理 适合处理重复事务、信息整理、邮件和日常工作流提效,核心价值是把输入、判断、执行、验证和交付边界固定下来,避…
- 面向日常重复事务、资料整理、邮件或工作流提效,优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Repository Structure / Adding a New Skill / Step 1: Choose a Category」组织步骤,不把推断写成作者事实。
- 读取文件、写入/修改文件;主要在本地完成;通常不需要额外 API Key。
- 先跑小样例,确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown,不编造命令、平台或依赖。 作者原文负责流程事实;仓库文件负责来源和命令;流狐只补充适用场景、限制和质量判断。
skill "marketplace-publishing" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Repository Structure / Adding a New Skill / Step 1: Choose a Category
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件 | 主要在本地完成
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
} Marketplace Publishing Workflow
This skill documents how to publish skills and agents to the dotnet-skills Claude Code marketplace.
Repository Structure
dotnet-skills/
├── .claude-plugin/
│ ├── marketplace.json # Marketplace catalog
│ └── plugin.json # Plugin metadata + skill/agent registry
├── .github/workflows/
│ └── release.yml # Release automation
├── skills/
│ ├── akka/ # Akka.NET skills
│ │ ├── best-practices/SKILL.md
│ │ ├── testing-patterns/SKILL.md
│ │ └── ...
│ ├── aspire/ # .NET Aspire skills
│ ├── csharp/ # C# language skills
│ ├── testing/ # Testing framework skills
│ └── meta/ # Meta skills
├── agents/
│ └── *.md # Agent definitions
└── scripts/
└── validate-marketplace.sh
Adding a New Skill
Step 1: Choose a Category
Skills are organized by domain:
| Category | Purpose |
|---|---|
akka/ |
Akka.NET actor patterns, testing, clustering |
aspire/ |
.NET Aspire orchestration, testing, configuration |
csharp/ |
C# language features, coding standards |
testing/ |
Testing frameworks (xUnit, Playwright, Testcontainers) |
meta/ |
Meta skills about this marketplace |
Create a new category folder if none fits.
Step 2: Create the Skill Folder
Create a folder with SKILL.md inside:
skills/<category>/<skill-name>/SKILL.md
Example: skills/akka/cluster-sharding/SKILL.md
Step 3: Write the SKILL.md
---
name: my-new-skill
description: Brief description of what this skill does and when to use it.
---
# My New Skill
## When to Use This Skill
Use this skill when:
- [List specific scenarios]
---
## Content
[Comprehensive guide with examples, patterns, and anti-patterns]
Requirements:
namemust be lowercase with hyphens (e.g.,cluster-sharding)descriptionshould be 1-2 sentences explaining when Claude should use this skill- Content should be 10-40KB covering the topic comprehensively
- Include concrete code examples with modern C# patterns
Step 4: Register in plugin.json
Add the skill path to .claude-plugin/plugin.json in the skills array:
{
"skills": [
"./skills/akka/best-practices",
"./skills/akka/cluster-sharding" // Add new skill here
]
}
Step 5: Validate
Run the validation script:
./scripts/validate-marketplace.sh
Step 6: Commit Together
git add skills/akka/cluster-sharding/ .claude-plugin/plugin.json
git commit -m "Add cluster-sharding skill for Akka.NET Cluster Sharding patterns"
Adding a New Agent
Step 1: Create the Agent File
Create a markdown file in /agents/:
---
name: my-agent-name
description: Expert in [domain]. Specializes in [specific areas]. Use for [scenarios].
model: sonnet
color: blue
---
You are a [domain] specialist with deep expertise in [areas].
**Reference Materials:**
- [Official docs and resources]
**Core Expertise Areas:**
[List expertise areas]
**Diagnostic Approach:**
[How the agent analyzes problems]
Requirements:
namemust be lowercase with hyphensmodelmust be one of:haiku,sonnet,opuscoloris optional (used for UI display)
Step 2: Register in plugin.json
Add to the agents array:
{
"agents": [
"./agents/akka-net-specialist",
"./agents/my-agent-name" // Add new agent here
]
}
Step 3: Commit Together
git add agents/my-agent-name.md .claude-plugin/plugin.json
git commit -m "Add my-agent-name agent for [domain] expertise"
Publishing a Release
Versioning
Update the version in .claude-plugin/plugin.json:
{
"version": "1.1.0"
}
Use semantic versioning (MAJOR.MINOR.PATCH):
- MAJOR: Breaking changes (renamed/removed skills)
- MINOR: New skills or agents added
- PATCH: Fixes or improvements to existing content
Release Process
Update version in plugin.json
Validate
./scripts/validate-marketplace.shCommit version bump
git add .claude-plugin/plugin.json git commit -m "Bump version to 1.1.0"Create and push tag
git tag v1.1.0 git push origin master --tagsGitHub Actions will automatically:
- Validate the marketplace structure
- Create a GitHub release with auto-generated notes
User Installation
Users install the complete plugin (all skills and agents):
# Add the marketplace (one-time)
/plugin marketplace add Aaronontheweb/dotnet-skills
# Install the plugin (gets everything)
/plugin install dotnet-skills
# Update to latest version
/plugin marketplace update
Validation Checklist
Before committing:
- SKILL.md has valid YAML frontmatter with
nameanddescription - Skill folder is under appropriate category
- Path added to
plugin.jsonskills array - For agents:
modelis specified (haiku/sonnet/opus) -
./scripts/validate-marketplace.shpasses
Troubleshooting
Skill not appearing after install
- Verify the path in plugin.json matches the folder structure
- Check that SKILL.md exists in the folder
- Try reinstalling:
/plugin uninstall dotnet-skills && /plugin install dotnet-skills
Validation errors
- Ensure JSON is valid:
jq . .claude-plugin/plugin.json - Check for trailing commas in arrays
- Verify all referenced folders contain SKILL.md
Release not created
- Ensure tag follows semver format (
v1.0.0) - Check GitHub Actions logs for errors
- Verify plugin.json version matches the tag
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核