Back to Details

aios-skill-publisher

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

AIOS Skill Publisher

AIOS 技能发布器

Purpose

用途

Automate the creation and publishing of proprietary skills for Claim Supply / NoManagement B.V. Ensures every custom skill follows a consistent format, uses the aios- prefix, publishes to the mrnobrands/aios-skills GitHub repo, and becomes installable via npx.
自动化为Claim Supply / NoManagement B.V.创建和发布专有技能。确保所有自定义技能遵循统一格式，使用aios-前缀，发布到mrnobrands/aios-skills GitHub仓库，且可通过npx安装。

When to Use

适用场景

  • User asks to create, build, make, or write a new skill
  • User asks to publish a skill to the AIOS repo
  • User wants to convert a workflow or process into a reusable skill
  • User references proprietary skill creation or aios-skills
  • 用户要求创建、构建、制作或编写新技能
  • 用户要求将技能发布到AIOS仓库
  • 用户希望将工作流或流程转换为可复用技能
  • 用户提及专有技能创建或aios-skills

Do NOT Use For

不适用场景

  • Installing marketplace skills (use npx skills add directly)
  • Editing existing marketplace community skills
  • Creating skills for other repos or systems
  • 安装市场技能（直接使用npx skills add）
  • 编辑现有市场社区技能
  • 为其他仓库或系统创建技能

Context Loading

上下文加载

Always Read

始终读取

  1. This SKILL.md
  2. references/skill-template.md — blank template for new skills
  3. references/naming-rules.md — naming and format conventions
  1. 本SKILL.md文件
  2. references/skill-template.md — 新技能的空白模板
  3. references/naming-rules.md — 命名和格式规范

Process

流程

Step 1: Gather Requirements

步骤1：收集需求

Ask the user (if not already clear):
  • What does this skill do? (one sentence)
  • When should it trigger? (what phrases or tasks activate it)
  • Does it need reference files? (templates, examples, patterns)
If the user has already provided enough detail, skip to Step 2.
向用户确认以下信息（若已明确可跳过）：
  • 该技能的功能是什么？（一句话描述）
  • 什么时候触发？（哪些短语或任务会激活它）
  • 是否需要参考文件？（模板、示例、模式）
如果用户已经提供了足够的细节，直接跳到步骤2。

Step 2: Determine Skill Name

步骤2：确定技能名称

  • Take the users description and create a kebab-case name
  • Prepend aios- prefix (always lowercase)
  • Examples: aios-lead-scoring, aios-weekly-digest, aios-client-onboarding
  • Confirm the name with the user before proceeding
  • 根据用户的描述创建kebab-case格式的名称
  • 添加aios-前缀（始终小写）
  • 示例：aios-lead-scoring、aios-weekly-digest、aios-client-onboarding
  • 继续操作前先和用户确认名称

Step 3: Locate the Repo

步骤3：定位仓库

Detect which machine you are on:
  • If /Users/luca exists → Mac path: /Users/luca/NoBrands Dropbox/MR. NO/Github/aios-skills/
  • If /home/luca exists and no /Users → VPS path: /home/luca/aios-skills/
检测当前运行的机器：
  • 如果存在/Users/luca目录 → Mac路径：/Users/luca/NoBrands Dropbox/MR. NO/Github/aios-skills/
  • 如果存在/home/luca目录且无/Users目录 → VPS路径：/home/luca/aios-skills/

Step 4: Create Skill Directory

步骤4：创建技能目录

mkdir -p [REPO_PATH]/aios-[skill-name]/references
mkdir -p [REPO_PATH]/aios-[skill-name]/references

Step 5: Write SKILL.md

步骤5：编写SKILL.md

Use the template from references/skill-template.md. Critical rules:
  • name field matches directory name exactly (all lowercase, kebab-case)
  • description under 1024 characters, no XML angle brackets
  • description includes trigger phrases, NOT a workflow summary
  • Include metadata.author: claim-supply and metadata.version: 1.0.0
  • Required sections: Purpose, When to Use, Context Loading, Process, Quality Gates, Output Format
使用references/skill-template.md中的模板。关键规则：
  • name字段与目录名称完全匹配（全小写，kebab-case格式）
  • 描述不超过1024个字符，不含XML尖括号
  • 描述包含触发短语，而非工作流摘要
  • 包含metadata.author: claim-supply和metadata.version: 1.0.0
  • 必需章节：用途、适用场景、上下文加载、流程、质量门禁、输出格式

