القائمة
How to add or update a skill in yusukebe/skills from inside another working project. Owner-only — uses Yusuke's local gh CLI auth.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/yusukebe/skills --skill contributeيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | contribute |
| title | Add or update a skill on skills.yusuke.run |
| description | How to add or update a skill in yusukebe/skills from inside another working project. Owner-only — uses Yusuke's local gh CLI auth. |
| tags | ["meta","github","gh","ci","owner-only"] |
| references | ["https://github.com/yusukebe/skills","https://cli.github.com/manual/gh_api"] |
| related | [] |
This skill describes how to contribute a new skill (or update an existing one) to the yusukebe/skills repo from a different working project, without leaving that project.
Owner-only. The flow uses the
ghCLI authenticated asyusukebe. If you are an agent working on someone else's machine, you cannot push toyusukebe/skills— skip this skill.
The catalog uses the vercel-labs/skills layout: each skill is a directory under skills/ with a SKILL.md inside. The registry is regenerated automatically before each deploy from skills/*/SKILL.md, so all you need to add is one Markdown file in the right place. PR → auto-merge → Cloudflare Workers Builds deploys.
kebab-case, short, descriptive. The name doubles as the directory name and the URL slug. Look at https://skills.yusuke.run/skills.json to keep naming consistent with the existing catalog.
Save it as /tmp/SKILL.md (or any temp path). Required frontmatter — the name field is what npx skills add looks for:
---
name: <name>
title: <one-sentence title>
description: <one-line description shown in the root index>
tags: [<lowercase>, <kebab-case>]
references:
- https://...
related: []
---
# ...
Follow the prose conventions: one paragraph per line, no hard wraps, English. Aim for "opinionated guidance + links into the web" rather than a tutorial. If the topic has no good web resource, write the guidance out in full.
NAME=<name>
BRANCH=add-skill-$NAME
MAIN_SHA=$(gh api repos/yusukebe/skills/git/refs/heads/main --jq '.object.sha')
gh api repos/yusukebe/skills/git/refs \
-f ref="refs/heads/$BRANCH" \
-f sha="$MAIN_SHA"
gh api -X PUT "repos/yusukebe/skills/contents/skills/$NAME/SKILL.md" \
-f message="add $NAME skill" \
-f branch="$BRANCH" \
-f content="$(base64 < /tmp/SKILL.md)"
Creating the file at the nested path skills/$NAME/SKILL.md implicitly creates the skills/$NAME/ directory — there is no separate "create directory" call.
gh pr create \
--repo yusukebe/skills \
--base main \
--head "$BRANCH" \
--title "add $NAME skill" \
--body "Adds the \`$NAME\` skill. Auto-proposed from another project."
gh pr merge --repo yusukebe/skills "$BRANCH" --squash --auto
Cloudflare Workers Builds picks up the merged commit on main and deploys.
Same flow, but step 3 looks like this — fetch the current file's sha first and pass it in:
NAME=<name>
BRANCH=update-skill-$NAME
MAIN_SHA=$(gh api repos/yusukebe/skills/git/refs/heads/main --jq '.object.sha')
FILE_SHA=$(gh api "repos/yusukebe/skills/contents/skills/$NAME/SKILL.md?ref=main" --jq '.sha')
gh api repos/yusukebe/skills/git/refs \
-f ref="refs/heads/$BRANCH" \
-f sha="$MAIN_SHA"
gh api -X PUT "repos/yusukebe/skills/contents/skills/$NAME/SKILL.md" \
-f message="update $NAME skill" \
-f branch="$BRANCH" \
-f content="$(base64 < /tmp/SKILL.md)" \
-f sha="$FILE_SHA"
Then the same gh pr create + gh pr merge --auto as above.
Do not push to the catalog without an explicit go-ahead from Yusuke. If unsure whether a piece of knowledge is "catalog-worthy" or just a one-off, lean toward asking.