메뉴
Publishes a validated Syncolab skill via GitHub pull request for review and merge to main. Use when submitting a new or updated skill under skills/ to the syncolab-skills repository after local authoring is complete.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/poly-gents/syncolab-skills --skill publish-skill명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
Project Knowledge Base concept tree — decisions, risks, notes, and custom taxonomy inside Managents (no extra OAuth)
Stakeholder-facing project timelines and milestones inside Managents (no extra OAuth)
Startup authoring skill for the Project System Assistant. Teaches Playbook Architect how to clarify intent, use filtered tool discovery, and preserve artifacts and validations while drafting playbooks.
SOC 직업 분류 기준
| name | publish-skill |
| description | Publishes a validated Syncolab skill via GitHub pull request for review and merge to main. Use when submitting a new or updated skill under skills/ to the syncolab-skills repository after local authoring is complete. |
Opens a GitHub pull request to add or update a Syncolab skill on main after local authoring and validation are complete. Assumes the syncolab-skills repo is cloned, the agent has shell and GitHub access (git, gh), and skill content already follows repository standards.
For authoring the skill itself, use create-skill first.
skills/<skill-label>/ and should land on main via review.origin.main with a clear summary and test plan.create-skill checklist). Syncolab maintainers update catalog artifacts when merging to main.skills/, e.g. create-skill.origin URL and default branch (usually main).main.meta.schema.json and instruction files.Confirm the skill package is complete per create-skill before publishing.
# Repo root
test -d skills && command -v git && command -v gh
gh is missing or unauthenticated, stop and ask the user to install/auth (gh auth login).SKILL.md / meta.yaml are missing or invalid.Confirm each skill in scope passes the create-skill review checklist (structure, frontmatter, meta.yaml vs schema). Do not open a PR with known schema or naming errors.
git status
git diff
git branch -vv
git log -5 --oneline
skills/<skill-label>/ (and only include intentional related changes)..env files.git fetch origin
git log origin/main..HEAD --oneline
git diff origin/main...HEAD --stat
Create a new branch if still on main with local commits, or continue on an existing feature branch.
git checkout -b "add-skill-<skill-label>"
# or reuse an approved branch name the user prefers
Stage only skill-related paths:
git add "skills/<skill-label>/"
# add other skill paths if multiple skills in one PR
git status
Commit message (complete sentences, focus on why):
Add <skill-label> skill for <short capability summary>.
EOF via heredoc when committing from automation.
Use a HEREDOC for multi-line messages:
git commit -m "$(cat <<'EOF'
Add create-skill skill for authoring validated Syncolab skills.
EOF
)"
--no-verify unless the user explicitly requests it.git push -u origin HEAD
gh pr create --title "Add <skill-label> skill" --body "$(cat <<'EOF'
## Summary
- Adds `skills/<skill-label>/` with SKILL.md and meta.yaml.
- Review: skill conforms to `meta.schema.json` and instruction files.
## Test plan
- [ ] Skill reviewed against schema and instructions
- [ ] Review routing metadata (description, tags, triggers)
- [ ] Confirm skill boundaries and tool rules are appropriate
EOF
)"
Adjust title/body for updates vs new skills (Update … / Fix validation for …).
Return:
| Access | Behavior |
|---|---|
git + gh + network | Branch, commit (if approved), push, open PR. |
git only | Prepare branch and commit locally; give exact gh pr create for the user. |
| Read-only | Output step-by-step commands and PR body draft; do not claim push/PR succeeded. |
Never fabricate PR URLs, CI status, or review approval.
Ready to publish when:
SKILL.md are aligned (triggers, boundaries, type).Do not:
main / master without explicit user request (warn if asked).git add . when unrelated changes exist in the tree.## Publish result
- **PR:** <url>
- **Branch:** <name>
- **Skills:** <skill-label>(s)
- **Validation:** passed | failed (details)
## Notes
- <uncommitted files, follow-ups, or reviewer callouts>
Add code-review skill, not Updates)..env, or private keys.git add ..skills/create-skill/SKILL.mdskills/skill.instruction.mdskills/meta.schema.json — metadata rulesgh pr create, gh pr view