Step 6: Create Reference Files (if needed)

步骤6：创建参考文件（若需要）

Place in references/ directory. Each file is kebab-case .md. Only create references the skill actually needs.
放在references/目录下，每个文件采用kebab-case命名的.md格式，仅创建技能实际需要的参考文件。

Step 7: Validate

步骤7：校验

  • name field matches directory name (lowercase kebab-case)
  • description has trigger phrases, not workflow summary
  • description under 1024 characters, no angle brackets
  • All required sections present
  • No placeholder text remaining
  • No README.md in skill folder
  • name字段与目录名称匹配（小写kebab-case格式）
  • 描述包含触发短语，而非工作流摘要
  • 描述不超过1024个字符，无尖括号
  • 所有必需章节都已存在
  • 无剩余占位符文本
  • 技能文件夹中没有README.md

Step 8: Publish to GitHub

步骤8：发布到GitHub

cd [REPO_PATH] && git add -A && git commit -m "Add aios-[skill-name]" && git push
cd [REPO_PATH] && git add -A && git commit -m "Add aios-[skill-name]" && git push

Step 9: Install Locally

步骤9：本地安装

npx -y skills add -y -g mrnobrands/aios-skills
npx -y skills add -y -g mrnobrands/aios-skills

Step 10: Notify User

步骤10：通知用户

Report: skill name, GitHub URL, install command, confirmation of local install.
告知内容：技能名称、GitHub URL、安装命令、本地安装确认信息。

Quality Gates

质量门禁

  • Lowercase aios- prefix naming convention followed
  • Folder name matches name field exactly
  • YAML frontmatter valid and under 1024 chars
  • Description contains trigger phrases only
  • All SKILL.md sections present and filled in
  • No README.md in skill folder
  • Git push succeeded
  • npx install succeeded
  • 遵循小写aios-前缀的命名规范
  • 文件夹名称与name字段完全匹配
  • YAML frontmatter有效且长度不超过1024字符
  • 描述仅包含触发短语
  • SKILL.md的所有章节均已存在并填写完整
  • 技能文件夹中没有README.md
  • Git推送成功
  • npx安装成功

Output Format

输出格式

  1. New directory in mrnobrands/aios-skills repo
  2. Valid SKILL.md with proper frontmatter
  3. Optional reference files in references/
  4. Git commit and push to GitHub
  5. Local npx install
  1. mrnobrands/aios-skills仓库中的新目录
  2. 带有正确frontmatter的有效SKILL.md
  3. references/目录下的可选参考文件
  4. Git提交并推送到GitHub
  5. 本地npx安装完成

Examples

示例

Example 1: Create a lead scoring skill

示例1：创建线索评分技能

User says: "Create a new skill for scoring incoming leads" Result: aios-lead-scoring/ with SKILL.md, pushed to GitHub, installed locally
用户说："创建一个用于给新流入线索打分的新技能" 结果：包含SKILL.md的aios-lead-scoring/目录，推送到GitHub，本地安装完成

Example 2: Convert a process to a skill

示例2：将流程转换为技能

User says: "Turn our weekly digest process into a skill" Result: aios-weekly-digest/ with full process as a skill
用户说："把我们的每周摘要流程做成一个技能" 结果：包含完整流程作为技能的aios-weekly-digest/目录

Troubleshooting

故障排查

Git push fails

Git推送失败

Cause: No git credentials or repo not cloned. Fix Mac: Check gh auth status. Run gh auth login if needed. Fix VPS: Check git config. May need personal access token.
原因：没有Git凭证或仓库未克隆。 修复Mac：检查gh auth状态，必要时运行gh auth login。 修复VPS：检查git config，可能需要个人访问令牌。

npx install shows old skills

npx安装显示旧技能

Cause: npm cache serving stale version. Fix: Wait 1-2 minutes and retry.
原因：npm缓存提供了过期版本。 修复：等待1-2分钟后重试。

Skill does not trigger

技能无法触发

Cause: Description missing trigger phrases or too vague. Fix: Add specific keywords. Test: "When would you use the [skill] skill?"
原因：描述缺少触发短语或过于模糊。 修复：添加具体关键词。测试："你什么时候会使用[skill]技能？"

References

参考

  • references/skill-template.md — Blank SKILL.md template
  • references/naming-rules.md — Naming conventions and rules
  • references/skill-template.md — 空白SKILL.md模板
  • references/naming-rules.md — 命名规范和规则